Deploy the SCCM Client via GPO: Configuration Manager Client Installation Step by Step

With Group Policy (GPO) you can make the SCCM client installation central and automatic. In this guide I go through the whole process: preparing the GPO, adding the ADM templates, site assignment, deploying the MSI package and verifying the result.

Why deploy the SCCM client with GPO?

• Central and automatic installation in Active Directory environments
• A standard, repeatable process
• Precise control of the client scope per OU
• Lower operational effort than push or manual installation

SCCM client deployment methods

• Deployment with GPO (the topic of this article)
• Installation with a logon script
• Manual installation (not recommended in large environments)
• Client Push Installation (from the SCCM console)
• Deployment with Microsoft Intune (MDM)

Prerequisites

1) Preparation: disable automatic client push

1. SCCM console → Administration > Site Configuration > Sites
2. Right-click the site → Properties
3. Under Client Installation Settings > Client Push Installation, clear Enable Automatic site-wide client push installation.
4. Save with OK.

Note: this step hands control of the client installation over to the GPO.

2) Create a new GPO

1. Open the Group Policy Management Console (GPMC) on a DC.
2. Group Policy Objects → right-click → New → give it a name (for example GPO-SCCM-Client-Install).
3. Right-click the GPO → Edit.

3) Add the SCCM ADM templates

Under Computer Configuration > Policies > Administrative Templates, choose Add/Remove Templates and browse to this folder:

<Drive>:\Program Files\Microsoft Configuration Manager\Tools\ConfigMgrADMTemplates

• ConfigMgrAssignment.adm
• ConfigMgrInstallation.adm

4) Site assignment and installation settings

Go to Administrative Templates > Classic Administrative Templates > Configuration Manager > Configuration Manager Client.

Site Assignment

• Configuration Manager Site Assignment → Enabled
• Assigned Site Code: TCC (example)
• Retry Interval: 5 minutes
• Retry Duration: 1 hour

Client Deployment Settings

Configure Configuration Manager Client Deployment Settings → Enabled. Example command line:

CCMSetup.exe SMSSITECODE=TCC FSP=SRV-01.contoso.com MP=SRV-01.contoso.com

The site code and server names are examples; use your own.

5) Create the software installation package (MSI)

1. Computer Configuration > Policies > Software Settings > Software Installation → right-click → New > Package.
2. Point to ccmsetup.msi on the network share (a UNC path is recommended).
3. Deployment type: Assigned.

MSI location (example):

<ConfigMgr_Media>\SMSSETUP\BIN\I386\ccmsetup.msi

Make sure the share grants Read permission (Domain Computers).

6) Link and apply the GPO

1. Right-click the target OU → Link an Existing GPO → GPO-SCCM-Client-Install.
2. Refresh policies on the clients:

   gpupdate /force

3. Restart the client if needed; ccmsetup.exe runs in the background.

7) Verification and troubleshooting

• Logs on the client:

  C:\Windows\ccmsetup\Logs\ccmsetup.log
  C:\Windows\ccmsetup\Logs\client.msi.log

• Event Viewer → the Application and System logs around the time of the installation
• SCCM console → Assets and Compliance > Devices: check that the device shows “Client = Yes”.

Best practices

• Use a UNC path for the MSI share (for example \\filesrv\dist\ccmsetup).
• Roll out in stages through your OU design: pilot → production.
• Monitor GPO replication (SYSVOL / DFS Replication).
• Review firewall and antivirus exclusions on the clients.

If the client installation fails

If the GPO is applied but the Configuration Manager client installation does not complete, do not just apply the GPO again. My guide SCCM Client Not Installing? Troubleshooting with ccmsetup.log and Client Health checks the installation, registration, Boundary and Management Point layers separately.

Sources

• Microsoft Learn – Deploy clients to Windows computers
• Microsoft Learn – Client installation properties (CCMSetup)