In this post we are going to discuss the different available options for installing the sccm 2012 client to our discovered machines see part 3 ,lets start…
In this method we will see how configure client push installation settings. Use this method only if you want the configuration manager clients to get automatically installed on the machine that is discovered.
Click on Administration, Expand Site Configuration, click on Sites, in the Sites list, and select the site for which you want to configure automatic site-wide client push installation. On the top ribbon
click on Client Installation Settings and click on Client Push Installation.
On the Client Push Installation Properties windows, click on General tab, check the box Enable automatic site-wide client push installation. Under System types, select Servers and Workstations.
Select the Accounts tab, the account that you will add here must have local administrator rights on every computer on which you want to install the client.
Click Apply and OK to close the properties page.
Installing configuration manager clients using client push installation wizard is very simple and you can use the wizard to install clients even if the site is not configured for client push. Ensure that the client installation settings are configured correctly, specially the accounts.
Click on Assets and Compliance, click on Devices, click on All Systems, right click on one of the computer and click on Install Client
On the Install Configuration Manager Client wizard click on Next.
Click on Install the client software from a specified site and click on Next.
Click on Close.
Take Care!! You might see this error while pushing the client
Error 0x800706ba (you may see this error in CCM log during the client push)
CWmi::Connect(): ConnectServer(Namespace) failed. – 0x800706ba
It is because the SCCM Client uses Dynamic RPC connections for WMI communications and can cause problems when a firewall is in place between the clients and the servers
ISSUE: Unable to deploy SCCM client to systems across firewall via client push
CAUSE: RPC Ports not open on firewalls
SOLUTION: You opened the port range above 1024 -5000 to allow for installation of the client.
You can manually install the System Center 2012 R2 Configuration Manager client software on computers in your enterprise by using the CCMSetup.exe program. This program and its supporting files can be found in the Client folder of the System Center 2012 Configuration Manager Installation folder on the site server and on management points in your site. This folder is shared to the network as <Site Server Name>\SMS_<Site Code>\Client.
CCMSetup.exe copies all necessary installation prerequisites to the client computer and calls the Windows Installer package (Client.msi) to perform the client installation.
You can specify command-line properties for both CCMSetup.exe and Client.msi to modify the behavior of the client installation. Make sure that you specify CCMSetup properties (the properties that begin with “/” before you specify Client.msi properties. The client installs by using the following properties:
|/mp:SMSMP01||This CCMSetup property specifies the management point SMSMP01 to download the required client installation files.|
|/logon||This CCMSetup property specifies that the installation should stop if an existing System Center 2012 Configuration Manager or Configuration Manager 2007 client is found on the computer.|
|SMSSITECODE=AUTO||This Client.msi property specifies that the client tries to locate the System Center 2012 Configuration Manager site code to use, for example, by using Active Directory Domain Services.|
|FSP=SMSFP01||This Client.msi property specifies that the fallback status point named SMSFP01 will be used to receive state messages sent from the client computer.|
Like this command for example
CCMSetup.exe /mp:2012sccm.test.local SMSSITECODE=ABC FSP=2012sccm.test.local