Some computers do not receive updates from the WSUS server
Technical update: August 1, 2008Microsoft has released a Microsoft security advisory about this issue for IT professionals. The security advisory contains additional security-related information. To view the security advisory, visit the following Microsoft Web site:http://www.microsoft.com/technet/security/advisory/954960.mspx (http://www.microsoft.com/technet/security/advisory/954960.mspx) On This PageSYMPTOMSYou use Microsoft Windows Server Update Services (WSUS) 3.0 to deploy software updates and hotfixes to computers that are in your organization. However, some computers do not receive updates from the WSUS server. This problem occurs if the computers have Microsoft Office 2003 or components of Office 2003 installed.
Note This problem affects Microsoft Windows Server Update Services 3.0 and Windows Server Update Services 3.0 Service Pack 1 (WSUS 3.0 SP1). However, in some circumstances, the following products may also be affected:
When this problem occurs, a message that resembles the following message is logged in the Automatic Updates log file (%windir%\WindowsUpdate.log) on the affected computer: This message is logged during the detection phase. Also, a message that resembles the following message is logged in the WSUS log file (%ProgramFiles%\Update Services\Log Files\SoftwareDistribution.log) on the WSUS computer: To locate this message, search the WSUS server for the ID that is obtained from the client log. CAUSE
This problem occurs because a recent revision to a Microsoft Office 2003 Service Pack 1 (SP1) update causes some WSUS 3.0 servers to incorrectly synchronize the revised update with the update’s approvals. When the affected client computers communicate with such a server, the Web service is unable to process the approvals. Therefore, the detection is unsuccessful.
RESOLUTION
To resolve this problem on a server that is running WSUS 3.0 SP1, install update 954960.
Note If you are using the RTM version of WSUS 3.0, refer to the workaround in the "Workaround" section to resolve this issue. If you use the RTM version of WSUS 3.0 and if you decide not to implement the workaround, visit the following Microsoft Web site for more information about how to upgrade to WSUS 3.0 SP1: http://go.microsoft.com/fwlink/?linkid=93750 (http://go.microsoft.com/fwlink/?linkid=93750)
The following files are available for download from the Microsoft Download Center: Download the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 (KB954960) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=6AA8A49D-170C-4077-8B9B-61F7BF5A1281) Download the Update for Windows Server Update Services (WSUS) 3 Service Pack 1 for x64-based Systems (KB954960) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=DBDCDB25-1097-47F4-8FD1-B1246D13C5F8)Release Date: August 1, 2008 For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 (http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
WORKAROUND
To resolve this problem, we recommend that you install update 954960. However, to work around this problem if you cannot install update 954960, reset the approvals to a consistent state on the WSUS server. To do this, follow these steps on the WSUS Administration Console:
wuauclt.exe/detectnow Then, examine the WindowsUpdate.log file to verify that the synchronization is successful. You may have to run detection two times. This is because some customers have reported that the first synchronization fails but that successive synchronizations succeed.
Note If you have a hierarchy of WSUS servers, you must follow these steps on each server. Start with the top-level server. If one of the servers is a replica child server, you must first change it to be autonomous. Follow the previous steps, and then change the autonomous server back to a replica child server. You can do this in the Options/Update Source and Proxy Server dialog box. MORE INFORMATIONKnown issues with this update
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
| Article Translations
|

Back to the top
