WSUS CatelogVersion Mis-Match in ConfigMgr after Restore

After WSUS Database (SUSDB) restore, sometimes Software Updates will no longer install on clients. UpdatesDeployment.log will show “Total Actionable Updates = 0”
You can also find missing updates based on WSUS Catalog:
“Get-WmiObject -Query “Select * FROM CCM_UpdateStatus” -NameSpace “root\ccm\SoftwareUpdates\UpdatesStore” | where {$_.status -eq “Missing”} | Select Title, Status”
It will show, lots of updates are missing. But SCCM agent won’t recognize these updates as applicable.
We can find out last CatalogVersion with the following SQL command:
“Select ContentVersion, LastSyncStateTime from dbo.Update_SyncStatus”
OR
“;WITH XMLNAMESPACES ( DEFAULT ‘http://schemas.microsoft.com/SystemsCenterConfigurationManager/2009/07/10/DesiredConfiguration’)
Select MAX(CI.SDMPackageDigest.value(‘(/DesiredConfigurationDigest/SoftwareUpdateBundle/

ConfigurationMetadata/Provider/Operation[@Name=”Detect”]/Parameter/Property[@Name=”MinCatalogVersion”]/@Value)[1]’, ‘int’)) MinCatalogVersion
FROM [CI_ConfigurationItems] as CI
WHERE CIType_ID = 8”
Result:

But CatalogVersion in SCCM Console shows different version:

How to Fix this issue?
To fix this issue, we need to fix values on two different places:
+ Update_SyncStatus database
+ Registry Fix for CatalogVersion
To fix “Update_SyncStatus”, we need to set “ContentVersion” value to match latest version. Use following command to update database:
“Update Update_SyncStatus Set ContentVersion = 1245 from Update_SyncStatus”

To fix CatalogVersion in Registry, we need to fix following values:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER]
“ContentVersion”=1245
“SyncToVersion”=1245
“LastAttemptVersion”=1244

After implementing above fix, we need to run “Synchronize Software Updates” from SCCM Console. Once synchronization will complete, the Catalog should have latest version.
After confirming everything, trigger “Machine Policy Retrieval & Evaluation Cycle” on one of the client to get new configurations. Trigger “Software Updates Deployment Evaluation Cycle” & “Software Updates Scan Cycle”. After few minutes, you should be able to see new or applicable updates on Software Center.

About the Author

Ajaz ur Rehman

Ajaz ur Rehman

I've been working as SCCM Administrator since 2012 that includes Server Administration as well. I've managed from Small to Enterprise Level environments. I love to troubleshoot complex problem. I've created many scripts for business to automate jobs and many reports for businesses to sort out software inventories and licensing issues. Everyday learning something new in IT.

Leave a Reply

Your email address will not be published. Required fields are marked *