Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, March 29, 2019 3:29 PM
My synchronization times have skyrocketed since going to 1810 with HFRU and enabling HP and Dell third party updates. I expected the first synchronization to be lengthy but not subsequent synchronizations. I have Primary Site server with WSUS database on remote SQL.
I wouldn't think that it would take so long to add 6 new definition updates to the database. All clients contact downstream servers and there are no apparent resource constraints on the primary site server. WSUS maintenance occurs daily using "Adamj Clean-WSUS" process and "Run WSUS cleanup after synchronization" is also enabled SUP.
1. What is happening under the covers during the "Calling ImportUpdatesFromCatalogSite" step?
2. What would cause synchronization for 6 updates to take approximately 1hr 45 min?
Approximately 1 hour 45 minutes - Calling ImportUpdateFromCatalogSite for driver update GUIDs:
Sync Catalog Drivers SCF value is set to : 1 SMS_WSUS_SYNC_MANAGER 3/29/2019 6:06:51 AM 19308 (0x4B6C)
Calling ImportUpdateFromCatalogSite for driver update GUIDs SMS_WSUS_SYNC_MANAGER 3/29/2019 6:06:51 AM 19308 (0x4B6C)
SyncGracePeriod not set, use default 120000 SMS_WSUS_SYNC_MANAGER 3/29/2019 7:45:49 AM 19308 (0x4B6C)
Sleeping 120 more seconds for WSUS server sync results to become available SMS_WSUS_SYNC_MANAGER 3/29/2019 7:45:49 AM 19308 (0x4B6C)
Set content version of update source {8CC6C6F3-8209-4D62-B631-53722E58BC45} for site P01 to 3521 SMS_WSUS_SYNC_MANAGER 3/29/2019 7:47:50 AM 6176 (0x1820)
Approximately 1 hour 45 minutes - sync: SMS synchronizing updates:
sync: SMS synchronizing updates, processed 0 out of 6 items (0%) SMS_WSUS_SYNC_MANAGER 3/29/2019 7:47:59 AM 5196 (0x144C)
Synchronizing update 9d736f97-94fb-4060-98e6-3d5208e8ebec - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.291.649.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 7:48:00 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 1 out of 6 items (16%), ETA in 00:28:55 SMS_WSUS_SYNC_MANAGER 3/29/2019 7:53:45 AM 5196 (0x144C)
Synchronizing update db4d7737-b59f-4aaa-aa3d-01b288cbb363 - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.291.649.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 7:53:45 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 2 out of 6 items (33%), ETA in 00:47:12 SMS_WSUS_SYNC_MANAGER 3/29/2019 8:11:34 AM 5196 (0x144C)
Synchronizing update d6b9e31d-66ae-4f31-a0c9-ebaf7bf87dad - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.291.655.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 8:11:35 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 3 out of 6 items (50%), ETA in 01:08:04 SMS_WSUS_SYNC_MANAGER 3/29/2019 8:56:02 AM 5196 (0x144C)
Synchronizing update 80169554-b8e0-4eba-a4d1-6bce428e0672 - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.291.655.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 8:56:02 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 4 out of 6 items (66%), ETA in 00:46:49 SMS_WSUS_SYNC_MANAGER 3/29/2019 9:21:36 AM 5196 (0x144C)
Synchronizing update df2f2151-c386-422d-84c6-a8b1bfe7c6e0 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.291.661.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 9:21:36 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 5 out of 6 items (83%), ETA in 00:19:41 SMS_WSUS_SYNC_MANAGER 3/29/2019 9:26:25 AM 5196 (0x144C)
Synchronizing update 39db6ac8-fdf4-4ffe-b043-aadfda30d35a - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.291.661.0) SMS_WSUS_SYNC_MANAGER 3/29/2019 9:26:25 AM 5196 (0x144C)
sync: SMS synchronizing updates, processed 6 out of 6 items (100%) SMS_WSUS_SYNC_MANAGER 3/29/2019 9:46:04 AM 5196 (0x144C)
sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 3/29/2019 9:46:04 AM 5196 (0x144C)
Any thoughts or feedback is greatly appreciated.
Thank you!
All replies (7)
Friday, March 29, 2019 4:05 PM
Have you cleaned up your WSUS DB including reindexing and rebuilding statistics recently?
Have you reindexed and rebuilt the statistics in your ConfigMgr DB recently?
Is your WSUS DB hosted in a SQL instance or WID?
Have you reviewed the overall performance of the system's hosting the WSUS DB, the ConfigMgr DB, and the site server?
Jason | https://home.configmgrftw.com | @jasonsandys
Friday, March 29, 2019 6:30 PM
Hi Jason, I appreciate the quick response and here are the answers to your questions.
1. Reindexing and rebuilding of WSUS DB is performed regularly.
2. Need to verify with SQL Team to determine last time it was done on SCCM DB.
3. WSUS DB is hosted in SQL instance.
4. Overall performance of servers that host SCCM and SQL health aren't showing any red flags.
It isn't clear to me what is actually being done during the steps. Do you think the delays are a result of congestion in SCCM DB? Would verbose logging provide additional information?* *
Please let me know when you get the chance or if there are any other recommended items to check.
Thank you - Rob
Friday, March 29, 2019 6:53 PM
To my knowledge, this is all SQL work at this point. Perhaps getting a DBA involved to help monitor the process on the DB side to see what is specifically taking so long.
Jason | https://home.configmgrftw.com | @jasonsandys
Friday, March 29, 2019 7:20 PM
Sounds like a plan. Thank you Jason!
I will provide an update when I have additional information.
Friday, June 14, 2019 2:26 PM
Rob, have you solved the problem?
Friday, June 14, 2019 2:40 PM
How about Cleanups?
Try running the execute spGetObsoleteUpdatestoCleanup
See what number you come back with.
Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro
Friday, June 14, 2019 2:47 PM
The SQL Team tuned the remote database and we added additional Memory and Processor to Virtual SQL Server which has brought the synchronization time down to about 90 minutes which is acceptable to us.
Thank you - Rob