Group Policy Deployment SCCM Client

SCCM has a variety of client deployment methods, such as configuring automatic discovery deployment through the console, Group Policy deployment, manual deployment, scripting deployment, and so on, which today describes how to deploy clients through Group Policy

First we open the Group Policy console to create a new Group Policy named Kslx_sccmagentforks, which will be applied to the KS site, deploy clients for computers affiliated to the KS site, edit our new Group Policy, navigate to Computer Configuration-Administrative Templates, Right-Select the Administrative template and click Add/Remove Templates

Next we will see a popup window where we click Add on the window, where we need to add the two Group Policy template files in the SCCM installation package, which is stored in the smssetup-"tools-" Configmgradmtemplates of the SCCM installation file, Locate the two template files and add them to the template for the current Group Policy

After the template has been successfully added, we expand the administrative template, we can see a new option "Classic Administrative Template", we expand his subkey, we can see that there are two configuration options for SCCM client installation in the right panel

Next we need to configure these 2 options, first configure site assignment, enable this configuration, and then fill in the client is assigned to the site, because I have to install the secondary site, so here to fill the site code of the secondary site KS1, other values remain the default

After configuring deployment Setting, when this configuration is enabled, we need to fill in some specific parameters, specify some configuration information for the client, Smssitecode=auto smsmp=ks5p-sccm-s01
Smssitecode is to assign the client to the site, we can specify the site code, can also be directly set to auto, let the client to choose the nearest site, but it is important to note that if we have an SCCM site set up on the Internet, it is not possible to use auto , you need to specify the site code manually. SMSMP is the initialization management point that assigns the client, and the client obtains the SCCM policies and applications from that management point

After configuring the two options above, we need to add the client's deployment installation file to the Group Policy, first we need to copy the Ccmsetup.msi file from the SCCM installation file to a shared directory (the path to the Ccmsetup.msi file is smssetup\bin\ I386), the shared directory must open the Read permission for everyone, but if you are deploying a client that is a domain-based computer, there is no need to create a shared directory to hold the file, and I copy the file directly to the script file in the Sysvol folder of the ad. The directory default open domain account Read permissions, next we configure the deployment of the installation package in Group Policy, expand the computer configuration of the "policy"-"Software Settings"-"Software Installation", right-click Select New Packet, Then find the Ccmsetup.msi file that we put in the script, choose the deployment method assigned, click OK

After all the configuration is complete, we attach the Group Policy to the corresponding site, and we can configure the WMI filter to select the installation according to the requirement, for example, I restrict the policy to be executed on the WIN7,WIN8,WIN10 client by the WMI filter condition. Therefore, this policy does not execute on any server version of the operating system

Well, the deployment of the client to this Group Policy is complete.

Group Policy Deployment SCCM Client