Upgrade to WSUS 3.0 SP2

  • Article

 

Applies To: Windows Server Update Services, Windows Small Business Server 2011 Standard, Windows Server 2008 R2, Windows Server 2003 with SP2, Windows Server 2008 R2 with SP1

You can upgrade from the following Windows Server Update Services (WSUS) versions to WSUS 3.0 SP2:

  • WSUS 2.0

  • WSUS 3.0

  • WSUS 3.0 SP1

In this topic:

Before you upgrade from WSUS 2.0 to WSUS 3.0 SP2

Before you upgrade the WSUS system, you should perform the following actions:

  1. Check the event logs for recent synchronization problems or problems with client computers not reporting. Resolve these issues before you upgrade WSUS.

  2. Run DBCC CHECKDB to verify that the WSUS database is correctly indexed and uncorrupted. For more information, see DBCC CHECKDB (Transact-SQL).

  3. Back up the WSUS database.

Upgrade to WSUS 3.0 SP2

When you install WSUS 3.0 SP2, the WSUS Setup program automatically upgrades all WSUS settings to WSUS 3.0 SP2. If the WSUS Setup program finds that WSUS is using a version of SQL Server earlier than SQL Server 2005 with Service Pack 2, it will perform the following additional actions:

  • Back up the existing database

  • Install Windows Internal Database

  • Migrate the database to Windows Internal Database

Upgrade a Remote SQL Server installation from WSUS 2.0 to WSUS 3.0 SP2

If the WSUS 2.0 installation uses a remote database server, you must uninstall WSUS 2.0 from the database server before you can upgrade to WSUS 3.0 SP2.

To upgrade a Remote SQL Server installation from WSUS 2.0 to WSUS 3.0 SP2

  1. Uninstall WSUS 2.0 by using Add or Remove Programs in Control Panel on the back-end computer. Do not remove the existing database.

  2. If necessary, install SQL Server 2008 Standard or Enterprise Edition or SQL Server 2005 with SP3, and then upgrade the existing database.

  3. Install WSUS 3.0 SP2 on the front-end server.

  4. Reindex the database. For more information, see Reindex the WSUS Database.

Troubleshoot WSUS upgrade issues

If you upgrade from WSUS 2.0 to WSUS 3.0 SP2, you might encounter the following issues:

Issue Resolution
The WSUS 2.0 configuration uses the IIS website on port 8530. This setting causes a mismatch in the WSUS environment. Change the default WSUS website port to 80 by using the following command:

 WSUSUtil.exe useCustomWebsite false
The SSL certificate is not configured for the WSUS port. If WSUS 2.0 was configured to use SSL, you must reinstall the SSL certificate after the upgrade is complete. Reinstall the SSL certificate by using the following command:

 wsusutil configuressl ServerCertificateName

where ServerCertificateName is the name of the SSL certificate.

For more information about SSL certificates, see Configuring Server Certificates in IIS 7.

Note

The wsusutil.exe command is located in the <installdrive>:\Program Files\Update Services\Tools folder. For more information about wsusutil, see Manage WSUS 3.0 SP2 from the Command Line.

Recovering from a failed upgrade

If you are upgrading from an earlier version of WSUS to WSUS 3.0 SP2 and the upgrade fails (for any reason other than trying an unsupported upgrade from SUS 1.0), perform the following tasks:

  1. Reinstall the earlier version of WSUS.

  2. Restore the database from the backup that you made before you try to upgrade. You cannot successfully complete an upgrade if there is an existing WSUS 3.0 SP2 database from a previous installation. In most cases, WSUS also automatically creates a backup. See the WSUSSetup.log file for the location.

  3. Review the logs to determine the cause of the failure, and resolve the problem.

  4. Install WSUS 3.0 SP2.

Changing the computer name prior to upgrading to WSUS 3.0 SP2 can cause the upgrade to fail

If you change the computer name after you install WSUS 2.0 and before you upgrade to WSUS 3.0 SP2, the upgrade can fail.

Use the following script to remove and re-add the ASPNET and WSUS Administrators groups. Then run the upgrade again.

You have to replace <DBLocation> with the folder where the database is installed, and <ContentDirectory> with the local storage folder.

sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE @asplogin varchar(200) SELECT @asplogin=name from sysusers WHERE name like '%ASPNET' EXEC sp_revokedbaccess @asplogin"  
sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE @wsusadminslogin varchar(200) SELECT @wsusadminslogin=name from sysusers WHERE name like '%WSUS Administrators' EXEC sp_revokedbaccess @wsusadminslogin"  
  
sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE @asplogin varchar(200) SELECT @asplogin=HOST_NAME()+'\ASPNET' EXEC sp_grantlogin @asplogin EXEC sp_grantdbaccess @asplogin EXEC sp_addrolemember webService,@asplogin"  
sqlcmd.exe -S <DBLocation> -E -Q "USE SUSDB DECLARE @wsusadminslogin varchar(200) SELECT @wsusadminslogin=HOST_NAME()+'\WSUS Administrators' EXEC sp_grantlogin @wsusadminslogin EXEC sp_grantdbaccess @wsusadminslogin EXEC sp_addrolemember webService,@wsusadminslogin"  
  
sqlcmd.exe -S <DBLocation> -E -Q "backup database SUSDB to disk=N'<ContentDirectory>\SUSDB.Dat' with init"

If you have migrated from Microsoft SQL Server Desktop Engine (MSDE) to SQL Server 2008 or SQL Server 2005 on WSUS 2.0, you have to change a registry value

If you have an installation of WSUS 2.0, and have migrated to SQL Server 2008 or SQL Server 2005, you have to change the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\WmsdeInstalled value from 1 to 0. If you do not do so before upgrading to WSUS 3.0 SP2, the upgrade will fail.

If you uninstall WSUS 3.0 SP2 and leave the log files behind, they may not have the appropriate permissions after reinstallation

If you uninstall WSUS 3.0 SP2, you have the option to keep the installation log files. When you reinstall WSUS 3.0 SP2, the old log files may lose their permissions (usually for WSUS Administrators only). As a best practice, confirm the permissions on these log files after installation.

If WSUS 2.0 clients have updates with "Not Applicable" status, the updates will appear as "Unknown" for a short time after upgrading to WSUS 3.0 SP2

If an existing WSUS 2.0 server has clients that have Not Applicable updates, these updates may be listed with an Unknown status for a short time after you upgrade to WSUS 3.0 SP2. The update status will return to Not Applicable after the next time that the client does a scan.

See Also

Install the WSUS Server
Windows Server Update Services 3.0 SP2 Migration Guide