Following the previous success of upgrading my DC, and Hyper-V servers I decided that it was time for my server that hosts the "Windows Server Update Services" role to be updated.
How did it go? In a nutshell... BLAH!
After the upgrade completed, WSUS was logging errors in the system log about not being able to connect to it's web sites. The reason became very obvious to me after I installed the IIS Management Console and had a look.... the WSUS application pool was not there, and neither was there any of the WSUS content in the "Default Web Site".
After a bit of searching on Google & Technet and finding nothing, I decided to uninstall the WSUS & IIS roles & then re-install.
Uninstall was easy ... just made sure to leave behind the downloaded updates, database, etc... and reboot.
Re-install was failing, saying that updates could not be found and suggesting that I might have a network connectivity issue. Well I didn't have a network connectivity issue, but I figured it was trying to use the WU client to connect to the MS updates site, and seeing how my WSUS Group Policy on the domain was pointing all systems to my WSUS server there was little wonder that it could not find any updates.
I decided the simplest and most certain way to revert the WU client to use the MS updates online was to change the "Specify intranet Microsoft update service location" to "Disabled" .... doing this instead of "Not Configured" ensured that it was actually disabled. I didn't really care if other systems picked up the policy in the short time it was going to be active.
Once I refreshed the policies on the WSUS server ("gpupdate /force"), and restarted the WU client service the installation of the WSUS role was successful - made sure to point to the original database & downloaded updates location... and everything was back to normal. PHEW!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment