Rebooting after patching

[Guest]

We have several machines that keep rebooting before they get to the logon prompt. They are SP 2 machines that just had the updated Windows Auto Updater installed so that they can get SUS updates via policy. The SUS log shows that they initiated Downloads and Self Updates before the problems began. Does this means that they went to Microsoft.com? If so, why did they not use the policy that other machines (SP4) are successfully using in the same OU? The policy states to use our local SUS server for updates. We removed MS04-011 from the approval list about 2 days before these entries appeared. I am wondering if these SP2 machines went to Microsoft.com to get updates and installed MS04-011, which may be causing the failure to boot. Ideas?

 

[Marina Roos [SBS-MVP]]

If those machines were on SP2 only, they might have been hit with the
blastworm. Open Taskmanager and look for the msblast.exe, mspatch.exe or
teekids-proces. Kill it and go to www.sophos.com\support\disinfection to get
the removaltool. After that install ms03-039 from microsoft to prevent from
happening again. And run Windows update again.

--
Regards,

Marina
Microsoft SBS-MVP

We have several machines that keep rebooting before they get to the logon

prompt. They are SP 2 machines that just had the updated Windows Auto
Updater installed so that they can get SUS updates via policy. The SUS log
shows that they initiated Downloads and Self Updates before the problems
began. Does this means that they went to Microsoft.com? If so, why did they
not use the policy that other machines (SP4) are successfully using in the
same OU? The policy states to use our local SUS server for updates. We
removed MS04-011 from the approval list about 2 days before these entries
appeared. I am wondering if these SP2 machines went to Microsoft.com to get
updates and installed MS04-011, which may be causing the failure to boot.
Ideas?