Has anyone come across an WSUS API mismatch with the server publishing verification wizard when the publishing server is Windows 2008 R2 and the WSUS server is Windows Server 2012?
Regards
Mike
Hi Mike,
This error is the result of the fact that Windows 2008 R2 cannot install the WSUS console for v6. As a workaround you can install an automation server on the WSUS server, and then create an automation server routing rule to push all WSUS actions to the auto server on the WSUS server.
That's great. I'll take a look on Tuesday when I'm back in the office. Do you have documentation links on how do install the automation server and configure it?
Sent from my iPad
Sure. Here's a write up that contains some more specific information on how to implement this workaround.
http://thwack.solarwinds.com/community/solarwinds-community/geek-speak_tht/blog/2013/01/29/managing-wsus-on-windows-server-2012-with-patch-manager-v185
Hi David,
I attempted to install the automation server on the WSUS server this morning and messed up my database so restored from backup. From what I understand the server did not register correctly and it created two user preferences called 'Default' which in turn caused me issues with the credential ring.
My next step is to talk with support and try installing the service again.
