Contents
How to troubleshoot software update synchronization issues?
The first step in troubleshooting synchronization issues is to verify that the following prerequisites are met: Verify that Prerequisites for software updates in Configuration Manager are met. When you install the software update point on a remote site system server, the WSUS Administration console must be installed on the site server.
What is the value of the synchronization error?
If the same error was not encountered on a previous run, this value is 0. The synchronization-errors/import-error/date-occurred element is the date, in Coordinated Universal Time (UTC), when this instance of the error occurred.
How to troubleshoot WSUS software update synchronization?
Verify that the Default website or WSUS Administration website is running on the WSUS server. Check the Update Source settings in the WSUS console on the software update point site system server. These settings are set automatically by WSUS Configuration Manager (WCM). If these settings don’t match, review WCM.log.
When to escalate to a full synchronization?
A synchronization will escalate to a full synchronization if there are configuration changes that require a full synchronization, such as: switching to a different default SUP, changes in the subscription, changes in the supersedence mode or window.
How to synchronize Windows Server with Windows Update?
At the top-level site you can specify a synchronization source other than Microsoft Update, such as an existing Windows Server Update Services (WSUS) computer that’s not in the Configuration Manager hierarchy. The synchronization process at the top-level site performs the following steps:
How does secondary site start software update synchronization?
The secondary site starts the software updates synchronization with the parent primary site. The secondary site’s SUP is configured as a replica of WSUS running on the parent site. The following is logged in WsyncMgr.log:
How to track software update synchronization in SQL Server?
The following is logged in SMSProv.log: In SQL Server Profiler trace: In SMSDBMON.log: In WSyncMgr.log: WSyncMgr then reads the list of software update points (SUPs) from the site control file (SCF). WSyncMgr first synchronizes the SUP that was installed as the first SUP in the site and then synchronizes the remaining SUPs.