ConfigMgr 2007, Client Push Installation – The server-side story

Sometimes its good to freshen-up some “hidden” knowledge. Its somewhere in your head, but it just needs to be freshened. One of these things is the Client Push Installation. In this post I will try to tell the story of the server side.

Prerequisites for Client Push Installation

To be able to do a successful Client Push Installation, the following prerequisites need to be met:

  • There must be a Client Push Installation –account defined in the Accounts tab of the Client Push Installation Properties.
  • The Client Push Installation –account must be a member of the local Administrators group on the targeted computer.
  • The targeted computer must have been discovered a ConfigMgr discovery method.
  • The targeted computer must have an ADMIN$ share.
  • The targeted computer must be able to contact a management point in order to download supporting files. See for more information my previous post about the ports used by a Client Push Installation.

Install the ConfigMgr Client using Client Push Installation

There a two methods of installing a ConfigMgr Client using Client Push Installation and I will described them both here, automatic and manual installation.

Method 1: Automatic Client Push InstallationClientPushInstallProp

  1. Open the Configuration Manager Console and browse to System Center Configuration Manager > Site Database > Site Management > <YourSiteName> > Site Settings > Client Installation Methods.
  2. Select Client Push Installation and click in the Actions pane Properties to open the Client Push Installation Properties.
  3. On the General tab select Enable Client Push Installation to Assigned Resources.
  4. (Prerequisite) On the Accounts tab specify an account to use when connecting to the targeted computer to install the client software.
  5. (Optional) On the Client tab specify any additional installation properties and click Ok.

Important (!): The specified installation properties, on the Client tab, must be for the client.msi. Also, the specified installation properties are published to the Active Directory if the schema is extended. These properties are used by client installations where the ccmsetup is run with no installation properties.

Method 2: Manual Client Push Installationimage

  1. (Prerequisite) On the Accounts tab (of the Client Push Installation Properties) specify an account to use when connecting to the targeted computer to install the client software.
  2. (Optional) On the Client tab (of the Client Push Installation Properties) specify any additional installation properties.
  3. Navigate to System Center Configuration Manager > Site Database > Computer Management > Collections.
  4. Select the collection or computer in a collection you want to push the client to. Right-click the computer or collection and then select Install Client to launch the Client Push Installation wizard and click Next.
  5. On the Installation options page, specify the client installation options that should be used and click Next.
  6. Review the installation settings, and click Finish to close the wizard

The Client Push Installation server-side –process

  • After a Client Push Installation is initiated a Client Configuration Request (CCR) –record gets created for each targeted computer. These records are created in <InstallationDirectory>\inboxes\ccr.box.
  • As soon as the CCR –record gets processed it will be moved to <InstallationDirectory>\inboxes\ccr.box\inproc. 
  • Based on the information of the CCR –record there will be a connection to the ADMIN$ share on the  targeted computer.
  • After the connection with the ADMIN$ was successful there will be a connection with the registry (IPC$), of the targeted computer, to gather information. 
  • Now the file copying will start. The MobileClient.tcf (from <InstallationDirectory>\bin\I386), the ccmsetup.exe and any needed updates (from <InstallationDirectory>\Client) are downloaded to ADMIN$\ccmsetup on the targeted computer.
  • After this the last thing that happens from the server-side is the verification whether the ccmsetup service is started successfully or not. When the ccmsetup –service is started successfully the CCR –record will be deleted and when the ccmsetup –service is not started (or created) successfully the CCR –record will be moved to <InstallationDirectory>\inboxes\ccrretry.box. Standard behavior is that those records get evaluated every hour.

Extra: If a installation fails and you want to prevent it from retrying every hour, just delete the corresponding CCR –record from the ccrretry.box.

Leave a Comment