Patch manager and Server 2016

Question

I've migrated all my wsus servers and patch manager servers to 2016......Now for the issue:

All of my 2016 servers won't update via wsus, wsus and patchmanager see them, but they aren't reporting correctly, nor are they patching via wsus.  When I use patchmanager  to query the server I get a 2084500c error.  which also happens to be the same error I get when I manually run windows update on a 2016 server.  I've googled this extensively, and am running up against walls.  Also, all machines have been manually patched, but still aren't reporting correctly.   Oh just a note, wsus on 2016 patches everything correctly except 2016.  (Win7, win10, Server 2008 r2, 2012)....

Any one have any ideas???

dang · Answer

Appears it's a solarwinds issue, and their "hot fix" fixed it:

SolarWinds
 Patch Manager 2.1.5 Hotfix 1

====================================================================================

This hotfix addresses the following issues:

* The Discovery task for subnets cannot retrieve MAC addresses from a machine

located in other subnets. To resolve this issue, this hotfix adds an

additional WMI request to the Discovery task that uses credentials to retrieve

MAC addresses from machines located in other subnets.

* The Windows Firewall tab does not work correctly for systems running Microsoft

Windows Server
 2016 (build 1709). To resolve this issue, this hotfix enables

Patch Manager to retrieve firewall information without errors for Patch

Manager servers running Windows Server 2016 (build 1709).

* "WMI providers are not installed" error when viewing the Windows Update History

on computers running Windows 10 and Windows Server 2016. This hotfix resolves

this issue and includes a new version of Patch Manager WMI providers.

* The Windows Update log cannot be viewed within Patch Manager. This issue is

caused by changes in the Windows Update log on computers running Windows 10

and Windows Server 2016. This hotfix resolves this issue.

jrouviere · Answer

I don't see a reference to that error, are you able to provide a screenshot of what you're seeing or a log snippet?

Shocko is right, you'll want to isolate Patch Manager from WSUS for now. One thing that comes to mind is checking online for updates. You don't have to install from Microsoft, but are you able to click the link for "Check online for updates from Microsoft Update"?

It should be underneath the regular check for updates button, this is assuming the servers can reach out anyway.

It's another option besides having to look at re-deploying WSUS entirely.

Additionally, re-reading your post, if you're seeing the same error when checking for Updates locally or when using Computer Explorer from Patch Manager that might indicate a communication error such as with the certificate or firewall.  Having some more information about the environment could help as Patch Manager will default to WMI using the Patch Manager Client Components if you don't have the agent installed.

dang · Answer

Done all the above on the 2016 servers (which also run WSUS) same error as before may end up rebuilding the wsus server to see if that helps the situation.......