The software update point in Microsoft System Center Configuration Manager 2007 is a required component of software updates and is installed as a site system role in the Configuration Manager console. The software update point site system role must be created on a site system server that has Microsoft Windows Server Update Services (WSUS) 3.0 installed. For more information about installing WSUS 3.0, see How to Install Windows Server Update Services 3.0.

Note
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.

There can be multiple site system servers with the software update point site system role, but only one site system server can be configured as the active software update point. When the site is in native mode, an additional active Internet-based software update point can be assigned to a remote site system server that allows communication from only Internet-based client computers. Additionally, if the active software update point is configured as a Network Load Balancing (NLB) cluster, a site system server with the software update point site role should be created for each server in the NLB. For information that will help you to determine the software update point configuration in your environment, see Determine the Software Update Point Infrastructure.

Use the following procedure to create an active software update point site role on a site system server and configure the software update point properties.

Note
For more information about creating and configuring an active Internet-based software update point, see How to Create and Configure an Active Internet-Based Software Update Point.

To configure a software update point

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

  2. 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.

  3. 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. When the computer account for the site server has access to the site system server and the site is in mixed mode, the settings on this page are optional. 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 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.

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

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

  6. Select Use this server as the active software update point, and then specify the port settings configured for the WSUS Web site on this site system.

    Important
    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.
  7. Specify the synchronization source for the active software update point using one of the following settings:

    • Synchronize from Microsoft Update: The software update point that is highest in the Configuration Manager 2007 hierarchy (most often the central site) must be configured to use this setting.

    • Synchronize from an upstream update server: The active software update points on all child sites and all Internet-based software update points should use this setting. The wizard selects this setting by default if this active software update point meets the criteria.

    • Do not synchronize from Microsoft Update or an upstream update server: Use this setting when this active software update point cannot connect to the upstream update server. Most often, this setting will be used by an active Internet-based software update point that has no access to the active software update point. For more information about synchronizing software updates when this setting is selected, see How to Synchronize Updates Using Export and Import.

  8. Keep the default setting Do not create WSUS reporting events, and then click Next.

  9. Specify whether to synchronize software updates on a schedule by selecting Enable synchronization on a schedule. When this setting is not selected, synchronization can be initiated manually by running the Run Synchronization action in the Configuration Manager. Click Next.

    Note
    Scheduled synchronizations perform full synchronization, but using the Run Synchronization action performs only delta synchronization.
  10. Specify the update classifications for which the software updates will be synchronized, and then click Next.

  11. Specify the products for which the software updates will be synchronized, and then click Next.

  12. Specify the languages for which the software updates will be synchronized, click Next, click Next, and then click Close.

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

  14. Open WCM.log in <InstallationPath>\Logs to verify that the connection to the WSUS server was successful. When the connection to the WSUS server has been established and the WSUS components have been verified, There are no unhealthy WSUS Server components on WSUS Server servername and Successfully checked database connection on WSUS server servername are written to the log file.

See Also