· At first ensure that the “nested triggers” option is enabled on the new SQL Server:
o Go to “Enterprise Manager”, right click on the new SQL Server and choose “Properties”.
o In the “Server settings” tab, the option: “Allow triggers to be fired which fire other triggers (nested triggers)” should be checked.
· The “Background Intelligent Transfer Service (BITS) 2.0” must be running on the new SQL Server.
· “Microsoft .NET Framework 1.1 Service Pack 1” must be installed on the new SQL server.
· Install WSUS on the new SQL Server
o Log on to the new SQL Server with a local administrator account
o Open up a command prompt and navigate to the folder that contains the WSUS setup files.
o Run this command: WSUSSetup.exe /b
o On the Welcome page of the wizard, click Next. Click “I accept the terms of the License Agreement”, and then click Next.
o On the Database Options page, you select the software used to manage the WSUS database. You must provide the new SQL Server instance for WSUS to use, by clicking Use an existing database server on this computer and typing the instance name in the SQL instance name box. You must click Use an existing database server on this computer. Select the instance name from SQL instance name box, and then click Next.
o On the Connecting to SQL Server Instance page, wait to be prompted with for a successful connection to the SQL server, and then click Next.
o On the Mirror Update Settings page, you specify the management role for this WSUS server. Enter the name of the upstream WSUS server here.
o On the Ready to Install Windows Server Update Services page, click Next.
o If the final screen confirms that WSUS installation was successfully completed, click Finish.
· After you install WSUS on the new SQL server, you must run a SQL script to identify how update storage is being managed on the front-end computer. The syntax of the SQL script you run depends on whether client computers are getting updates locally from the front-end computer or are downloading updates directly from Microsoft. You established where clients obtain updates when you installed WSUS on the front-end computer.
· If you cannot remember how you configured the front-end computer, you can find out by reading the log file located on the front-end computer here:
%programfiles%\Update Services\Logfiles\WSUSSetup_InstallDate.log,
where InstallDate is the date you installed WSUS.
· From this file you need the value for two keys:
o HostOnMu
o LocalContentCacheLocation
· At the command prompt of the SQL Server, type one of the following commands, depending on how you set up the front-end computer:
o If you chose local storage on the front-end computer, type:
"%programfiles%\update services\tools\osql\osql.exe" -S SQLServerName -E -b -n -Q"
USE SUSDB UPDATE dbo.tbConfigurationA SET HostOnMu = '0'UPDATE dbo.tbConfigurationB SET LocalContentCacheLocation = N'LocalContentCacheLocation Value'"whereSQLServerName is the name of the SQL Server instance that holds the SUSDB database; where %programfiles% is the location of the Program Files folder on the front-end computer and where LocalContentCacheLocation Value is the actual string used to identify where in the file system of the front-end computer to store content, with \WSUSContent appended to the end. For example, if you used C:\WSUS on the front-end computer, you would type C:\WSUS\WSUSContent. Do not use a network location or a UNC path. Do not add a trailing backslash (\).
· If you chose remote storage on Microsoft Update, type the following:"%programfiles%\update services\tools\osql\osql.exe" -S SQLServerName -E -b -n -Q"
USE SUSDB UPDATE dbo.tbConfigurationA SET HostOnMu = '1' UPDATE dbo.tbConfigurationB SET LocalContentCacheLocation = N'%programfiles%\Update Services\WsusContent'"where SQLServerName is the name of the SQL Server instance on the back-end computer; and where %programfiles% is the location of the Program Files folder on the front-end computer.
· Set Permissions on Windows Server 2003
o On the SQL Server, click Start, point to Administrative Tools, and then click Computer Management.
o In the tree, expand Local Users and Groups, and then click Groups.
o In the details pane, double-click WSUS Administrators.
o In the WSUS Administrators Properties dialog box, click Add.
o In Select Users, Computers or Groups, click Object Types.
o In Object Types, click Computers, and then click OK.
o In Select Users, Computers, or Groups, enter the name of the front-end computer, and then click OK.
o In the WSUS Administrators Properties dialog box, click OK.
· Configure the WSUS Server to use the database of the new SQL Server by editing the registry
o On the WSUS Server (front-end computer), click Start, and then click Run.
o In the Open box, type regedit, and then click OK.
o In Registry Editor, navigate to the following registry key:HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup§ In the details pane, double-click the SQLServerName key. In Value data, type the name of the new SQL Server (back-end computer), and then click OK. When entering data, use the syntax servername\instance. If your server uses the default instance, you can omit the instance name-for example, servername.
o Move the SUSDB database from the old SQL Server to the new SQL Server o Log on to the old SQL Server and detach the SUSDB database.
o Copy (don’t move) the corresponding MDF and LDF files of the SUSDB database to the new location on the new server.
o Attach the copied database on the new SQL Server.Manually start the Update Service
§ Click Start, and then click Run.
§ In the Open box, type services.msc, and then click OK.
§ In the details pane, double-click the Update Services service, and then click Start.
§ Check that the WSUS installation works correctly. In that case you can delete the files of the SUSDB database from the old SQL Server.
For Reference purposes:Step-by-Step Guide to Getting Started with Microsoft Windows Server Update Serviceshttp://www.microsoft.com/downloads/details.aspx?FamilyID=3ba03939-a5a9-407b-a4b0-1290ba5182f8&DisplayLang=en Microsoft Windows Server Update Services Operations Guidehttp://www.microsoft.com/downloads/details.aspx?familyid=E26BCDB4-EF0B-4399-8A71-9B3B00C4F4CD&displaylang=en Deploying Microsoft Windows Server Update Serviceshttp://www.microsoft.com/downloads/details.aspx?familyid=E99C9D13-63E0-41CE-A646-EB36F1D3E987&displaylang=en WSUS: Install Required Softwarehttp://technet2.microsoft.com/WindowsServer/en/library/ace052df-74e7-4d6a-b5d4-f7911bb06b401033.mspx?mfr=true WSUS: Remote SQLhttp://technet2.microsoft.com/WindowsServer/en/library/ace052df-74e7-4d6a-b5d4-f7911bb06b401033.mspx?mfr=true