Export (0) Print
Expand All
Expand Minimize
1 out of 1 rated this helpful - Rate this topic

How to Create and Configure an Active Software Update Point on a Secondary Site

Updated: October 1, 2009

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

The software update point in Microsoft System Center Configuration Manager 2007 is a required component of software updates on primary sites, an optional component for software updates on secondary sites, and is installed as a site system role in the Configuration Manager console. When the secondary site is not configured with a software update point site system, any clients residing in the boundaries of the secondary site will automatically be configured to use the software update point at the parent site. When there is limited network bandwidth to the software update point at the parent site or when Windows Server Update Services (WSUS) is approaching the maximum number of client computers, it is recommended that a software update point be installed at the secondary site. For information that will help you to determine the software update point configuration in your environment, see Determine the Software Update Point Infrastructure.

The site system server must have WSUS 3.0 installed prior to adding the software update point site system role. For more information about installing WSUS 3.0, see How to Install Windows Server Update Services 3.0. WSUS running on the software update point for the secondary site is configured to be a replica of the active software update point for the parent site.

noteNote
Configuration Manager 2007 Service Pack 1 (SP1) requires WSUS 3.0 SP1 or WSUS 3.0 Service Pack 2 (SP2). WSUS 3.0 SP2 is required to support Configuration Manager 2007 SP2 software update management for the Windows 7 and Windows Server 2008 R2 operating systems.

Use the following procedures to create a software update point site role on the secondary site and then to configure the active software update point.

To create the software update point on a secondary site

  1. If not already installed, install WSUS 3.0 on the site system server selected for the software update point site role at the secondary site. For more information, see How to Install Windows Server Update Services 3.0.

  2. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / <secondary site code> - <secondary site name> / Site Settings / Site Systems.

  3. Determine whether to create a new site system server or add the software update point site system role to an existing site system server, and then follow the associated step:

    • To create a new site system server and add the software update point site role: Right-click Site Systems, click New, and then click Server.

    • To add the software update point site role to an existing site system server: Right-click the site system server name, and then click New Roles.

  4. Configure the general site system settings for the site system server. By default, the computer account for the site server will connect to the site system computer to install the software update point components. For more information, see New Site System Server Wizard: General Page. When the computer account does not have access to the site system server or when the site is in native mode, the following settings should be configured:

    • Specify a fully qualified domain name (FQDN) for this site system on the intranet: This setting must be configured for the active software update point site system when the site server is in native mode or when it is in mixed mode and uses Secure Sockets Layer (SSL). By default, this setting is enabled and must be configured.

    • Specify an Internet-based fully qualified domain name for this site system: This setting must be configured for the active software update point if it accepts Internet-based client connectivity or for the active Internet-based software update point site system.

    • Use another account for installing this site system: This setting must be configured when the computer account for the site server does not have access to the remote site system.

    • Allow only site server initiated data transfers from this site system: This setting must be specified when the remote site system does not have access to the inboxes on the site server. This allows a site system from a different domain or forest to store the files that need to be transferred to the site server. The site server will periodically connect to the remote site system and retrieve the files. The Internet-based software update point might require this setting to be enabled.

    Click Next.

  5. Select Software update point, and then click Next.

  6. Specify whether the site server will use a proxy server when connecting to the software update point, and then click Next.

  7. Click Next, and then click Close.

To configure the active software update point for the secondary site

  1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / <secondary site code> - <secondary site name> / Site Settings / Component Configuration.

  2. Right-click Software Update Point Component, and then click Properties.

  3. Click the General tab, and then specify the port settings configured for the WSUS Web site on this site system.

    ImportantImportant
    The site server will fail to communicate with the WSUS server if the port settings are not correct. For information about how to find this information, see How to Determine the Port Settings Used by WSUS.

  4. Click the Sync Settings tab to specify whether to create event messages for WSUS reporting. These reporting events are not used by Configuration Manager and can be disabled if WSUS reporting is not used.

  5. Click OK to exit the dialog box.

  6. Open SUPSetup.log in <ConfigMgrInstallationPath>\Logs to monitor the installation progress for the software update point. When the installation completes, Installation was successful is written to the log file.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.