This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
I get this question every once in a while so I thought I’d share what I learned here. We have two options to upgrade WSUS SP1 to SP2:
1. As an offer from Microsoft Update
KB972455 is the WSUS SP2 update. If you want to see SP2 in the list of updates make sure you have selected Service Packs in the Classification list. Custom view has been added for Service Packs in the below screenshot.
For WSUS SP2 to be offered on the server running WSUS SP1, the following conditions should not be true:
1. SQL is running remote
2. Server is running MOM version of SCE
We are checking for the following registry keys to know if above conditions are met. If SP2 is not offered on the server running SP1 we may need to install SP2 manually in these scenarios.
“HKEY_LOCAL_MACHINE" Subkey="Software\Microsoft\Microsoft Operations Manager\3.0\Setup" Value="ServerVersion" Comparison="EqualTo" Data="6.0.1251.0"
"HKEY_LOCAL_MACHINE" Subkey="Software\Microsoft\Microsoft Operations Manager\3.0\Setup" Value="ServerVersion" Comparison="EqualTo" Data="6.0.5000.0"
"HKEY_LOCAL_MACHINE" Subkey="Software\Microsoft\Update Services\Server\Setup" Value="SqlInstanceIsRemote" Comparison="EqualTo" Data="1"
"HKEY_LOCAL_MACHINE" Subkey="Software\Microsoft\System Center Essentials\2.0\Setup\Components" Value="SERVER-VERSION" Type="REG_SZ"
If the above conditions are not true, SP2 will be offered to any server running SP1 if the following conditions are true:
Value="Version" Comparison="EqualTo" Data="3"
Value="ServicePackLevel" Comparison="EqualTo" Data="1"
Value="VersionString" Comparison="EqualTo" Data="3.1.6001.65"
If SP2 is offered for the server running SP1 then we can approve the update for the installation. This update is not for the WSUS Clients. Following are some of the screenshots showing the SP2 installation through WSUS.
Note: SP2 upgrade is not a silent process, Admin intervention is required.
If WSUS SP2 is offered through WSUS, the installation process will first backup the SUSDB and we will see the following line in the WSUSSetup.log.
2009-09-06 02:40:39 Success MWUSSetup Creating database backup...
2. Manual Upgrade
As mentioned earlier, if SQL is on a remote machine we have to download the SP2 setup from the below link and run the upgrade manually on the server. Before running the setup you need to backup the SUSDB manually from the remote SQL box as the upgrade process will not take any backup of the database.
Once the setup is finished, the regular configuration wizard will start which can be ignored by clicking cancel.
How to check if Upgrade was Successful?
The installation of SP2 can be verified from Add/Remove Programs:
or from the Console:
or via the Registry:
Note: Administrative Tools will not show any Service Pack version at this time.
Hope this helps,
Mohammed Tajammul Hussain | Technical Support Lead
An interesting but ultimately not particularly helpful article.
It would be useful if the preconditions for installing WSUS SP2 were detailed more thoroughly, with a list of conditions known to cause failures - that is - a more detailed analysis of why the service pack will not install correctly, together with necessary corrective actions..
On SBS 2008 which was previously [and successfully] running WSUS SP1 this update was "offered" in the SBS console Update tab.
As advised, after first checking all the published preconditions, the administrator ran the update manually. The process proceeded more or less as described, first backing up the existing DB and then uninstalling SP1 and then installing itself until circa 90% completion; at which point the update failed with an "unknown error" and rolled itself back. After a restart WSUS was no longer installed. There was no useful information in either Event logs or in the setup logs to indicate why the update failed.
Manual reinstall of WSUS SP1 from original media, as described in various MS tech notes and KB articles succeeded, but all attempts to reintegrate the service into SBS 2008 console have thus far failed, and nowhere does the SBS Console actually log _why_ it is failing to integrate with WSUS and run its Update functions. SBS Best Practice Analyser gives no indications of any errors or other conditions which might block SBS Console integration.
All GPOs are correct, all WSUS and SQL configurations are correct. This leaves the system administrator unable to fix the issue or to manage client system updates in a sane and sensible fashion.
Microsoft's published advice appears to be that if a reintegration of WSUS into the SBS Console fails then the only remaining option is to reinstall SBS. This is unacceptable.
It is also not acceptable that an installer for a system service of such importance should not first check all conditions and pre-requisites to determine if it _can_ succeed. It is unacceptable that such an installation should fail in a fashion that it leaves the system in an unsupported and vulnerable condition. Given the number of online reports of WSUS upgrade failures in SBS 2008, and the lack of any apparent help from Microsoft, I'd say that this Service Pack isn't fit for purpose.
If you are running SBS 2008 then be warned.