Deploying Configuration Manager console using SCCM 2012 R2 In this short post we will see the steps for Deploying Configuration Manager console using SCCM 2012 R2. I have been asked several times by many people on how to do that. Here is short post that explains on how to deploy SCCM console using configuration manager 2012 R2. SCCM admins use the Configuration Manager console to manage the Configuration Manager environment. Each Configuration Manager console connects to either a central administration site or a primary site. After the initial connection is made, the Configuration Manager console can connect to other sites. However, you cannot connect a Configuration Manager console to a secondary site. You can install the Configuration Manager console during the site server installation in the Setup Wizard, or run the stand-alone application. That would be the easiest way to do it but it suits better when you want to install it for a single user or less number of users. However if you want to deploy the console to multiple users then you could use SCCM to do it.
Deploying Configuration Manager Console
Before you start to deploy the CM console, you need to make sure that .NET Framework 4.0 or higher version is installed on the system where you want to deploy the console. Download the .NET Framework 4.0 standalone installer by clicking on this link.
If you need help on deploying Microsoft .NET Framework 4.0 Using SCCM then click on this link.
To install the console you need to get the installation files copied to a folder. On the site server, browse to <ConfigMgrSiteServerInstallationPath>ToolsConsoleSetup. Copy the ConsoleSetup folder to a location on your site server. Launch the CM console, under Application Management right click Packages and click on Create Package. Provide the details for the package and click on Next.
Choose the Program Type as Standard Program. Click Next.
Specify information about the console program, provide the install command as
consolesetup.exe /q TargetDir=”D:/Program Files/ConfigMgr” EnableSQM=0 DefaultSiteServerName=MyServer.Contoso.com
/q – Installs the Configuration Manager console unattended. The EnableSQM, TargetDir, and DefaultSiteServerName options are required when you use this option.
TargetDir – Specifies the installation folder to install the Configuration Manager console.
EnableSQM – Specifies whether to join the Customer Experience Improvement Program (CEIP). Use a value of 1 to join the Customer Experience Improvement Program, and a value of 0 to not join the program.
DefaultSiteServerName – Specifies the FQDN of the site server to which the console connects when it opens.
Complete the remaining steps and at last click on Close.
Once your package is ready, distribute the content to DP and deploy it to desired collection. On the client machine you can open the execmgr.log file and monitor the installation. I have tested the installation of console on Windows 7 twice and it works well. If you face any issues with deployment then do write in comments.