You must carefully plan how you will deploy the Configuration Manager 2007 client software to computers. You can use any of the following client deployment methods:
- Software-update-point-based installation
- Client push installation
- Manual installation
- Group Policy installation
- Logon script installation
If you are upgrading from Systems Management Server 2003, you can also deploy the new Configuration Manager Client to the SMS 2003 clients using software distribution.
All of the client methods have different dependencies, requirements, and security concerns. Choose the client installation method that best fits your environment and business requirements.
For more information, see the following:
- Determine the
Configuration Manager Client Installation Method to Use
- Tasks for Installing
Configuration Manager Clients
Installing a Test Client
There is no single recommended way to deploy clients, but the following method is suitable for testing basic client functions.
On the test client, run the following command from a command prompt:
\\<site server>\SMS_<site code>\client\ccmsetup.exe /mp=<management point> SMSSITECODE=<site code> FSP = <fallback status point>
If you need a server locator point, include the following properties: /NATIVE: crlandfallback and SMSSLP = <server locator point>.
Use the following table if you need more information about replacing the placeholder values.
When specifying a server, you can use a fully qualified domain name (FQDN), a short name (host name or NetBIOS name), or an IP address.
The computer from where you ran Configuration Manager 2007 Setup.
The three-character site code.
The computer you configured with the management point role.
<fallback status point>
The computer you configured with the fallback status point role.
<server locator point>
The computer you configured with the server locator point role.
If your client cannot locate site information from Active Directory Domain Services, consider including the installation property SMSSIGNCERT= <Full path and filename>. For more information, see Decide How to Deploy the Site Server Signing Certificate to Clients (Native Mode).
To install a client by running CCMSetup with the following values:
- A site server named SJC003
- A site code of SJC
- A management point named SJC020
- A fallback status point named SJC021
Type: \\SJC003\SMS_SJC\Client\CCMSetup.exe /mp:SJC020 smssitecode=SJC FSP=SJC021
To install the same client if it must use a server locator point that is named SJC025:
Type: \\SJC003\SMS_SJC\Client\CCMSetup.exe /NATIVE: crlandfallback /mp:SJC020 smssitecode=SJC FSP=SJC021 SMSSLP = SJC025
Additional Information for Client Deployment
Client deployment documentation: Planning and Deploying Clients for Configuration Manager 2007.
Administrator checklist for client deployment: Administrator Checklist: Deploying Configuration Manager Clients.
Troubleshooting: Troubleshooting Configuration Manager Client Deployment.
TasksHow to Install Configuration Manager Clients Using Client Push
How to Install Configuration Manager Clients Using Software Update Point Based Installation
How to Upgrade Clients Using Software Distribution in Configuration Manager
How to Install Configuration Manager Clients Using Computer Imaging
How to Configure Request Ports for the Configuration Manager Client
ConceptsHow to Install Configuration Manager Clients Manually
How to Install Configuration Manager Clients Using Group Policy
How to Install Configuration Manager Clients Using Logon Scripts
About Configuration Manager Client Installation Properties
Determine the Configuration Manager Client Installation Method to Use