In this post I will illustrate how to install SCCM Client by using Client Push, while you can deploy the SCCM Client via a variety of methods among which manual installation and GPO can be found.
Once you have installed ConfigMgr and configured discovery methods the next logical step is to configure SCCM Client Push so that the ConfigMgr client will be automatically installed on any machine discovered in infrastructure as per Microsoft recommendations.
SCCM Client Push Requisites
SCCM Client Push function are already part of a default ConfigMgr installation so the only requirement that needs to be satisfied is the creation of a the client push installation account.
The SCCM Client Push installation account can be any domain account with administrative rights on client computers where the SCCM client will be installed for the purpose of this lab I will use the mcsecmpa account to which I have delegated administrative rights on all client computers via Group Policies.
Configure SCCM Client Push
Once the client push account has been created and proper permissions have been delegate to enable automatic client push installation open the ConfigMgr console and navigate to [Administration] –> [Site Configuration] –> [Sites] either right-click on the site for which you want the client push installation to be enabled or click Client Installation Settings on the Ribbon interface
Tick the Enable automatic site-wide client push installation and select for which type of systems you want the client to be automatically installed, in my lab I have set automatic installation only for clients
Under the Accounts tab click the sunburst icon and specify the account, with administrative privileges on the client, that will be used to carry on the actual installation
Finally under the Installation Properties you can specify parameters that will affect both SCCM client installation and behavior for this article I have just specified the ConfigMgr site code
After a couple of minutes the SCCM Client will be deployed on the client you can actually monitor this checking processes on the client where you should see the ccmsetup.exe process
Wait till the installation is complete and check in the admin console for the client to appear as installed
There are two main and important log files for SCCM Client Push installation the first one is named ccmsetup.log and is located under C:WindowsccmsetupLogs the second one is on the SCCM Server and will allow you to see when installation is triggered and is named ccm.log
SCCM Client Push Installation Troubleshooting
The process of having ConfigMgr push the SCCM client to computers in your infrastructure is easy to implement and usually without any issues anyhow if you cannot deploy the client here’s some points that will help you troubleshoot the process
- Make sure the Windows Firewall on the client machine is either disabled or allowing inbound/outbound ports used by SCCM
- Make sure the BITS Service is running on the Client machine
- Make sure the client is correctly assigned to a site
- Make sure the account used for Client Push process has admin rights on the client machine
- Make sure the WMI database is not corrupted on the client machine
There are of course many other possible issues causing the push installation process to fail but I am pretty confident the list above can help you isolate the problem