Auto Update Client Behavior

N

Nick

Can anyone confirm or deny that admin users on
workstations part of an AD that have been configured via
Group Policy to schedule automatic updates from an SUS
server...that it actually works? It seems that the
default behavior for the Automatic Updates client when
you are an admin is to wait for user intervention
regardless of what the policy dictates. Admin users get
the balloon message from the systray icon, whereas
regular users do not. Therefore, admin users who stay
logged into the machine overnight and never reboot do not
receive the updates. Is my theory correct or does the
scheduled update occur anyway? In light of the recent
RPC vulnerability, I hope that my theory is wrong.

Thanks in advance for your responses.
 
M

MadDHatteR

I am reasonably sure that whoever is logged in will be logged out and the
computer rebooted (if necessary to install the patches), whether they are
admin or not. I haven't tested this in a long time, so I might not remember
correctly. The obvious solution if you are concerned, is to scan your
network to make sure there are no vulnerable machines. Microsoft recently
released a program that will scan your network for KB823980-vulnerable
machines.

\\ MadDHatteR
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

SUS group policy 4
Disable Windows Update 1
Group Policy for Windows Automatic Update 5
Windows Update 2
SUS OU? 7
Group Permissions not working on client computers 5
SUS auto-restart 2
SUS Automatic Updates 2

Top