B
Bill
I've had my sus policy working for about a year now, but
recently some users who have been removed from the local
admin group of their machines, have had the no option
during the reboot option, grayed out. I've got the 'no
auto-restart for scheduled automatic updates installation'
enabled and as i've mentioned hadn't had any problems.
I've revisited some of the documentation regarding SUS,
but didn't see any mention of the user having to be part
of the local admin group in order to receive the no option
during the reboot phase, but did find this bit from
http://www.microsoft.com/technet/security/guidance/secmod19
7.mspx
"For users without local administrator rights, the update
will install in the background at the scheduled time.
These users can only delay a computer restart, if the No
auto-restart for scheduled Automatic Updates installations
policy setting has been enabled."
by "delay" I would imagine that meaning they could say no,
but on these users machines it counts down and reboot
automatically.
thx,
Bill
recently some users who have been removed from the local
admin group of their machines, have had the no option
during the reboot option, grayed out. I've got the 'no
auto-restart for scheduled automatic updates installation'
enabled and as i've mentioned hadn't had any problems.
I've revisited some of the documentation regarding SUS,
but didn't see any mention of the user having to be part
of the local admin group in order to receive the no option
during the reboot phase, but did find this bit from
http://www.microsoft.com/technet/security/guidance/secmod19
7.mspx
"For users without local administrator rights, the update
will install in the background at the scheduled time.
These users can only delay a computer restart, if the No
auto-restart for scheduled Automatic Updates installations
policy setting has been enabled."
by "delay" I would imagine that meaning they could say no,
but on these users machines it counts down and reboot
automatically.
thx,
Bill