auto install but no restart

I'd like to know if it is possible to configure microsoft (windows) update
like:
"download updates for me and install but do not restart"?

I'd like to use this configuration on a terminal server. The server is in
use 7 days a week, so it may not restart automaticly.

An other option would be to install updates if no one is using the server.


Thanks in advance
Davy

"Davy" <> wrote in message
news:E394C9D1-CA4C-4BA8-89EC-...
> I'd like to know if it is possible to configure microsoft (windows) update
> like:
> "download updates for me and install but do not restart"?

No.... install requires restart. It's a critical component of the
installation process. This is so because the files are not actually
'installed' until a script runs at powerup, just before you get the login
prompt.

> I'd like to use this configuration on a terminal server. The server is in
> use 7 days a week, so it may not restart automaticly.

You absolutely do /not/ want to do this on a terminal server.

Terminal Servers have very specific procedural requirements for applying
updates.


> An other option would be to install updates if no one is using the server.

In fact, this is the /only/ appropriate option.

> Thanks in advance
> Davy

First of all
thanks for your response

Is it possible to configure automatic updates to install updates when no one
is using the machine? Or do you mean that i should check if no one is using
the terminal server and if not install the updates?


Davy

"Lawrence Garvin [MVP]" wrote:

>
> "Davy" <> wrote in message
> news:E394C9D1-CA4C-4BA8-89EC-...
> > I'd like to know if it is possible to configure microsoft (windows) update
> > like:
> > "download updates for me and install but do not restart"?
>
> No.... install requires restart. It's a critical component of the
> installation process. This is so because the files are not actually
> 'installed' until a script runs at powerup, just before you get the login
> prompt.
>
> > I'd like to use this configuration on a terminal server. The server is in
> > use 7 days a week, so it may not restart automaticly.
>
> You absolutely do /not/ want to do this on a terminal server.
>
> Terminal Servers have very specific procedural requirements for applying
> updates.
>
>
> > An other option would be to install updates if no one is using the server.
>
> In fact, this is the /only/ appropriate option.
>
> > Thanks in advance
> > Davy
>
>
>

You cannot explicitly configure the system to only install when nobody is
using the machine, however you could /schedule/ the installations to occur
when nobody is supposed to be using the machine. I would still not recommend
this practice on a server, though.

The best practice for installing updates on a server is to use Option 3
"Download and notify for installation", and then install the updates from
the server console after all users have logged off. This may require you to
establish a server maintenance time when no users are permitted to be logged
onto the server.


"Davy" <> wrote in message
news:4AE94F9E-4BB4-4B35-B23B-...
> First of all
> thanks for your response
>
> Is it possible to configure automatic updates to install updates when no
> one
> is using the machine? Or do you mean that i should check if no one is
> using
> the terminal server and if not install the updates?
>
>
> Davy
>
> "Lawrence Garvin [MVP]" wrote:
>
>>
>> "Davy" <> wrote in message
>> news:E394C9D1-CA4C-4BA8-89EC-...
>> > I'd like to know if it is possible to configure microsoft (windows)
>> > update
>> > like:
>> > "download updates for me and install but do not restart"?
>>
>> No.... install requires restart. It's a critical component of the
>> installation process. This is so because the files are not actually
>> 'installed' until a script runs at powerup, just before you get the login
>> prompt.
>>
>> > I'd like to use this configuration on a terminal server. The server is
>> > in
>> > use 7 days a week, so it may not restart automaticly.
>>
>> You absolutely do /not/ want to do this on a terminal server.
>>
>> Terminal Servers have very specific procedural requirements for applying
>> updates.
>>
>>
>> > An other option would be to install updates if no one is using the
>> > server.
>>
>> In fact, this is the /only/ appropriate option.
>>
>> > Thanks in advance
>> > Davy
>>
>>
>>

I was looking for automated solution. That is what i'm doing now, but indeed
it's probably the best solution.

Thank you for your response
I take this as a good answer for my question

Davy

"Lawrence Garvin [MVP]" wrote:

> You cannot explicitly configure the system to only install when nobody is
> using the machine, however you could /schedule/ the installations to occur
> when nobody is supposed to be using the machine. I would still not recommend
> this practice on a server, though.
>
> The best practice for installing updates on a server is to use Option 3
> "Download and notify for installation", and then install the updates from
> the server console after all users have logged off. This may require you to
> establish a server maintenance time when no users are permitted to be logged
> onto the server.
>
>
> "Davy" <> wrote in message
> news:4AE94F9E-4BB4-4B35-B23B-...
> > First of all
> > thanks for your response
> >
> > Is it possible to configure automatic updates to install updates when no
> > one
> > is using the machine? Or do you mean that i should check if no one is
> > using
> > the terminal server and if not install the updates?
> >
> >
> > Davy
> >
> > "Lawrence Garvin [MVP]" wrote:
> >
> >>
> >> "Davy" <> wrote in message
> >> news:E394C9D1-CA4C-4BA8-89EC-...
> >> > I'd like to know if it is possible to configure microsoft (windows)
> >> > update
> >> > like:
> >> > "download updates for me and install but do not restart"?
> >>
> >> No.... install requires restart. It's a critical component of the
> >> installation process. This is so because the files are not actually
> >> 'installed' until a script runs at powerup, just before you get the login
> >> prompt.
> >>
> >> > I'd like to use this configuration on a terminal server. The server is
> >> > in
> >> > use 7 days a week, so it may not restart automaticly.
> >>
> >> You absolutely do /not/ want to do this on a terminal server.
> >>
> >> Terminal Servers have very specific procedural requirements for applying
> >> updates.
> >>
> >>
> >> > An other option would be to install updates if no one is using the
> >> > server.
> >>
> >> In fact, this is the /only/ appropriate option.
> >>
> >> > Thanks in advance
> >> > Davy
> >>
> >>
> >>
>
>
>

Davy wrote:

> I was looking for automated solution. That is what i'm
> doing now, but indeed it's probably the best solution.
>
Hi,

Another alternative is to use a script to install the updates available
to the computer from the WSUS server (kick it of e.g. from a scheduled
job).

Rob Dunn have created a nice VBScript that can do both detecting and
"install now" on a computer:

Windows Update Agent force script, email results
http://uphold2001.brinkster.net/vbsh...id=199&start=1

After the reboot needed after the updates, you should repeat the
operation to see if more updates are available.


The Windows Update Agent API used in the script is documented here:
http://msdn.microsoft.com/library/en...tal_client.asp

Several VBScript examples available at the MSDN web site as well:

Using the Windows Update Agent API
http://msdn.microsoft.com/library/en..._agent_api.asp

Tales from the Script, July 2005
http://www.microsoft.com/technet/com...ts/sg0705.mspx



--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx