|
Posted by Roger Abell [MVP] on September 22, 2005, 10:12 pm
If you were Registered and logged in, you could reply and use other advanced thread options
Yes, you can force the reboot when one is needed.
Also notice that with WSUS you can both provide a
schedule by which time the client is to have completed
install of a patch, and also, you can have patches that
do not interrupt services or require reboot installed
immediately (rather than waiting for next scheduled
install time).
Now, back to your point, with WSUS you require
installation in the same way as was done in SUS.
You set the Configure Automatic Updates to 4, and
you do not allow users to receive the update notifications
that let them delay. These settings are all well-covered
in the WSUS deployment paper.
Also, you are correct, if an install has been deferred,
then new patches are not noticed until the deferred has
been allowed to complete.
> We've used SUS for quite some time now to distribute updates. I am in the
> process of moving to WSUS and for the most part things seem to be working
> well. One nice feature is the ability to see if a user has taken on the
> patches. I know for a fact that currently many users blow past the install
> and/or reboot prompts that they receive when SUS is trying to do its
> thing.
> Ultimately I believe that we end up with machines that are not properly
> patched. In WSUS it's nice to be able to get a report on the status of
> those
> machines, but is there a way to force that PC to reboot remotely so that
> all
> the patches are properly done?
| 
XML site map