Deploying the ConfigMgr Console as a ConfigMgr Application

The Configuration Manager Console is the primary tool used to manage an organization’s Configuration Manager environment. Currently, when using the ConsoleSetup.exe file to install the Configuration Manager Console silently, the R2 RTM version of the console is installed. Also, the Report Viewer is left out of the install. Now Micro’s team of expert engineers presents the process for creating a Configuration Manager application that will silently install the console and the report viewer while also applying the latest cumulative update.

Getting Started

  • The installation files for the console can be found on the Configuration Manager (ConfigMgr) server in the Tools folder (under the ConfigMgr install directory).
  • The installation files for the latest cumulative update (CU4) can be found on the ConfigMgr server at C:Program FilesMicrosoft Configuration ManagerhotfixKB3026739AdminConsolei386
  • .NET Framework 4.5 is a prerequisite for the ConfigMgr console. See Now Micro’s previous blog post for instructions on how to create a .NET Framework 4.5 Application.

Deployment

The following steps outline the process for creating an application that installs the ConfigMgr 2012 R2 Console:

  1. On the ConfigMgr server, browse to ConfigMgr_Install_Directorytools.
  2. Copy the contents of the ConsoleSetup folder to a network share.
  3. On the ConfigMgr server, browse to ConfigMgr_Install_DirectoryhotfixKB3026739AdminConsolei386.
  4. Copy the configmgr2012adminui-r2-kb3026739-i386.msp file to the same network location as in the previous step.
  5. Create a new batch file in the network location where the installation files were copied.
  6. Edit the batch file, and copy the below commands. Then save the file.
    @ECHO OFF
    CLS
    REM Installs and patches the ConfigMgr Console.
    :install
    REM Check for OS architecture, then silently install the console
    IF “%PROCESSOR_ARCHITECTURE%”==”AMD64″ (
    consolesetup.exe /q TargetDir=”C:Program Files (x86)Microsoft Configuration ManagerAdminConsole” EnableSQM=1 DefaultSiteServerName=CM.nowmicro.local
    ) ELSE (
    consolesetup.exe /q TargetDir=”C:Program FilesMicrosoft Configuration ManagerAdminConsole” EnableSQM=1 DefaultSiteServerName=CM.nowmicro.local
    ):patch
    REM Install the current cumulative update using the same properties as the package/program…
    msiexec.exe /p configmgr2012adminui-r2-kb3026739-i386.msp /L*v %TEMP%configmgr2012adminui-r2-kb3026739-i386.msp.LOG /q REBOOT=ReallySuppress REINSTALL=ALL REINSTALLMODE=mous

    :fix
    REM As of R2 CU4, silent console installs still leave out the report viewer… Hopefully they fix this soon!
    ReportViewer.exe /q /norestart

    :end

  7. Go to the software library in the Configuration Manager Console, and click Create Application.
  8. On the first window, select the option to Manually specify the application information. Then click Next.
  9. Enter a name for the application. Then click Next.
  10. For App Catalog customizations, do so now on this window. Then click Next.
  11. On the Deployment Types window, click Add to create a new deployment type.
  12. In the new window that appears, choose Script Installer from the drop-down menu. Then click Next.
  13. Enter a descriptive name for the Deployment Type. Then click Next.
  14. In the Content Location box, browse to the network share where the batch file and install files are located.
  15. In the Installation Program box, browse to the batch file.
    ConfigMgr Console - Now Micro
  16. On the Detection Methods window, click the Add Clause button.
  17. In the window that appears, choose Windows Installer from the Setting Type drop-down menu.
  18. Click the Browse button, and navigate to the network share folder.
  19. Select the AdminConsole.msi file. Then click Open.
    ConfigMgr Console - Now Micro
  20. Click Ok.
  21. Click Next.
  22. On the User Experience window, choose Install for System, Whether or not a user is logged in, and Hidden. Then click Next.
  23. On the Requirements window, click Next.
  24. On the Dependencies window, click the Add button to create a new dependency.
  25. Give the dependency group a name.
    CofigMgr Console - Now Micro
  26. Click the Add button to add an application to the dependency group.
  27. Choose the .NET Framework 4.5 Application.
    ConfigMgr Console - Now Micro
  28. Click Ok twice to complete the create of the dependency.
  29. Click Next on the Dependencies window.
  30. Click Next on the Summary window.
  31. Click Finish.
  32. Click Next on the Deployment Types window.
  33. Click Next on the Summary window.
  34. Click Finish.