How to Deploy Configuration Manager Client Using GPO – Trinn-for-trinn guide.
If you are planning to deploy Configuration Manager clients using GPO then you must make sure that in the client push installation properties, Enable Automatic site-wide client push installation is not checked. If this is checked then the client would get installed on all the systems after its discovery. So first uncheck the option Enable Automatic site-wide client push installation and proceed.
1. Åpen de Group Policy Management console. Choose OU, for which a new GPO will be created (or you may link it later);
2. Høyre museknapp click and click Create GPO in this domain, and link it here;
3. Tast inn your Name og klikk OK;
4. Click on the newly created policy, in the pop-up window click OK;
5. Høyre museknapp click on the policy and click Redigere;
MERK: GPO templates files are only required if the schema has not been extended
6. Navigere til Computer Configuration\Policies\Administrative Templates. Høyre museknapp click and click Add/Remove Templates;
7. Klikk Legg til;
MERK: The Configuration Manager templates can be found inSourceDVD\SMSSETUP\TOOLS\ConfigMgrADMTemplatesor you can also add it from <Drive>:\Program Files\Microsoft Configuration Manager\tools\ConfigMgrADMTemplates.
8. Select templates and click Åpen;
9. Klikk Lukk;
10. Navigere til Computer Configuration\Policies\Administrative Templates\Classic Administrative Templates\Configuration Manager\Configuration Manager Client;
11. Høyre museknapp click atConfigure Configuration Manager Site Assignment template and click Redigere;
12. Plukke ut Aktivert to enable the policy, under Options specifyAssigned Site code, Site Assignment Retry Interval til 5 minutter, and Site Assignment Retry Duration til1 hour (You can also choose to leave the options to default except site code). KlikkOK;
13. Høyre museknapp click atConfigure Configuration Manager Client Deployment Settings og klikk Redigere;
14. Plukke ut Aktivert. Under options specify the installation properties for the CCMSetup file. I have used the following installation command SMSSITECODE=L01 FSP=SCCM.enterinit.com MP=SCCM.enterinit.com. Klikk OK;
15. Navigere til Computer Configuration\Policies\Software Settings\Software installation. Høyre museknapp click and click New\Package;
MERK: De ccmsetup.msi can be found inSOURCEDVD\SMSSETUP\BIN\I386 or <Drive>:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\I386. Copy the ccmsetup.msi in a folder (Create a new folder on SCCM Server) and share it with permissions Read-only for Everyone OR copy it to your SYSVOL folder. I create a new folder in Scripts – SCCM Client and copy *.msi to it.
16. Browse the file ccmsetup.msi and click Åpen;
17. Velg Deployment method asAssigned. KlikkOK;
18. When you click on Software installation you should see the Navn of thePackage, itsVersion, Deployment Status ogSource. You can now close the console;
19. Reboot the Client machine and then SCCM client installation begins. You can see the cmmsetup.exe(32 bit) i Task Manager konsoll;
22. When the process disappears, you can go to SCCM Console\Assets and Compliance\Devices and check the newly installed client;
Do you have to reboot the machine to have the .msi kick off? Can you log off and back on instead to have the GPO refresh? I am wanting to install the client on many different servers and really don’t want to put in a change request for all the different machines if I don’t have to.
Hello. Reboot is required because the software installation by group policy applies at startup. If you don’t want to reboot your machines, then use manual client installation. Not fast and simple like GPO but perfectly work without reboot (in mostly cases).