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 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.
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.
In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems.
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:
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:
Click Next.
Select Software update point, and then click Next.
Specify whether the site server will use a proxy server when connecting to the software update point, and then click Next.
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.
Specify the synchronization source for the active software update point using one of the following settings:
Keep the default setting Do not create WSUS reporting events, and then click Next.
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.
Specify the update classifications for which the software updates will be synchronized, and then click Next.
Specify the products for which the software updates will be synchronized, and then click Next.
Specify the languages for which the software updates will be synchronized, click Next, click Next, and then click Close.
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.
Installation was successful
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.
There are no unhealthy WSUS Server components on WSUS Server
Successfully checked database connection on WSUS server