Trevor Sullivan's Tech Room

Minding the gap between administration and development

ConfigMgr 2012: Installing the Software Update Point Role

Posted by Trevor Sullivan on 2011/05/05


Introduction

In a new ConfigMgr 2012 site, you probably won’t initially have a Software Update Point (SUP), which allows you to deploy Microsoft software updates. This process actually uses Windows Server Update Services (WSUS) 3.0 under the covers, just like ConfigMgr 2007 did.

Add the Software Update Point (SUP) Role

In the ConfigMgr 2012 console, under Administration –> Overview –> Site Operations –> Servers and Site System Roles, you can select the server you’d like to add the role to, and the click Add Site System Role on the Microsoft Office-style ribbon bar.

image

You’ll be prompted with a wizard to install site system roles.

image

If you hit the Next button, you’ll see the screen that allows you to select the roles to add to the site system

image

Select the “Software update point” role and hit the Next button

The software update point is described as follows: “A software update point integrates with Windows Server Update Services (WSUS) to provide software updates to Configuration Manager clients.

On the next screen, we’re allowed to configure some basic settings for the new role we’re adding. If your network configuration doesn’t require a proxy server, simply hit the Next button.

If you do require a proxy server, check the “Use a proxy server when synchronizing software update” checkbox, type your proxy server FQDN & port, and then provide credentials if required.

image

In order to use this new SUP, we must denote that it is active and usable by ConfigMgr clients. On the “Specify active software update point settings” screen, check the box for “Use this server as the active software update point.

When you installed WSUS on the server, you should have had the option to use port 80, or a “custom website” which means that WSUS will listen on port 8530. Select the appropriate option and click Next.

image

On the “Specify synchronization source” screen, choose the option to “Synchronize from Microsoft Update.” This will configure WSUS to pull update metadata directly from Microsoft, as opposed to an “upstream” software update point. If you have installed a stand-alone primary site, or a central site, the option to synchronize from an upstream server will be greyed out.

You can safely ignore the option for “WSUS reporting events.

image

On the “Specify synchronization behavior” screen, enable a recurring synchronization, and select the "Generate an alert when synchronization fails in any site in the hierarchy" option. Change the “Simple Schedule” to every 3 days, for a lab environment – that ought to be sufficient, since updates are released relatively infrequently. Keep in mind that the initial catalog sync will take quite a while, and subsequent syncs will take much less time.

When you’re finished, click Next.

image

On the “Select behavior for software updates that are superceded” screen, leave the option set to “Immediately expire a superceded software update.

When completed, hit the Next button.

image

On the Classifications screen, select the software update classifications you’d like to deploy. I generally recommend adding the “Critical Updates” category, which isn’t selected by default, because there are often critical, non-security updates that will increase the overall reliability of your servers and desktops.

When you’re finished on this screen, click the Next button.

image

 

image

On the “Languages” screen, select any update languages that you require. In this case, I’ll just choose English.

When you’re finished, click Next.

image

The next screen simply summarizes all of the settings you’ve entered so far, so go ahead and click Next.

image

SUP Installation Log

When you install a Software Update Point, a log file will be created called SUPSetup.log. Here are the contents of mine after a successful installation:

<05-10-2011 09:43:29> ====================================================================
<05-10-2011 09:43:29> SMSWSUS Setup Started….
<05-10-2011 09:43:29> Parameters: E:\PROGRA~1\MICROS~2\bin\x64\ROLESE~1.EXE /install /siteserver:SCCM01 SMSWSUS
<05-10-2011 09:43:29> Installing Pre Reqs for SMSWSUS
<05-10-2011 09:43:29>         ======== Installing Pre Reqs for Role SMSWSUS ========
<05-10-2011 09:43:29> Found 1 Pre Reqs for Role SMSWSUS
<05-10-2011 09:43:29> Pre Req SqlNativeClient found.
<05-10-2011 09:43:29> SqlNativeClient already installed (Product Code: {025B5B19-DB4D-4B44-BAEE-428D1F5DB0BD}). Would not install again.
<05-10-2011 09:43:29> Pre Req SqlNativeClient is already installed. Skipping it.
<05-10-2011 09:43:29>         ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
<05-10-2011 09:43:29> Installing the SMSWSUS
<05-10-2011 09:43:29> Correct and supported WSUS Server version (3.1.7600.226) is installed.
<05-10-2011 09:43:29> Invoking process c:\Windows\Microsoft.NET\Framework64\v4.0.30319\\RegAsm.exe "e:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
<05-10-2011 09:43:30> Registered DLL e:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
<05-10-2011 09:43:30> Installation was successful.

From the above log, we can see the following steps happening:

  • Check for SQL Server Native Client to be installed
    • If the SQL Server Native Client is not installed, go ahead and install it
  • Check for correct version of WSUS Server to be installed
  • Registers wsusmsp.dll using RegAsm.exe

Conclusion

At this point, you’ve successfully installed the software update point in ConfigMgr 2012 Beta 2! There really isn’t much different here from SCCM 2007, but hopefully I’ll get a chance to investigate and write about some of the changes to how updates are deployed in SCCM 2012.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: