Following a recovery of our primary site (due to upgrading to Server 2012) all appears to be working ok apart from none of our secondary sites are updating their SUP. The link state is 'Active' but the last sync attempt and Catalog version are all pre-recovery (ie not up to date). The wsyncmgr.log file on one of the affected secondary sites has very little information - doesn't look like its even tried to check in.

Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 28/07/2015 20:33:35 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 28/07/2015 21:33:35 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 28/07/2015 22:33:35 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 28/07/2015 23:33:35 3132 (0x0C3C)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 00:00:08 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 01:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 02:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 03:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 04:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 05:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 06:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 07:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 08:00:13 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 09:00:14 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 10:00:14 3132 (0x0C3C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 11:00:14 3132 (0x0C3C)
SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 3256 (0xCB8).              SMS_WSUS_SYNC_MANAGER 29/07/2015 11:46:06 1372 (0x055C)
Log level 2                                      SMS_WSUS_SYNC_MANAGER 29/07/2015 11:46:06 3256 (0x0CB8)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 11:46:23 3256 (0x0CB8)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 12:20:15 3256 (0x0CB8)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 12:20:25 3256 (0x0CB8)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 13:20:30 3256 (0x0CB8)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 13:39:18 3256 (0x0CB8)
Thread terminated by service request. SMS_WSUS_SYNC_MANAGER 29/07/2015 14:07:06 3256 (0x0CB8)
SMS_EXECUTIVE started SMS_WSUS_SYNC_MANAGER as thread ID 3356 (0xD1C).              SMS_WSUS_SYNC_MANAGER 29/07/2015 14:10:20 2024 (0x07E8)
Log level 2                                      SMS_WSUS_SYNC_MANAGER 29/07/2015 14:10:20 3356 (0x0D1C)
Wakeup by SCF change                    SMS_WSUS_SYNC_MANAGER 29/07/2015 14:10:40 3356 (0x0D1C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 15:10:45 3356 (0x0D1C)
Wakeup for a polling cycle                SMS_WSUS_SYNC_MANAGER 29/07/2015 16:10:45 3356 (0x0D1C)

If anyone can point me in the right direction it would be really appreciated!

The reasons seems to be the version of the catalog. It's 2 on the primary, but 80 on the secondaries.

Thanks Torsten,

Yes, the WSUS db on the primary wasn't kept unfortunately and following the recovery we had to re-configure it which seems to have started the catalog numbering again.  Will I need to remove and re-install the SUP role from each of the secondary sites to resolve this or is there an easier way to reset them?

Cheers,
Alastair

Hi,

Have you resolved this problem?

Hi Joyce,

No, this is still not resolved. I'm trying to open a support case however having issues with our Software Assurance so any comments on how to resolve this would be much appreciated.

Thanks

After I moved our primary site to another server using the database backup/restore method we had issues with clients scanning and reporting old metadata. This link helped sort the problem out: http://www.windows-noob.com/forums/index.php?/topic/9837-not-reporting-software-update-compliance/ It's not exactly what you're looking for but you can see how to change the content version of the WSUS database at least.