Server update causes client problems.

I have 15, 2003 servers in 5 application cluster groups of 3 servers.
Overnight each group is sequentially taken offline and data updates
undertaken. This process is triggered initially by the time but subsequent
updates are started by the notification of the previous cluster being back on
line. Dependant on the actual data, these application updates can take
between 10 and 60 minutes (large data and restart is needed).
The majority of these servers do not have a ‘user’ on the console but can
have up to 3,000 clients connected at any one time. An unplanned restart of
the OS under the application causes problems for the clients, whereas the
programmatically restarted application (and reboot if needed) ensures correct
closure and migration of clients.
I cannot configure AU to install updates but not restart (past a maximum 30
minute delay) to cover the above. This aspect of the update service is
designed for desktop but not a server environment.
This scenario is a subset of my 150 server estate, I cannot go around
logging onto each server to stop the re-start.
How can I automatically install all updates then restart at my request (at
up to 24 hours after install) on servers that do not have a user logged on?

> How can I automatically install all updates then restart at my request (at
> up to 24 hours after install) on servers that do not have a user logged on?

How to delay the update reboot up to 24 hours- see Method 2 here:
http://www.codinghorror.com/blog/archives/000294.html

*Should* be the same for W2003. *Should* be able to do so with a script?

Note: I possess little knowledge of Enterprise updating practices.
You *really* should post this issue to the Server General newsgroup.
Yes, I know there's a link to this NG under Management/Windows Update,
but this NG is really aimed at the Home User/SoHo.

Web-based:
http://www.microsoft.com/communities...&lang=en&cr=US

NNTP:
news://msnews.microsoft.com/microsof...server.general


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============



BobW wrote:

> I have 15, 2003 servers in 5 application cluster groups of 3 servers.
> Overnight each group is sequentially taken offline and data updates
> undertaken. This process is triggered initially by the time but subsequent
> updates are started by the notification of the previous cluster being back on
> line. Dependant on the actual data, these application updates can take
> between 10 and 60 minutes (large data and restart is needed).
> The majority of these servers do not have a ‘user’ on the console but can
> have up to 3,000 clients connected at any one time. An unplanned restart of
> the OS under the application causes problems for the clients, whereas the
> programmatically restarted application (and reboot if needed) ensures correct
> closure and migration of clients.
> I cannot configure AU to install updates but not restart (past a maximum 30
> minute delay) to cover the above. This aspect of the update service is
> designed for desktop but not a server environment.
> This scenario is a subset of my 150 server estate, I cannot go around
> logging onto each server to stop the re-start.
> How can I automatically install all updates then restart at my request (at
> up to 24 hours after install) on servers that do not have a user logged on?
>

BobW wrote:

> I cannot configure AU to install updates but not restart (past a maximum 30
> minute delay) to cover the above.

Because that's a bad idea. You should wait until you can restart before
installing any updates.

The best procedure for servers in a typical environment is to configure them to
download updates, and then to explicitly install the updates (i.e., by logging
into the server and double-clicking the yellow shield in the taskbar) at an
appropriate time. Your environment is not typical, so you might instead wish to
install the updates via a script. I've written one which might serve as a
starting point, there are many others available:

<http://www.scms.waikato.ac.nz/~harry/wsusupdate.vbs>

This was designed for use with WSUS but as far as I know it should work just as
well in a non-WSUS environment. Test it thoroughly before using it in production.

Harry.

"MowGreen [MVP]" wrote:
> How to delay the update reboot up to 24 hours- see Method 2 here:
> http://www.codinghorror.com/blog/archives/000294.html

Many thanks for the reply but the description of the policy is accurate -
this only applies with a logged on user. Not so good on a server farm
unfortunatly.

"Harry Johnston [MVP]" wrote:

>
> The best procedure for servers in a typical environment is to configure them to
> download updates, and then to explicitly install the updates (i.e., by logging
> into the server and double-clicking the yellow shield in the taskbar) at an
> appropriate time. Your environment is not typical, so you might instead wish to
> install the updates via a script. I've written one which might serve as a
> starting point, there are many others available:
>
> <http://www.scms.waikato.ac.nz/~harry/wsusupdate.vbs>
>

Not being a scripter, I will try this (it seems to work with the update
policy settings)
Many thanks