Release Notes for Microsoft Windows Server Update Services 0 sp1 5

Contents

Release Notes for Microsoft Windows Server Update Services 3.0 SP1

 System requirements for WSUS 3.0 SP1 server installation

 Configuration requirements for WSUS 3.0 SP1 server installation

 System requirements for WSUS 3.0 SP1 remote console installation

 System requirements for client installation

 Software requirements for WSUS SP1 server installation

 Minimum disk-space requirements for WSUS 3.0 SP1 server installation

 WSUS 3.0 SP1 upgrade requirements

 Setup command-line parameters

 Setup issues

 Upgrade issues

 Known issues

 WSUS 3.0 SP1 on Windows Server® 2008

 WSUS 3.0 SP1 on Windows Small Business Server 2003

System requirements for WSUS 3.0 SP1 server installation

Supported operating systems

 Windows Server 2003 Service Pack 1

WSUS 3.0 Server software prerequisites

 Windows Server 2003 SP1 or later

 IIS 6.0 or later

 Microsoft .NET Framework 2.0

 Microsoft Management Console 3.0

 Microsoft Report Viewer

 SQL Server 2005 SP1 is optional. If a compatible version of SQL Server is not installed already, WSUS 3.0 will install Windows Internal Database.

WSUS 3.0 Administration Console software prerequisites

 Microsoft .NET Framework 2.0

 Microsoft Management Console 3.0

 Microsoft Report Viewer

WSUS 3.0 SP1 server is supported on Windows Server 2008 and Windows Server 2003 Service Pack 1

Windows 2000 Server is not supported for WSUS 3.0 SP1 servers

WSUS 3.0 SP1 is not supported on servers running Terminal Services

Configuration requirements for WSUS 3.0 SP1 server installation

IIS must be installed

If IIS is running in IIS 5.0 isolation mode, installation will fail

If any IIS component is installed in 32-bit compatibility mode on a 64-bit platform, the WSUS 3.0 SP1 installation may fail

Proxy servers may support HTTP only, or HTTP and HTTPS

If two or more Web sites are already running on port 80, delete all but one of them before installing WSUS

When installing WSUS 3.0 SP1, you may need to disable antivirus programs

This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround, but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

An antivirus program is designed to help protect your computer from viruses. You must not download or open files from sources that you do not trust, visit Web sites that you do not trust, or open e-mail attachments when your antivirus program is disabled.

WSUS 3.0 SP1 requires the nested triggers option to be turned on in SQL Server

If you plan to use a SQL Server database as the Windows Server Update Services data store, the SQL Server administrator should verify that the nested triggers option on the server is turned on before the WSUS 3.0 SP1 administrator installs WSUS 3.0 SP1 and specifies the database during setup.

WSUS 3.0 SP1 Setup turns on the RECURSIVE_TRIGGERS option, which is a database-specific option; however, it does not turn on the nested triggers option, which is a server global option.

To see if the nested triggers option is on, use the following:

To turn on the nested triggers option in SQL Server, run the following from a batch file on the computer running SQL Server:

If you do not have SQL Server Management Studio on your server, you may want to run SQL scripts from the command line. You can obtain the Microsoft SQL Server 2005 Command Line Query Utility from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=70728). To get started, run sqlcmd.

If you wish to run SQL scripts against Windows Internal Database, you must also download the SQL Server Native Client from the same download page.

Remote SQL limitations and requirements

 You cannot use a server configured as a domain controller for the back end of the remote SQL pair.

 You must not be running Terminal Server on the computer that will be the front-end server of a remote SQL installation.

 You must use at least Microsoft SQL Server 2005 Service Pack 1 (available on the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=66143) for database software on the back-end computer if that computer is running Windows Server 2003, and SQL Server 2005 Service Pack 2 if the back-end computer is running Windows Server® 2008.

 Both the front-end computer and the back-end computer must be joined to an Active Directory domain; otherwise, if they are in different domains, you must establish cross-domain trust between the domains before running WSUS setup.

 If you already have WSUS 2.0 installed in a remote SQL configuration and wish to upgrade to WSUS 3.0 SP1, you should uninstall WSUS 2.0 (using Add or Remove Programs in Control Panel) on the back-end computer while ensuring that the existing database remains intact. Then you should install SQL Server 2005 SP1 or SP2 and upgrade the existing database. Finally, you should install WSUS 3.0 SP1 on the front-end computer.

System requirements for WSUS 3.0 SP1 remote console installation

 Windows Server 2008

 Windows Vista® or later

 Windows Server 2003 SP1 or later

 Windows XP SP2 or later

System requirements for client installation

 Windows Vista or later

 Windows Server 2008 or later

 Microsoft Windows Server 2003, any edition

 Microsoft Windows XP Professional SP2 or later

 Microsoft Windows 2000 Professional SP4, Windows 2000 Server SP4, or Windows 2000 Advanced Server with SP4

Software requirements for WSUS 3.0 SP1 server installation

Make sure the WSUS 3.0 SP1 server meets this list of requirements before you run WSUS 3.0 SP1 setup. If any of these updates require restarting the computer when installation is completed, you should perform the restart before installing WSUS 3.0 SP1.

If WSUS 2.0 has been installed previously and it is using SQL Server 2000, SQL Server Desktop Engine 2000, or any SQL Server database earlier than SQL Server 2005 SP1 (or SQL Server 2005 SP2 on Windows Server 2008), the WSUS 3.0 SP1 installation program will install Windows® Internal Database and migrate the database to it.

Minimum disk-space requirements for WSUS 3.0 SP1 server installation

 1 GB on the system partition

 2 GB for the volume on which database files will be stored

 20 GB for the volume on which content is stored

WSUS 3.0 SP1 cannot be installed on compressed drives. Please check that the drive you choose is not compressed.

WSUS 3.0 SP1 upgrade requirements

Ensure that your WSUS installation is running correctly, and back up the WSUS database before upgrading

1. Check for recent errors in the event logs, problems with synchronization between downstream servers and upstream servers, or problems with clients not reporting. Make sure that these issues have been resolved before continuing.

2. You may want to run DBCC CHECKDB to ensure that the WSUS database is correctly indexed. For more information about DBCC CHECKDB, see DBCC CHECKDB (http://go.microsoft.com/fwlink/?LinkId=86948).

3. Back up the WSUS database.

If you have manually modified the port used by WSUS, uninstall before upgrading

1. If you have not yet installed WSUS 3.0, uninstall WSUS 2.0, keeping the database and content. (If you have already installed WSUS 3.0, uninstall it, keeping the database and content.)

2. Start the Default Website, temporarily re-enabling SUS 1.0, but making it accessible to the uninstaller.

3. Uninstall SUS 1.0.

Software Update Services 1.0 should be uninstalled

It is not possible to upgrade from WSUS 2.0 to WSUS 3.0 SP1 on a 64-bit operating system

Setup command-line parameters

Sample Usage

WSUSSetup.exe /q /u (uninstall WSUS)

If you install WSUS 3.0 SP1 in quiet mode (/q), and the machine does not have all the prerequisites installed, the installation will generate a file named WSUSPreReqCheck.xml and save it in the %TEMP% directory.

Setup issues

IIS will be restarted during WSUS 3.0 SP1 Setup

If connections are open to an existing WSUS database, the installation may fail

WSUS setup shows the wrong directory for database files

If WSUS is installed on a machine that has Multilingual User Interface language packs with a default language other than English, Help will be displayed in the default language rather than in English

Upgrade issues

Recovering from a failed upgrade

1. Reinstall the previous version of WSUS.

2. Restore the database from the backup that you made before attempting the upgrade. (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 correct the problem.

4. Reattempt to upgrade WSUS.

It is not possible to upgrade from WSUS 2.0 to WSUS 3.0 SP1 if there is a WSUS 3.0 SP1 database from a previous installation

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

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

You will need to replace with the folder where the database is installed, and with the local storage folder.

sqlcmd.exe -S -E -Q "USE SUSDB DECLARE @asplogin varchar(200) SELECT @asplogin=name from sysusers WHERE name like '%ASPNET' EXEC sp_revokedbaccess @asplogin"

sqlcmd.exe -S -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 -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 -E -Q "backup database SUSDB to disk=N'\SUSDB.Dat' with init"

Setup will overwrite a previous database backup

If you have migrated from MSDE to SQL Server 2000 or SQL Server 2005 on WSUS 2.0, you will need to change a registry value

If WSUS 2.0 setup is started and canceled, it will delete the WSUS registry key

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

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 SP1

Known Issues

Troubleshooting multiple download errors or repeated client synchronization failures

To delete the client download cache:

1. Delete all files and subdirectories in this location on the client computer: %windir%\SoftwareDistribution\Download

2. Attempt to install the update by synchronizing the client computer with WSUS 3.0 SP1 again. This installation attempt should fail with the following error: WU_E_DM_NOTDOWNLOADED, "The update has not been downloaded."

If synchronization fails, retry synchronization

Changing the WSUS 3.0 SP1 configuration directly in the database is not supported

Download failures are not reported quickly if disk quotas are turned on

If WSUS 3.0 SP1 is deployed using SSL, client computers may fail with a 0x8024400a error code

The WSUS Administrators domain account will not be deleted when WSUS is uninstalled

If a downstream server is converted to an upstream server, catalog site updates must be re-imported

If you are using IIS with SSL, unencrypted access is still possible unless "Require Secure Channel" is checked

Catalog site import may fail without read/write permissions to the %windir%\TEMP folder

Performance may be slow when synchronizing between WSUS 3.0 SP1 and a downstream replica server running WSUS 2.0

If the e-mail server is down or unreachable, e-mail notification fails without notice

Changed settings on an upstream server are not pushed immediately to the downstream server

Uninstalling WSUS 3.0 SP1 does not uninstall the database instance

If it is necessary to uninstall Windows Internal Database, the following commands will uninstall the application:

(on 32-bit platforms)

msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe

(on 64-bit platforms)

msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe

If you wish to uninstall Windows Internal Database Service Pack 2 from Windows Server 2008, you may do so by using Server Manager.

However, the removal of the application may not remove the default .mdf and .ldf files, which will cause a subsequent WSUS 3.0 SP1 installation to fail. These files can be deleted from the %windir%\SYSMSI\SSEE directory.

If a downstream server changes its upstream server, "Unknown" status updates are reported as "Not Applicable"

If the Server Cleanup Wizard times out on one server when run on multiple servers from a remote console, the connection to all servers will be lost

Starting and stopping the connection in quick succession causes "There was no synchronization failure" error message in the Configuration Wizard

WSUS 3.0 SP1 on Windows Server 2008

Supported Versions

Prerequisites

Using the Security Configuration Wizard

The following known issues exist with using the SCW together with the WSUS role:

 The Windows Internal Database service is enabled even though it may not be used by WSUS. You configure WSUS to use a database—either Windows Internal Database or SQL Server database. If WSUS is installed with SQL Server and you select the WSUS role in the SCW, the Windows Internal Database service is enabled if it is installed on the computer, but it is not used by WSUS. You should disable the Windows Internal Database service if you are using SQL Server database instead of Windows Internal Database.

 Firewall rules for WSUS on a custom Web site are not selected by default. If you install WSUS on a custom Web site (port 8530 or 8531), the required firewall rules are not automatically selected even if you select the WSUS role in the SCW. You should enable the appropriate firewall rules for WSUS based on whether Secure Sockets Layer (SSL) is configured for the WSUS server.

WSUS 3.0 SP1 on Windows Small Business Server 2003

If the IIS virtual root is restricted to certain IP addresses or domain names, the WSUS 3.0 SP1 server will not be able to update itself

Installing WSUS 3.0 SP1 on Small Business Server—Integration Issues

 If ISA is using Windows Authentication, proxy server credentials should be typed in the form DOMAIN\user and the user should be a member of the Internet Users group.

If you have added a subnet to your network without using the Windows SBS wizards, you must perform this procedure

1. In Server Management, expand Advanced Management, expand Internet Information Services, expand Web Sites, expand Default Web Site, right-click the Selfupdate virtual directory, and then click Properties.

2. Click Directory Security.

3. Under IP address and domain name restrictions, click Edit, and then click Granted Access.

4. Click OK, right-click the ClientWebService virtual directory, and then click Properties.

5. Click Directory Security.

6. Under IP address and domain name restrictions, click Edit, and then click Granted Access.

Copyright

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.