Deploying Configuration Manager 2007 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 2007 client.
Dependencies External to Configuration Manager 2007 and Automatically Downloaded During Installation
The Configuration Manager 2007 client has a number of potential external dependencies listed below. The exact dependencies depend on the client's operating system, the installed software and the processor type of the client computer.
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
|
| Microsoft Background Intelligent Transfer Service (BITS) version 2.5 | Required to allow throttled data transfers between the client computer and Configuration Manager 2007 site systems. .gif) Note |
|---|
|
On computers running Windows 2000, BITS version 2.0 will be installed. |
|
| Microsoft Windows Installer version 3.1.4000.2435 | Required to support the use of Microsoft Windows Installer update (.msp) files for packages and software updates. |
| Microsoft Windows Update Agent version 7.0.6000.363 | Required by Windows to support update detection and deployment. |
| Microsoft Core XML Services (MSXML) version 6.0.3883.0 | Required to support the processing of XML documents in Windows. |
| Microsoft WMI Redistributable Components version 5.2.3790.1830 | WMI components required by Windows 2000 Service Pack 4 computers. |
| Microsoft Remote Differential Compression (RDC) | Optimizes data transmission over the network. |
| Note |
|---|
|
The software version numbers listed are minimum version numbers only. |
.gif) Important |
|---|
|
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 will not complete until the computer is restarted. For this reason, it is recommended that you pre-deploy BITS on client computers before you install the Configuration Manager 2007 client. |
Configuration Manager 2007 Dependencies
For more information about the following site system roles, see Configuration Manager Site System Planning.
|
Configuration Manager Site System
|
More Information
|
| Management Point | Although a management point is not required to deploy the Configuration Manager 2007 client, you must have a management point to transfer information between client computers and Configuration Manager 2007 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 2007 site to send state messages when they are unable to communicate with a management point. |
| Server Locator Point | Client computers require a server locator point to assign to Configuration Manager 2007 site and to locate management points when the Active Directory schema has not been extended for Configuration Manager 2007. |
Installation Method Dependencies
The following prerequisites are specific to the various methods of client installation:
|
Client Installation Method
|
More Information
|
| Client Push installation | -
At least one Client push installation account must have been defined in the Accounts tab of the Client Push Installation Properties dialog box.
-
The computer to which you are targeting the client installation must have been discovered by at least one Configuration Manager 2007 discovery method.
- 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 2007 client to discovered resources.
-
The client computer must be able to contact a management point in order to download supporting files.
-
The Windows firewall must be configured on client computers with exceptions to allow client push installation to complete. For information, see Firewall Settings for Configuration Manager Clients.
|
| Software Update Point based installation | -
If the Active Directory schema has not been extended, installation properties for CCMSetup.exe must be provisioned in the registry of the computer using the procedure in How to Provision Configuration Manager Client Installation Properties using Group Policy.
-
The required version of the Configuration Manager 2007 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 /source switch has been specified in 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 /source switch has been specified in the CCMSetup.exe command line.
|
| Software Distribution based installation (for upgrades only) | -
If the Active Directory schema has not been extended, installation properties for CCMSetup.exe must be provisioned in the registry of the computer using the procedure in How to Provision Configuration Manager Client Installation Properties using Group Policy.or in the setup command line in the Configuration Manager 2007 package containing the client.
-
The client computer must be able to contact a management point in order to download supporting files unless the /source switch has been specified in the CCMSetup.exe command line.
|
See Also