Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

When does wsyncmgr start the synchronization process?


Asked by Baker Lyons on Dec 12, 2021 FAQ



The synchronization process on a child primary site or secondary site performs the following steps: When the sync notification that's sent by the parent site arrives in the WSyncMgr.box folder through file replication, WSyncMgr wakes up and starts synchronization. The following are logged in WsyncMgr.log:
One may also ask,
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. All additional SUPs are configured as replicas of the first SUP.
Next, During the software update synchronization process on the top-level site, the software update configuration items are replicated to child sites by using database replication. At the end of the process, the top-level site sends a synchronization request to the child site, and the child site then starts the WSUS synchronization process.
Likewise,
We can check wsyncmgr.log for more information, it records details about the software update sync process. The sync time out errors are usually caused by the network connections or something wrong between your WSUS instance and the Microsoft Update. Please remember to mark the replies as answers if they help.
Besides,
When there is a remote Internet-based SUP, WSUS Synchronization Manager starts the synchronization process for WSUS running on the remote site system. The WSUS servers on the other SUPs are configured as replicas of WSUS running on the default SUP at the site.