I have a client that recently migrated and reverted changes to their WSUS infrastructure. After that, client is unable to push all updates to all computers. After further investigation, I discovered that GPO is properly applied to all workstation using port 8530, but somehow the computers still make a reference to old different port number used in the past.
I was able to identify that the policy is properly applied to computers, however for some reason, there is a registry key in all computers that makes reference to a old port number server . Please see details below, and let me know if I have to reinstall WSUS, and choose port 80 or if I can modify exiting IIS binding settings to use same port that is being used by the GPO.
I would like to summarize all troubleshooting steps taken today regarding the existing WSUS infrastructure at CompanyAcme
Telnet from testing machines to your WSUS server on port 80 and 8530 passed successfully. Link http://technet.microsoft.com/en-us/magazine/gg153542.aspx
Opened a Web browser on the client and go to http://
Manually deleted the existing WSUS GPO policies in AD.
Force replication among all DCs
The following settings were applied to WSUS console; Synchronization Schedule, Automatic Approvals, and Computer container to use Group Policy or registry settings on Computers
Deployed a new GPO named WSUS Update policy; only two settings were configure [Configure Automatic updates and specify intranet Microsoft Update service location to locate your current WSUS server on port 8530]
Link GPO to a testing OU. Policy is Link enabled and force. We did block inheritance over test OU to prevent any issues with other policies, and computers lost RDP access. Block inheritance was disabled to rollback changes
Force replication in AD
From two test computers, we ran gpoupdate/force and each computer was rebooted.
New GPO was correctly applied to computers, however all computers still make a reference to a different port used on a previous WSUS upgrade/deploy server[port 8xxxx].
Once your machines will be able to look at current WSUS server and the correct port, patches will be deploy properly.
You mentioned earlier that WSUS for Windows 2012 server was deployed in the past, then realized system center essentials is not compatible with Windows 2012 R2 server and SCCM is required, all changes were reverted and did the upgrade from Windows 2003 to Windows 2008.
Please see articles below, and see if that might help