Open Server Manager and remove Web Server (IIS) and Windows Server Update Services roles.When asked for, leave the check boxes clear for the removal of WSUS database, log files and downloaded update files. During the installation of WSUS 3.0 SP2, the Server Manager on Windows Server 2008 [R2] actually looks for Windows Server Update Services 3.0 SP2 Dynamic Installer for Server Manager [x64 Edition] (KB972493), but the update server is normally configured to receive updates from itself, and there’s no itself—functioning at least—for the moment. I had checked some addtional boxes, which overloaded the list (I think).I have since removed those from the synchronization list but no I get Error: Connection error. This doesn't work, nor does clearing out the WSUS snap-in config file under APPDATA Anyone else get this problem and resolve it?
I updated the settings in the domain GPO to point to the new server, »v_srv30. I also migrated our help desk system to the same server. What I didn't realize was that WSUS still used port 80 for communications even with 8530 set up (at least according to what I've read) for reporting client status.
I have recently set up two new servers on our domain, labelled CADCS001 and CADCS001.
These servers are intended to be almost identical aside from the hostname and have been set up to be as similar as possible.
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.