There are hundreds of results on Google with many pointing to Technet but I still can't get this issue resolved.
Servers are all 2008 R2 Enterprise and clients are all Windows 7 Pro/Ent x64.
It occurred to me that perhaps the new SCCM is overriding the domain policy.
To fix that, I tried changing the domain policy to point the workstations to the sccm server hoping they would report to that server for updates. Even though the clients show up, the status for all of them reads "Not updated yet".
But deep inside the WSUS server, things are a mess: The WSUS server is the only computer that can get updates from itself, it cannot communicate with clients, and after a few days, all computers—except for the WSUS server itself—are listed as .
Visiting Event Viewer Custom Views for Server Roles, or hitting the Roles’ list collapse sign (plus sign inside the square) on Server Manager and looking into each role’s events, you’d be surprised to see there’s no recent events or perhaps no events at all listed for Web Server (IIS).
I didn't migrate the database but set up a new server (new updates, etc). Maybe there was something cached on the client end in regards to updates?
I've remoted to some of the clients and forced them to report to WSUS, but after a short while, it still says it hasn't reported.
I know I'm missing something simple since this has to be a somewhat common setup for other small and medium organizations.
An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.
To me, the subversive update number is not clear yet.