Article ID: 945536 - Last Review: December 11, 2007 - Revision: 1.0 Client computers can no longer synchronize with Windows Server Update Services after you import many third-party product updates
On This PageSYMPTOMSAfter you import many locally-published, third-party product updates in Microsoft Windows Server Update Services (WSUS), client computers can no longer synchronize with WSUS. You experience this issue after you import many third-party updates that have distinct product names or that have distinct vendor names. WSUS provides APIs to import and to manage locally-published updates. However, WSUS does not provide a user interface (UI) to import or to manage these updates. Therefore, you are more likely to experience this issue when you use a tool that uses the WSUS APIs to manage locally-published updates. These tools include the following:
CAUSEThis issue occurs if too many categories are published in WSUS. When you import a catalog of third-party updates into WSUS, WSUS uses the product name together with the vendor name to create a category. This category is associated with a particular update. During a synchronization operation between a client computer and WSUS, all the locally-published categories are sent to the client computer for evaluation. If too many distinct categories are published, the synchronization process fails. RESOLUTIONTo resolve this issue, you must perform the following operations:
Step 1: Delete the update metadataMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.Run the following scripts to delete all the updates together with the references to the catalog that was originally imported. Note These scripts require Windows PowerShell. For more information about how to obtain Windows PowerShell, see the "More Information" section. Script 1Script 2Note This script deletes all the updates that belong to a particular category.Step 2: Unwedge client computersTo unwedge client computers that can no longer synchronize with WSUS, you must cause each client computer to clear the cached update metadata. One method to cause a client computer to clear the cached update metadata is to change the ID of WSUS. To do this, use one of the following methods.Method 1: If you use the default instance of Microsoft SQL Server on the local computerBy default, WSUS uses the default instance of SQL Server on the local computer. In this scenario, enter the following command to set a new WSUS ID:%programfiles%\Update Services\Setup\ExecuteSQL.exe -S %Computername%\MICROSOFT##SSEE -d "SUSDB" -Q
"UPDATE dbo.tbConfigurationA SET ServerID = newid()"
Method 2: If you use a named instance of SQL ServerIf you use a named instance of SQL Server, enter the following command:%programfiles%\Update Services\Setup\ExecuteSQL.exe -S ServerName\InstanceName -d "SUSDB" -Q
"UPDATE dbo.tbConfigurationA SET ServerID = newid()"
Step 3: Delete update contentNote This step is an optional step.Step 1: Delete the binary files from the content folderThe content folder contains a .cab file that contains the published binary files. To delete the files from the content folder, follow these steps:
Step 2: Delete the binary files from the package folderThe package folder contains binary files that are not packaged in one or more .cab files. To delete the files from the package folder, follow these steps:
MORE INFORMATIONWSUS provides APIs to allow for the distribution of updates from sources other than Microsoft Update. However, WSUS does not provide a user interface (UI) to distribute these updates. You can use the IUpdateServer.DeleteUpdate API to remove the update metadata for these kinds of updates. However, the corresponding update content remains in the package folder. For more information about how to obtain Windows PowerShell, visit the following Microsoft Web site: http://msdn2.microsoft.com/en-us/library/bb905330.aspx
(http://msdn2.microsoft.com/en-us/library/bb905330.aspx)
For more information about local publishing in WSUS, visit the following Microsoft Web site:http://msdn2.microsoft.com/en-us/library/bb902470.aspx
(http://msdn2.microsoft.com/en-us/library/bb902470.aspx)
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
