Deploy Configuration Manager 2012 Client Using a Startup Script

17 Dec

This post is about deploying the Configuration Manager 2012 client using a startup script. This is a heavily modified script of the original made by Jason Sandy which can be found here.


  • The script and xml readme can be found here.

New Features

  • For Windows XP and 2003 machines, the certificate auto-enrollment legacy hotfix (KB968730) can now be installed by the script. New options are defined in the xml file for the legacy hotfix.
  • Input arguments are more flexible.
  • Logs can be copied to a central share.
  • Additional SCCM client arguments can now be specified in the XML.
  • CU’s now scan and install properly according to architecture.

What does it do?

  • The script will:
    • Install the SCCM 2012 client.
    • Maintain the health of the SCCM client.
    • Install Client hotfixes.
    • Install certificate enrollment hotfixes.
  • This script does not fix WMI problems at this time. That’s a feature we’re still working on.

How do I use it?

  • Make a Group Policy Object in the OU of your choice, name it “Deploy SCCM Client”. In the GPO under “Startup” scripts assign:
  • For name: Enter the path of where your script is stored plus the script name.
  • For parameters: Enter “/config:” and the path to the xml file.
    GPO settings

XML Options

See the github readme for additional options available in this version of the script.


Leave a comment

Posted by on December 17, 2012 in Uncategorized


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: