Re-Install SCCM client using Active Directory Group Policy


Powershell SCCM client install toolkit. Download the script here.


  • Should be a computer policy.
  • Uninstall should happen before install.
  • Always use Deploy-Application.ps1 and not Deploy-Application.exe from the Powershell SCCM client install toolkit (The technet article uses Deploy-Application.exe as the lanuncher, which then summons Deploy-Application.ps1. But in this case, we have to use Deploy-Application.ps1 directly)


Create a Group Policy Object. e.g. SCCM Client Re-Install Policy.

Create a SCOPE for the Group Policy Object. Remove all other scopes. The scope will be limited to an AD security group e.g. ‘SCCM-Client-Re-Install-AD-Group’

Now the group policy will only run on computers who are members of the above AD security group. In this case, ‘SCCM-Client-Re-Install-AD-Group‘ security group.

Create a Computer Policy start-up script. Select the PowerShell tab.

Browse and select the file Deploy-Application.ps1. The parameters will be <Start> -DeploymentType UnInstall -DeployMode silent <finish> without the <Start> and <Finish>. Priority 1

Now again, browse and select the file Deploy-Application.ps1. The parameters will be <Start> -DeploymentType Install -DeployMode silent -SMSCACHESIZE 10260 -SMSMP “FQDN-of-Management-Point” -SMSSITECODE “Your-Site-Code” -FSP “FQDN-of-Fall-back-Status-Point” <finish> without the <Start> and <Finish>. Fill-in all the server names with FQDN’s of the servers. Priority 2

Furthermore one can add POSH scripts like this to remove the computer automatically from the AD group ‘Sccm-Client-Re-Install-AD-Group’. For doing so, give domain computers access to change membership of the AD group.


Related Articles

SCCM task sequence UI – Set computer name and more during an SCCM task sequence deployment

It is always a unique challenge of having to build an OSD experience that includes providing a great user experience during the deployment of a new operating system.

The attached application would allow you to present a front-end to an active end-user who is executing the SCCM task sequence……

Keywords: SCCM tasksequence UI, SCCM Task Sequence User interface, SCCM task sequence Set computer name.


Are you an SCCM administrator?

SCCM Task Sequence deployment orchestrator.

built on best practices, learnings & insights of industry experts.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.