When you deploy Configuration Manager Clients using Automatic Site Wide Client Push Installation method (we did this is a few labs back), during the discovery process, configuration manager clients are installed automatically. To demonstrate this lab, i.e., using Group Policy to deploy Configuration Manager Clients, we need to first disable the Automcatic Site Wide Push Installation.
Under sites, highlight the YTO- Toronto Site and then click Client Installation Settings. Choose Client Push Installation.
Ensure that the “Enable Automatic site Wide Client Push Installation” option is unchecked. Click Apply then click OK.
From this point on in this lab, we will be working on the Domain Controller. So, go to the Domain Controller, launch gpmc.msc.
Right-click the domain level and click Create a GPO in this domain, and Link it here.
Enter a policy name (My SCCM Deployment Using GPO) and click OK.
Right-click the newly created policy and choose Edit.
Under Computer Configurations, choose Policies, click Administrative Templates, and click Add/Remove Templates.
To add templates click Add.
Add two templates found in the Configuration Manager DVD Drive\SMSSETUP\TOOLS\ConfigMgrADMTemplates. (For example if you DVD drive is D:\ then the files can be found at D:\ SMSSETUP\TOOLS\ConfigMgrADMTemplates\)
Drill down to Administrative Templates -> Classic Administrative Templates -> Configuration Manager 2012 -> Configuration Manager 2012 Client. You will see the two templates on the right side but unconfigured.
Let’s enable the first one: Configure Configuration Manager 2012 Site Assignment. Right-click on the template and click Edit.
Click Enable, then enter the Site Code, Site Assignment Retry Interval, and Site Assignment Retry Duration.
Click Next Setting.
Click Enable to enable the policy. Enter the CCMSetup command as:
CCMSetup.exe SMSSITECODE=YTO FSP=SCCM.DALARIS.LOCAL MP=SCCM.DALARIS.LOCAL.
For more information about the CCMSetup command, click here: https://technet.microsoft.com/en-us/library/048dbf2d-5132-4fc0-ad8a-d90322b6db96#BKMK_CCMSetupCommandLine
Now click Apply and then click OK.
Now under Software Settings, click Software Installation, click New, and choose Package.
Pause this step for a moment. Now copy the file ccmsetup.msi from the DVD Drive\ SCCM\SMSSETUP\BIN\I386 to a shared location where Read-Only access for everyone is given. This file will be assigned via a network path (UNC Path). In my case, the DVD drive is D:\ so I took the file ccmsetup.msi from D:\ SCCM\SMSSETUP\BIN\I386\ and then paste it in my local hard drive at C:\Share. After that I share out the folder C:\Share to everyone with Readonly permission.
Place that MSI file in C:\Shared on the Domain Controller.
Remember to share the folder C:\Shared.
Now choose the MSI file to assign.
Choose Assigned and click OK.
As you can see, the ConfigMgr Client Setup package is now displayed under Software Installation. Verify that is the case and then close the Group Policy Management Editor.
In Group Policy Management, create a new OU for the computers in which you want Configuration Manager Client software to be deployed. Should you leave the Policy linked to the domain level, all computers on your domain will get this software installed.
Right-click the domain DALARIS.LOCAL and click New Organizational Unit.
Provide a name for the OU and then click OK.
After having the new OU created, right-click on it and choose Link an existing GPO.
Choose the new GPO we created earlier and then click OK.
As we can see that the new GPO is linked to the correct OU.
Now we need to move a few client computers to the OU we created so that Configuration Manager Client software can be installed by the GPO.
Launch dsa.msc. Select the Computers OU, right-click on two client computers and choose Move.
Choose Windows Computers For SCCM Install and click OK. This means that we want to move the two selected computers to the target OU.
Verify that the client computers are available in the Windows Computers For SCCM Install OU.
On the Domain Controller, perform GPUPDATE. Type gpupdate /force.
Now do the same thing (GPUPDATE) on the client computers and restart both of them. Verify that Configuration Manager is installed automatically.
In this lab we have successfully deployed Configuration Manager Client Software to two sample client computers using Group Policy Objects.