ConfigMgr 2012 Console Automated Deployment Walkthrough


Console installation for remote management

By default ConfigMgr only installs the administration console on the primary site server.  There is a redistributable console package conveniently provided with ConfigMg 2012 that makes deploying the admin console to other servers and desktops significantly easier than in 2007.

There are a couple ways to deploy the console, the first being to connect to the installation media and from the splash.hta page, run the installation and only select the console install.  This may be awkward for all users to take advantage of and it does require additional manual configuration such as the site server name.  In addition to this the ConfigMgr 2012 console requires .NET 4.0 Extended (or Full as it’s sometimes called) which many servers and most client desktops do not install by default.  To make this a more seamless process the best solution is to take advantage of the new application model in ConfigMgr 2012 to deploy all the require resources in one click.

Before starting the following steps, ensure that .Net 4 Full has been downloaded and placed in its own folder and is accessible to the site server.  The version of .Net required for this process is the same as the one used for the site server prerequisites.  At the time of writing this is dotNetFx40_Full_x86_x64.exe, dated 2/21/2011. Available for download here.

  • In the ConfigMgr console click on Software Library in the Wunderbar.
  • Click to expand Application Management and then on the ribbon, click the Create button and from the dropdown list click Create Application to open the Create Application Wizard.
  • On the General page, click the radio button next to Manually specify the application information
  • Next, enter in the name for the .Net application entering in name, manufacturer as per below.
    • Name:  .Net Full
    • Manufacturer: Microsoft
    • Software version: 4
    • Once set, click Next.
  • On the Application Catalog page, in the Keywords section, type in .Net, Utility and then click Next
  • On the Deployment Types page, click the Add button to launch the Create Deployment Type Wizard.
  • On the General page of the Create Deployment Type Wizard click the radio button next to Manually specify the deployment type information and then click Next.
  • On the General Information page, type in the Name of the deployment type.  In this case .Net 4 Full Installation and then click Next.

 

  • On the Content page, next to Content location click the Browse button and navigate to where you placed the .net 4 executable file prior to starting this process.  IE:  \\sccm\SourceMedia\Tools\DotNet4_Full_x86_x64\
  • In the Installation program text box, enter in the following command line that will perform a silent installation of .Net 4: dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
  • (Optional) In the Uninstall program text box, enter in the following command line that will perform a silent uninstallation  %windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /q /norestart
  • Once set, click Next

 

  • On the Detection Method page, click the Add Clause… button to open the Detection Rule dialog box
  • Click the drop down next to Setting Type and select Registry
  • Click the drop down next to Hive and select HKEY_LOCAL_MACHINE
  • In the Key text field enter in: Software\Microsoft\NET Framework Setup\NDP\v4\Full
  • In the Value text field enter in: Install
  • Click the drop down next to Data Type and select Integer
  • Once set, click OK and then Next

  • On the User Experience page, click the drop down next to installation behavior and select Install for System

 

  • Click the drop down next to Installation program visibility and select Normal
  • Click the drop down next to Logon requirement and select Whether or not a user is logged on
  • Set the value for Maximum allowed run time (minutes) to 20 and then click Next
  • On the Requirements page, click Next
  • On the Dependencies page, click Next
  • On the Summary page, review the information and then click Next
  • On the Completion page, click Close
  • Back at the Create Application Wizard / Deployment Types page, click the Next button
  • On the Summary page, click Next
  • On the Completion page, click Close

With the .Net 4 package ready, the next step is to perform the same steps for the ConfigMgr console itself.  The ConfigMgr console installer will reference the .Net 4 package as a prerequisite in order to allow for a fully automated end to end installation of the console.

  • In the ConfigMgr console click on Software Library in the Wunderbar.
  • Click to expand Application Management and then on the ribbon, click the Create button and from the dropdown list click Create Application to open the Create Application Wizard.
  • On the General page, click the radio button next to Manually specify the application information
  • Next, enter in the name for the .Net application entering in name, manufacturer as per below.
    • Name:  ConfigMgr Console
    • Manufacturer: Microsoft
    • Software version: 2012
    • Once set, click Next.
  •  On the Application Catalog page, in the Keywords section, type in ConfigMgr, Console, Utility and then click Next
  • On the Deployment Types page, click the Add button to launch the Create Deployment Type Wizard.
  • On the General page click the radio button next to Manually specify the deployment type information and then click Next.
  • On the General Information page, type in the Name of the deployment type.  In this case ConfigMgr Console Installation and then click Next.
  • On the Content page, next to Content location click the Browse button and navigate to the console folder which is located under the ConfigMgr installation folder.  IE:  \\sccm.network.int\ConfigMgr\tools\ConsoleSetup\
  • In the Installation program text box, enter in the following command line that will perform a silent installation of the console: consolesetup.exe /q TargetDir=C:\ConfigMgrConsole EnableSQM=0 DefaultSiteServerName=sccm.network.int
    • The Enable SQL option is for the Microsoft Experience Feedback option.  0 is disabled, 1 is enabled.
    • The DefaultSiteServerName option is the FQDN of the primary site server that you want to connect to when the console opens.  This can be changed when the console is open if you need to connect to a different site.
    • In the Uninstall program text box, enter in the following command line that will perform a silent uninstallation: consolesetup.exe /uninstall /q
    • Once set, click Next
 
  • On the Detection Method page, click the Add Clause… button to open the Detection Rule dialog box
  • In the Path text field enter in: C:\ConfigMgrConsole\Bin
  • In the File or folder name text field enter in: Microsoft.ConfigurationManagement.exe
  • Click the box to deselect (uncheck) the box next to This file or folder is associated with a 32-bit application on 64-bit systems.  Once set, click OK and then Next
  • On the User Experience page, click the drop down next to installation behavior and select Install for system if resource is device; otherwise install for user
  • Click the drop down next to Logon requirement and select Whether or not a user is logged on
  • Click the drop down next to Installation program visibility and select Hidden
  • Set the value for Maximum allowed run time (minutes) to 20 and then click Next

  • On the Requirements page, click Next
  • On the Dependencies page, click the Add.. button to open the Add Dependency page.
  • In the text field next to Dependency group name: enter in Dot Net 4, click the Add… button to open the Specify Required Application dialog box.
  • Navigate through the list of applications and select the .Net Full installer you created in the previous sequence of steps, click the check mark next to the installer in the Deployment types for selected application and then click OK.
  • Once set, click OK

  • Back on the Dependencies page, click Next
  • On the Summary page, click Next
  • On the Completion page, click Close
  • Back on the Deployment Types page of the Create Application Wizard, click Next
  • On the Summary page, click Next
  • On the Completion page, click Close

The console can now be advertised like you normally would.  Just advertise the console install and it will check for and auto install the .Net 4 prerequisites before moving on to the console.  A few steps but certainly worth the effort and considerably more reliable than doing this same process with ConfigMgr 2007!

email

Written by , Posted .
  • http://myITforum.com/myitforumwp/community/members/rodtrent/ Rod Trent

    Great post!

  • http://myITforum.com/myitforumwp/community/members/ben-thorn/ Ben Thorn

    Brilliant post, much appreciated, keep them coming :)

  • Lee Sands

    Great stuff!
    Although I am getting an error that seems to reflect the detection of .Net 4 after it has been installed. I have triple checked what I have typed into the detection rule and I have also confirmed that the registry key is present….any ideas??
    Thanks