Menu

App-V 5 Sequencing Recipe – ConfigMgr 2012 R2 Admin Console

August 8, 2014 - Deployment, SCCM 2012

Sequencing the SCCM Admin Console is always a hassle. Prerequisites like .Net Framework and VC++ redists need to be in place. Sometimes other Microsoft products cannot be installed next to the ConfigManager Admin Console. And custom shortcuts are needed to have a working software package. Each new version brings new challenges!

I will sequence the Microsoft Configuration Manager Console 2012 R2 (aka Admin Console), with some extra’s like the famous Right Click Tools and the SCCM Toolkit (think CMTrace).

Sequencing Environment

Sequencer version: App-V 5.0 SP2 (no Hotfix applied)

Sequencer OS version: Windows 7 x64 with SP1 (reflects the company OS, same patch-level and middleware installed, no anti virus)

image

.NET Framework 4.5 and Silverlight are very important to have installed on both sequencing machine and client machines.

I’m using version .NET Framework 4.5.1 because all client machines have this version installed. If you’re using Framework 4.0, be sure you have the FULL version installed.

Sequencing machine is build like Nicke Kallen suggests: http://www.applepie.se/setup-a-vm-for-packaging

Sequencing Preparations

Get the source files

SCCM 2012 R2 Admin Console

Sources files are copied from the SCCM server, you find them in “Program Files\Microsoft Configuration Manager\tools\ConsoleSetup”

image

ConfigMgr 2012 Powershell Right Click Tools (Now Micro Right Click Tools)

Can be downloaded from http://www.nowmicro.com/rct/

System Center 2012 R2 Configuration Manager Toolkit

ConfigMgrTools.msi

Installation script

To automate the sequencing process I use a batch script to –more or less- silently install the admin console and extra tools. (place in the “c:\temp” folder)

“C:\Temp\ConsoleSetup.exe” /q TargetDir=”C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole” EnableSQM=0 DefaultSiteServerName=YourSERVERNAMEorALIAS.FQDN.BLA

msiexec /i “c:\temp\Right Click Tools.msi” /qn

msiexec /i “c:\temp\ConfigMgrTools.msi”

regedit /s “C:\Temp\ReportBuilder.reg”

I don’t use the “/qn” msiexec parameter for ConfigMgrTools.msi, because I don’t want to install all features (you could make a transform file to accomplish a silent installation, but I don’t think it’s worth the effort).

Sequencing Steps

  • Copy sources files and installation script to the sequencing machine, create snapshot.
  • Start the sequencer
  • PVAD; C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole
  • Launch install-batch script. This will install the Admin Console, Right-Click Tools and the SCCM Toolkit.
  • ConfigMgrTools 2012 R2 Tookit default install (except for the server tools feature).

    image

  • Don’t launch the Admin Console while monitoring as it will generate unnecessary package “clutter”.

     

    After the monitoring phase clean up your sequence!

    Remove shortcuts: EULA, HELP, ..

    Issues

    The console don’t behaves and crashes

    At first the console seems to work, it launches. But as soon as you add resources to a collection for example, it crashes or you simply cannot add devices.image

    My workaround for this issue was to use a custom shortcut to “Microsoft.ConfigurationManagement.exe” using the Dynamic Configuration XML’s.

    Change original “pointer” to the shortcut from:

    <Target>[{AppVPackageRoot}]\AdminConsole\bin\Microsoft.ConfigurationManagement.exe</Target>

    To:

    <Target>C:\ProgramData\App-V\PKG-GUID\VERSION-GUID\Root\AdminConsole\bin\Microsoft.ConfigurationManagement.exe</Target>

    image

    More on this issue at the Technet Forums and MS Blogs.

    Console crash since R2

    Starting from the R2 version the Admin Console crashes as soon as you create a collection or add resources to an existing collection (not limited to these actions!).

    image

    Add Resources:

    image

    Event Logs pointed to .NET Runtime errors.

    image

    Application: Microsoft.ConfigurationManagement.exe

    Framework Version: v4.0.30319

    Description: The process was terminated due to an unhandled exception.

    image

    Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.0.7958.1000, time stamp: 0x5230d1aa

    Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409,

    The custom shortcut doesn’t fixes this issue this time (R2).

    After troubleshooting a numerous of things, I fixed this by one the following actions:

  • Don’t use a fake PVAD, install the Admin Console to your PVAD.
  • Don’t start the Console while monitoring
  • Cleanup your sequence.
  •  

    Custom shortcut to “Microsoft.ConfigurationManagement.exe” is still needed in my environment (AppV 5 Publishing Server).

    4 thoughts on “App-V 5 Sequencing Recipe – ConfigMgr 2012 R2 Admin Console

    Jonas Berends

    Hi Ben,

    Nice one, thanks for that! I especially like the Now Micro right-click tools – didn’t know that one yet.

    One question: what is in your reportbuilder.reg file, and what is its use?

    Cheers,
    Jonas

    Ben De Vriese

    Hey Jonas,

    Had an issue with the report-feature of ConfigMgr 2012 some time ago, that registry key fixed that. But I don’t remember the details. Can’t find any trace in my documentation either, sorry.

    But here’s the reg file anyway:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ConfigMgr10\AdminUI\Reporting]
    “ReportBuilderApplicationManifestName”=”ReportBuilder_3_0_0_0.application”

    Jonas Berends

    Hi Ben,

    As opposed to “ReportBuilder_2_0_0_0.application” which seems to be the standard value in my manual installs then? OK, won’t touch it for now as I do not seem to have any issues. Thanks for the quick reply!

    Jonas

    Kenneth Sundby

    Hi,

    The registry fix is so that you can launch the report viewer from the console. For some reason they forgot to update the registry to point towards the correct manifest version, so when you try to open a report you will get an error without this fix 🙂

    Comments are closed.