Why SUS behavior inconsistent?

[Kevin]

Hi

Can anyone shed some light on this?

I pushed out updates last night that mandated a reboot, and I get three
different behaviors on the clients:
a) Updates were installed automatically and client rebooted
b) Updates were downloaded but not installed, icon in the sys tray awaiting
installation
c) Prompt on client screen asking if you would like to reboot or not

All clients have the exact same Registry settings, and all are logged on as
Admin equivalent accounts.

I setup an SUS server before to push out Windows patches, and all of the
clients have the same settings:
"Keep my computer up to date...." is checked
"Automatically download the updates, and install them on the schedule that I
specify"
Every day at 7:00pm

I entered the Registry keys to set these settings on every client, as well
as grey it out so the users
cannot change them. Why did it work flawlessly for a couple weeks, and now
it is all over the place?
I have lost faith that this is a reliable and consistent means of sending
out updates.

Thanks,
Kevin

 

[Torgeir Bakken (MVP)]

Hi

Fyi, there is a separate newsgroup for SUS:

microsoft.public.softwareupdatesvcs

news://msnews.microsoft.com/microsoft.public.softwareupdatesvcs

URL to the group softwareupdatesvcs for those who uses the Web
interface to access the newsgroups:
http://www.microsoft.com/windowsser...t.mspx?dg=microsoft.public.softwareupdatesvcs

A Web site about SUS with a FAQ and a SUS forum:
http://www.susserver.com/

More Web sites:
http://www.cites.uiuc.edu/sus/faq.html
http://www.faqshop.com/sus/default.htm