Client Installation Planning Worksheet

Aplica-se a: 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

It is recommended that you familiarize yourself with the client installation methods and their related settings before completing this worksheet.

Use the following guidelines to assist in planning tasks.

 

Client installation methods Explanation Configuration parameters

Install Clients Using Software Update Point Based Installation

The Software update point (SUP) client installation method installs the Configuration Manager 2007 client software on any computer that can communicate with the site's software update point.

  • To specify the setup parameter information for the client installation you will need to create the SetupParameters registry string value in the following registry key: HKey_Local_Machine \Software \Policies \Microsoft \CCMSetup 

  • CCMSetup.exe will locate the setup parameters using this registry string value. For example: the registry string value information /mp:[ServerName] is read by CCMSetup.exe and the Configuration Manager client is directed to the server name specified. Specifying parameters through the registry key SetupParameters is the equivalent of specifying the installation parameters using the command line.

Client imaging

You can load client software components on the computer when it is originally prepared for service in your organization. Typically, computer preparation work is done by an IT team in a staging area. The client is installed on a computer master image by installing core client components without specifying a site code for assignment. The computer is ready to be assigned to a site when it arrives at the location where will be used in production.

  • Identify the CCMSetup.exe command line options you will use when installing the client on the master computer to be imaged.

  • Identify any registry modifications that need to be made for the preferred client type.

  • Identify the site code that the client should be assigned to.

Client Push installation

Client Push Installation is useful for installing the client software on computers that:

  • Have been discovered by Configuration Manager 2007 but do not have the client software installed.

  • Rarely log on to the network because the users lock their Windows sessions instead of logging out.

  • Log on with a user account that does not run a logon script or does not have administrative permissions on the computer.

  • Are servers that users might not log on to for a long period of time.

  • Enabled?

  • For computers running Windows Vista you must enable the remote registry service or the client push installation will fail on those clients.

  • Identify the client push installation account that will be used.

  • Identify whether you will push the client to servers, workstations, or domain controllers.

Manual installation

You can use CCMSetup.exe to manually install the Configuration Manager 2007 client software to a computer. CCMSetup.exe uses the Client.msi program to install the client software. CCMSetup.exe copies all the files necessary to complete the client installation, including the Client.msi and language-specific files and folders, to the computer.

  • Identify how and when CCMSetup.exe will be run on each client

  • Identify any specific command line options required.

Active Directory Group Policy

You can distribute the Configuration Manager 2007 client software using Active Directory Group Policy. Because of the limitations with customizing this installation method, Group Policy installations should be used for targeting small groups of computers. You can publish or assign the client installation program to computers based on their organizational unit location in Active Directory.

  • Identify the name(s) of any Group Policy objects.

  • Name(s) of OU, domain, or site the Group Policy object is linked to.

  • Identify any additional Group Policy object settings such as No Override or group filtering.

  • Identify Group Policy object security settings

Logon scripts installation

You can use the file CCMSetup.exe in a login script to trigger the client installation.

  • Logon script installations can be configured using the same method that you would configure a manual client installation. You can specify the /logon switch with CCMSetup.exe which will cause CCMSetup.exe to skip the installation if there is already a Configuration Manager Client installed.

  • If no installation source is specified using the /Source switch and no management point is specified using the /MP switch, CCMSetup.exe can locate the management point if there is a server locator point and Active Directory Services has been extended.

  • Identify any logon scripts being used and the commands being processed.

Software distribution

Software distribution can be used to upgrade existing SMS 2003 Advanced Clients.

Outline your plan to distribute CCMSetup.exe to run on each client.

  • Identify how and when CCMSetup.exe will be distributed on each client

  • Identify any specific command line options required.

Consulte Também

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.

Conteúdo da Comunidade

Mostrar: