Hello again folks! Today I’m going to step you through how to use App-V 5.0 to sequence the Configuration Manager 2012 Administrator Console. In this example, I’m also installing SP1 and CU1 so the console will be the latest and greatest (as of today). If your ConfigMgr Administrator Console is not at this exact same version, these steps should still work for you, however I have only tested it on 2012 SP1 and 2012 SP1 CU1.

A shout-out goes to Senior Premier Field Engineer and App-V Guru Ryan Cobb for his assistance along the way with tackling this one!

If you haven’t yet deployed the App-V 5.0 client out to your ConfigMgr 2012 SP1 clients, be sure to visit my blog posting here to see how that is done. Enough of that, let’s get on with the fun stuff!

Step 1: Sequencing the ConfigMgr Admin Console

Pre-reqs! In order to successfully accomplish these steps, you will need to first download MDOP 2012 or 2013 from your volume license site (of course you must have an MDOP license for this to be downloadable) and grab the bits from the App-V directory. You will need to install the App-V Sequencer on a clean and pristine client OS. I prefer using Windows 7 SP1 in a Hyper-V environment so that I can quickly and easily revert it to a previous checkpoint, thereby allowing me to sequence applications efficiently without having to re-install the OS each time.

So, go ahead and launch your App-V Sequencer!

At this point, the App-V Sequencer will check for the following conditions:

Windows Search Service (stop and disable)

Antivirus Client (disable)

SMS Agent Host Service (stop and disable)

I also recommend having a clean & pristine Windows Sequencer PC with these settings applied just before taking a snapshot/creating a checkpoint of it. Additionally you also may want to insure the Configuration Manager Client Health scheduled task is disabled or it may unexpectedly fix your disabled SMS Agent Host service in the middle of sequencing your application and begin deploying apps and updates to your nice clean OS!

After correcting any issues that might have been identified during the preparation check, click Next to proceed.

Select “Standard Application (default)” and click Next.

Browse to the path to the ConsoleSetup.exe in the \Tools sub-directory of your ConfigMgr 2012 installation and click Next.

Enter the FQDN of the site server you want the Admin Console to automatically connect to when launched, and click Next.

For the Installation folder, enter the same path as you entered in the Primary Application Virtual Directory above. Click Next.

Select the appropriate radio button as you desire for the CEIP and click Next.

Now click Install, and prepare to virtually be amazed!

Now the Configuration Manager Admin Console will begin installing using our options.

Click Finish once the install is completed. Uncheck the “Start the Configuration Manager console after you close the Setup Wizard” box and click Finish. The App-V sequencer will give you a chance to execute the Admin Console and Remote Control apps, so it’s not required to do so at this point.

Next, install KB2817245 which is the CU1 update for SP1. If you are not on CU1, you can skip this step. The most important thing to remember is that you want your console to be at a compatible version with your site server, or you may experience regular console crashes due to version incompatibilities.

If you click the drop-down menu in the upper left corner, and select “About Configuration Manager”, the Configuration Manager Admin Console version should be 5.0.7804.1202 which is the SP1 CU1 version.

Once this is confirmed, fully close both applications and click Next in the App-V Sequencer wizard.

Once again, the sequencer will collect system changes.

The “Installation Report” dialog will appear warning you that some files were excluded from the package. Review this is desired (this message is expected and normal), and click Next.

Unless there is additional customizations you desire to make at this point, leave the “Stop now” radio button and click Next on the Customize dialog.

Select “Continue to modify package without saving using the package editor” and click Next.

Another warning about files being excluded from the package will appear. Again, this is normal, so just click Close.

Now you will be on the Properties tab of the App-V Sequencer. Copy both the Package GUID and PackageVersion GUID information into your favorite text editor.

Feel free to review the settings in your sequenced Admin Console, and when finished, click “File” and “Save” and save the package to your ConfigMgr applications & packages sources share. Once done saving, exit out of the Application Virtualization Sequencer application.

Step 2: Creating the Application in Configuration Manager 2012

When the “Create Application Wizard” appears, select “Microsoft Application Virtualization 5” for the Type, and for the location, browse to the folder you copied the contents of your newly sequenced Admin Console to, and click Next.

Review the imported information, and then click Next.

If desired, populate any additional information about the application and click Next.

Confirm the settings, click Next and then click Close.

At this point, with the large majority of applications, you are normally ready to deploy and begin testing. Fortunately (or unfortunately, depending on your view), this is your lucky day. I’ve sequenced ConfigMgr 2012 Admin Console (with and without SP1 and CU1), and found that using the console without ANY modification of the XML files included within the package directory, you will have issues with the console crashing. For example, if you right-click any collection, and click “Properties”, you will get a .NET crash. This is a known issue with a few specific applications which can be worked around by changing the target path of the shortcut of the application.

*NOTE*: This is NOT, and should NOT be considered to be a permanent or long-term workaround to this issue. By doing these steps, you will also have to insure that you follow them again each time you upgrade this specific sequenced application. By hard-coding the shortcuts in the XML files, an update to the sequenced version will not automatically launch the new version when deployed to the clients. Instead the old version will launch, and you will need to manually update the modified shortcut paths within the XMLs in order to insure your clients are running the new version. (The “VersionGUID” value is all that will need modified to match each new version you create.)

Using your favorite text editor, open up the {appname}_DeploymentConfig.xml file which is located inside the package directory with the .appv file that was just created.

Scroll down until you find the section just under “<Shortcut>” that appears as follows:

Now, follow these same steps one more time - this time modifying the {appname}_UserConfig.xml file inside the package directory.

This completes the sequencing and application creation part of the Configuration Manager 2012 Admin Console.

Now you can distribute the modified content out to your desired DPs, and deploy the application out to all your ConfigMgr admins! Be sure to create a collection of machines with the ConfigMgr Admin console installed so you can upgrade them easily in the future!

… And be sure to visit my other blog post titled “Deploying the App-V 5.0 client using Configuration Manager 2012 SP1” if you haven’t yet deployed the App-V 5 client out yet. The App-V client itself has some dependencies to set up, so if they are not already installed, this admin console (as well as any other .appv package you create) will not execute!

Hello, congratulations for the post, sorry for my english, but it is not my mother tongue. I ran the esattamante workarount recommended to you by changing the {appname} _DeploymentConfig.xml. the problem of the crash. NEt still present.

Do you know what could be the problem? thx Nicola

Nicola

4 Jun 2013 9:23 AM

I forgot, I also made the same change in the file {appname} _UserConfig.xml, but the problem remains

So this leads me to believe that maybe your .xml updates did not make it into the application properly or the revision you're pushing to the client does not have the updated .xml. If you look at the xml files in the client's cache in the application's directory, are they the pre-modified xml's or do they have your modifications in them? Did you create the application in CM2012 before or after you modified the XML files? If you created it before, then go to your deployment method and update the package content to make sure the updated XMLs are in the application.

Nicola

4 Jun 2013 9:49 PM

by the time I made the standalone installation locally with double click on the msi file. Tomorrow I'll try directly from cm2012. I think first change the xml files, then when everything is ok i will create the application in cm2012. Right?

Yes, or at least verify you've edited the XMLs in the source directory, and then update the content to make sure that revision is on the DP. Then after the app installs if it still doesn't work, look at the XML files in your client's ccmcache and verify that the modified XML files arrived to the client.

Nicola

5 Jun 2013 1:39 PM

Hi, Thank you so much for your help, when I distribute with CM2012 everything works perfectly.

App-V client has VC++ dependencies and installs what it needs as long as you use the launcher .exe vs the msi. SCCM Client installs its dependencies as well. If you do have or create VC++ packages, make absolutely certain they're the exact correct version that the client will install - tons of version variations out there.

KathyM

5 Nov 2013 7:06 PM

Is there an equivalent command to get this working with 4.6 SP2?

Roger

3 Dec 2013 10:03 AM

Hi Kathy, i also have problems with APPV 4.6.SP2 and SCCM2012R2 console.

I get the DOTNET crashes during sequencing can't read the properties of for example a package.

after setup the console works.

Jason

10 Dec 2013 5:32 PM

Roger,

I think the DONNET 80004005 crashes are fixed by installing .NET 4.5 full.

My issue is after the console launches it locks the mouse. Everything seems to work but why would it lock the mouse?