Hi,
WSUS wouldn't sync yesterday so I was unable to get the patch Tuesday updates into SCCM.
I checked the log file below and found out this error about PatchMyPC.
WCM.log
Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:04:34 11548 (0x2D1C)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:12 11548 (0x2D1C)
Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:12 11548 (0x2D1C)
Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:12 11548 (0x2D1C)
Category Company:f3135976-b9d1-263d-917d-2e2eb43ff40a (Patch My PC) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:12 11548 (0x2D1C)
Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:13 11548 (0x2D1C)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 11/04/2018 21:06:13 11548 (0x2D1C)
After going through the SCCM SUP Product List I unchecked PatchMyPC and now it started syncing again.
We have been using PatchMyPC for quite some time so I'm unsure why this problem occurred yesterday...
Hi,
This usually happens when a Vendor / Product is enabled in SCCM, but that Vendor / Product no longer exist in WSUS. It's possible that you had updates published under the Patch My PC vendor / SCUP Updates product that are now all expired and got removed from WSUS during the cleanup.
This makes sense. The updates I published as PatchMyPC (PowerBI) were all expired.
WSUS shouldn't just completely fail to sync if it doesn't find updates from a product that "no longer exists" but that's not on you.
WSUS is just acting as you would expect... Very badly.
Consider this resolved!
Thanks,
Quote from: ronmanp on April 13, 2018, 06:18:24 AM
This makes sense. The updates I published as PatchMyPC (PowerBI) were all expired.
WSUS shouldn't just completely fail to sync if it doesn't find updates from a product that "no longer exists" but that's not on you.
WSUS is just acting as you would expect... Very badly.
Consider this resolved!
Thanks,
Agreed, that it shouldn't just fail to sync in this scenario :).