The following blog runs through the procedure that is required to install a remote SUP in your environment. This could be to off-load site roles from the site server or to scale out.

Note that the installation has taken place on a Windows 2008 R2 server and that the site server is not going to be used as a SUP. For remote WSUS configuration on Server 2012 see here.

Install the WSUS Console on the site server

Download WSUS 3.0 SP2 from here.

Click Next in the WSUS install wizard.

When prompted choose to install the console only. Click Next.

Accept the licence agreement and click Next.

One the install is complete click Finish.

Install MS KB’s 2720211 and 2734608

Go to http://support.microsoft.com/kb/2720211/en-us & http://support.microsoft.com/kb/2734608/en-us respectively and install the WSUS 3.0 SP2 update patches, in no particular order.

Install IIS role on the remote SUP server

Connect to your remote server allocated for the WSUS role and load Server Manager. Choose Add Role. Select Web Server (IIS) and click Next.

Click Next.

Add the following IIS components

Common HTTP Features Static Content Default Document Directory Browsing HTTP Errors Application Development ASP.NET .NET Extensibility ISAPI Extensions ISAPI Filters Health and Diagnostics HTTP logging Request Monitor Security Windows Authentication Request Filtering Performance Static Content Compression Management Tools IIS Management Console IIS 6 Management Compatibility IIS 6 Metabase Compatibility

 Click Install.

Once installation of the IIS role is complete click Close.

Install Report Viewer 2008 on the remote SUP server

Download Report Viewer 2008 from http://www.microsoft.com/en-us/download/details.aspx?id=6576

Run the Reportviewer.exe file. Click Next.

Accept the licence terms and click Install.

Once complete click Finish.

Install WSUS on the remote SUP server

Follow the procedure to install WSUS on the remote SUP server as outlined earlier, however note the difference at the Database Options screen.

Choose ‘Use an existing database server on a remote computer’. Enter the hostname of the site server where the SUSDB was installed previously. Click Next.

Once a connection is made to the remote database choose to use the existing database on the SQL server. Click Next.

Continue the wizard through as per the previous WSUS install until complete. Then patch the SUP server with MS KB’s 2720211 and 2734608.

Add site server as local admin on the remote SUP server

Ensure that the site server has admin rights to the remote SUP server by adding it to the local administrators group.

Add the remote SUP server as a site system and install SUP role

Before the SUP role can be added in, the remote server must be added into SCCM as a site system. In the SCCM console go to the Administration workspace and choose Site Configuration>Servers and Site System Roles. Select ‘Create Site System Server’

Type in the FQDN of the remote SUP server and select the site code from the drop down list. Click Next.

Enter any proxy details if required. Click Next.

Choose to install a Software Update Point and click Next.

Select to use WSUS ports 8530 or 8531. If using 8531 (HTTPS) check the ‘Require SSL communications to the WSUS server’ checkbox. Click Next.

Click Next.

Select a synchronisation source, in this instance I am using the Microsoft Update site. Click Next.

Select a synchronisation schedule. I am using the default of every 7 days. Click Next.

Set the supersedence rules. Click Next.

Select the classification of updates you wish to install. Click Next.

Select the products that you wish to install updates for. Click Next.

Select language settings you want to synchronise. Click Next.

Click Next at the Summary screen.

Click Close once complete.

The SUP will being to install. Check the SMS\Logs folder on the remote server. In particular the SUPSetup.log which will report the success/failure of the SUP.

Also the WCM.log file on the site server will report connectivity to the new SUP.

..and the progress of the sync for product and classifications.

The sync can take a while. Once complete the following will be reported in the WCM.log.

Also take a look at the wsyncmgr.log file on the site server for information about the latest synchronisation that is taking place.

Finally, to check the status of the new SUP check the Site Status health in the Monitoring workspace.

and at the Component Status for the remote server.

The remote SUP is now successful installed.