Prerequisites for Client Deployment in Configuration Manager 2012

Updated: March 15, 2011

Applies To: System Center Configuration Manager 2012

Deploying Configuration Manager 2012 clients in your environment has the following external dependencies and dependencies within the product. Additionally, each client deployment method has its own dependencies that must be met for client installations to be successful.

Also review Configuration Manager Supported Configurations to ensure that computers in your site meet the minimum hardware and operating system requirements for the Configuration Manager 2012 client.

Dependencies External to Configuration Manager 2012

Microsoft Background Intelligent Transfer Service (BITS) version 2.5 is required to allow throttled data transfers between the client computer and Configuration Manager 2012 site systems. BITS is not automatically downloaded during client installation and must be present before the Configuration Manager 2012 client can be installed.

Dependencies External to Configuration Manager 2012 and Automatically Downloaded During Installation

The Configuration Manager 2012 client has a number of potential external dependencies listed below. The exact dependencies depend on the client's operating system and the installed software.

If these dependencies are required to complete the installation of the client, they are automatically installed with the client software.

 

Dependencies Automatically Supplied During Installation More Information

Windows Installer version 3.1.4000.2435

Required to support the use of Windows Installer update (.msp) files for packages and software updates.

Windows Update Agent version 7.0.6000.363

Required by Windows to support update detection and deployment.

Microsoft Core XML Services (MSXML) version 6.20.5002 or later

Required to support the processing of XML documents in Windows.

Microsoft Remote Differential Compression (RDC)

Optimizes data transmission over the network.
noteNote
The software version numbers listed are minimum version numbers only.
ImportantImportant
When BITS is installed on client computers, a restart is generally required. If BITS is being installed during client installation (by CCMSetup.exe), then the client installation is not completed until the computer is restarted. For this reason, it is recommended that you pre-deploy the minimum required version of BITS or a later version on client computers before you install the Configuration Manager 2012 client.

Configuration Manager 2012 Dependencies

For more information about the following site system roles, see Determine the Site System Roles You Need for Clients in Configuration Manager 2012.

 

Configuration Manager Site System More Information

Management Point

Although a management point is not required to deploy the Configuration Manager 2012 client, you must have a management point to transfer information between client computers and Configuration Manager 2012 servers. Without a management point, you cannot manage client computers.

Fallback Status Point

The fallback status point is an optional, but recommended site system role. The fallback status point allows computers in the Configuration Manager 2012 site to send state messages when they are unable to communicate with a management point. Client installation status is also sent to the fallback status point.

Server Locator Point

Client computers require a server locator point to assign to Configuration Manager 2012 site and to locate management points when the Active Directory schema has not been extended for Configuration Manager 2012 or when client computers are not joined to an Active Directory domain.

Installation Method Dependencies

The following prerequisites are specific to the various methods of client installation:

 

Client Installation Method More Information

Client push installation
  • Client Push Installation accounts are used to connect to computers to install the client and are specified in the Accounts tab of the Client Push Installation Properties dialog box. The account must be a member of the local administrators group on the destination computer.

    If you do not specify a Client Push Installation account, then the site server computer account will be used.

  • The computer on which you are installing the client must have been discovered by at least one Configuration Manager 2012 discovery method.

  • The computer has an ADMIN$ share.

  • Enable client push installation to assigned resources must be selected in the Client Push Installation Properties dialog box if you want to automatically push the Configuration Manager 2012 client to discovered resources.

  • The client computer must be able to contact a management point in order to download supporting files.

Software update point-based installation
  • If the Active Directory schema has not been extended, or you are installing clients from another forest, installation properties for CCMSetup.exe must be provisioned in the registry of the computer by using Group Policy. For more information, see How to Provision Client Installation Properties by using Group Policy in Configuration Manager 2012.

  • The Configuration Manager 2012 client must be published to the software update point.

  • The client computer must be able to contact a management point in order to download supporting files.

Group Policy-based installation

Logon script-based installation
  • The client computer must be able to contact a management point in order to download supporting files unless the CCMSetup /source property has been specified with the CCMSetup.exe command line.

Manual installation
  • The client computer must be able to contact a management point in order to download supporting files unless the CCMSetup /source property has been specified in the CCMSetup.exe command line.

Workgroup computer installation
  • In order to access resources in the Configuration Manager 2012 site server domain, the Network Access account must be configured for the site.

Software distribution-based installation (for upgrades only)

Firewall Requirements

If there is a firewall between the site system servers and the computers onto which you want to install the Configuration Manager client, see Windows Firewall and Port Settings for Clients in Configuration Manager 2012.

See Also