There are a number of different methods that you can use to install the Configuration Manager 2007 client software on computers in your enterprise. You can use one, or any combination of these methods which are suitable for your needs.

The following table outlines the advantages and disadvantages of each client installation method to help you determine which will work best in your organization. Reference Tasks for Installing Configuration Manager Clients for procedural information about using these methods.

Client Installation Method Advantage Disadvantage

Client push installation
  • Can be used to push to a single computer, a collection or the results from a query.

  • Can be used to automatically install the client on discovered computers.

  • Automatically uses client installation properties defined on the Client tab of the Client Push Installation Properties dialog box.
  • Can cause high network traffic when pushing to large collections.

  • Can only be used on computers that have been discovered by Configuration Manager 2007.

  • Cannot be used to install clients in a workgroup.

  • A client push installation account must be specified which has administrative rights to the intended client computer.

  • The Windows firewall must be configured on client computers with exceptions to allow client push installation to complete.

Software update point based installation
  • Can use your existing software updates infrastructure to manage the client software.

  • Can automatically install the client software on new computers if WSUS and Active Directory Group Policy is configured correctly.

  • Does not require computers to be discovered before the client can be installed.

  • If the Active Directory schema has been extended for Configuration Manager 2007, computers can read installation properties published to Active Directory Domain Services.

  • Will reinstall the client software if it is removed.
  • Requires a functioning software updates infrastructure as a prerequisite.

  • Must use the same server for client installation and software updates, and this server must reside in a primary site.

  • To install new clients, you must configure an Active Directory Group Policy object with the client's active software update point and port.

  • If the Active Directory schema is not extended for Configuration Manager 2007, you must use Group Policy to provision computers with client installation properties.

Group Policy installation
  • Does not require computers to be discovered before the client can be installed.

  • Can be used for new client installations or for upgrades.

  • If the Active Directory schema has been extended, computers can read installation properties published to Active Directory.
  • Can cause high network traffic if a large number of clients are being installed.

  • If the Active Directory schema is not extended for Configuration Manager 2007, you must use Group Policy to add client installation properties to computers in your site.

Logon script installation
  • Does not require computers to be discovered before the client can be installed.

  • Supports using command line properties for CCMSetup.
  • Can cause high network traffic if a large number of clients are being installed.

Manual installation
  • Does not require computers to be discovered before the client can be installed.

  • Can be useful for testing purposes.

  • Supports using command line properties for CCMSetup.
  • No automation, therefore time consuming.

Upgrade installation (software distribution)
  • Can leverage the features of Configuration Manager 2007 to upgrade the client by collection, or to a defined timescale.

  • Supports using command line properties for CCMSetup.
  • Can cause high network traffic when distributing the client to large collections.

  • Can only be used to upgrade the client software on computers that have been discovered and assigned to the site.

See Also