Sequencing Config Manager Admin Console (MMC) : App-V General Sequencing : Microsoft Application Virtualization (App-V) : Microsoft TechNet Forums


This solution for sequencing the console was given to by my Richard Ruiz MSFT.

1) Install all prerequisites (e.g. MMC 3.0, etc.) and SCCM 2007 Console natively on
your clean WinXP workstation, to the exact location you will be sequencing to.
2) Export the following keys and save to a central location:
3) Turn Off and Delete all changes (VHD) or Reimage your sequencer to a clean state
if physical box
4) Install the Sequencer
5) Install all prerequisites for SCCM 2007 Console (e.g. MMC 3.0, etc.) natively
6) Start your sequence. While monitoring, install SCCM 2007 Console. After
installation is complete, before you stop monitoring, import the 3 exported reg
7) Launch the Console and test functionality, then complete the installation.
8) During the Application Wizard, ensure the shortcut exe path is set to the Q: or
VFS path as necessary and launch the MMC to test functionality at this phase.
9) Finish the sequence and save it.
10) Modify the OSD to include the following dependency:
echo off \n
copy /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Manifests
%windir%\WinSxS\Manifests \n
xcopy /S /y %SFT_MNT%\<Replace with Asset Dir>\VFS\CSIDL_WINDOWS\WinSxS\Policies
%windir%\WinSxS\Policies \n
10) Publish the sequence and test the functionality on your SoftGrid Client.
*NOTE: All prerequisites need to be installed natively on the clients as they were
on the sequencer prior to sequencing.

Sequencing Config Manager Admin Console (MMC) : App-V General Sequencing : Microsoft Application Virtualization (App-V) : Microsoft TechNet Forums

The App-V Blog : Help, my package is too big!


If you sequence enough applications in either SoftGrid or MS App-V you'll eventually run into the issue where your sequenced package is too large to be saved.  We're limited to a 4GB file size so if you have an application that is large enough, or if you package many applications together, chances are you'll eventually run into this.  So how to you get around it?  Well, there's no getting around the 4GB file size limitation so what we're left with is reducing the size of the package.  To do this you could possibly break out your package into two different linked packages using DSC, you could sequence your combined applications separately, you could use compression (mentioned briefly here) or you could simply remove unneeded things from the package to reduce the size.

To give you an example of how removing unnecessary files and folders can reduce the size of your package, let's say you want to  sequence Visual Studio 2005 and the associated patches for it.  If you do this then by default you'll probably end up with a package too large to be saved.  So what we can do to workaround this is to take a look at the package and see if there's anything we can exclude.  In this case there are a large number of files in the hidden folder C:\windows\installer\$patchcache$ that are not used by the application, thus we can safely exclude it from the sequenced package. Here's how we would do that when we sequence the app:

1. Start the SoftGrid Sequencer.
2. On the File menu, click New Package.
3. Click No when you are prompted for help.
4. On the Tools menu, click Options.
5. Click the Exclusion Items tab.
6. Click New.
7. In the Exclusion Item dialog box, type %CSIDL_WINDOWS%\Installer\$PatchCache$ in the Exclude Path box.
8. In the Exclusion Item dialog box, click VFS in the Mapping Type list.
9. Click OK to close the Exclusion Item dialog box.
10. Click OK to close the Options dialog box.
11. On the Tools menu, point to Sequencing Wizards, and then click Package Configuration. The Package Configuration Wizard starts.

Then simply continue with the steps for sequencing in Visual Studio 2005 listed in

Of course this is just one example but the same method can be used for any application that includes files that are not necessarily needed by the virtualized app later on.  What those files are and whether they even exist will depend on the app so you may need to consult your vendor for additional details, but if you run into the issue where your package is too large to be saved there's a chance that excluding certain files can get your in under the limit.

The App-V Blog : Help, my package is too big!

App-V ADM Template Now Available on Connect!

The App-V team is excited to make available a RC version of our App-V 4.5 ADM template. It has just been posted over on the Microsoft Connect site (

The template focus is on registry settings that are well suited to controlling via ADM Template/Group Policy infrastructure and are the most likely to be customized. The ADM Template covers over 40 registry settings, including many of our newest features. For example, the ADM Template includes:

  • New flags that allow overriding the location configured in the Open Software Description (OSD) file for the Application Source Route (ASR), the Icon Source Root (ISR), and the OSD Source Root (OSR) with the registry value located on the client
  • New Auto Load settings including when to target apps and what will start an Auto Load
  • New Reporting Configuration options
  • New Client Logging settings like maximum log size and number of copies to keep
  • All permissions settings visible through the App Virtualization Client
  • Disconnected Operation configuration
  • Client user interface settings that control how the Tray behaves

Our ADM Template allows controlling Preferences (not enforced policies). For an explanation of the difference, please see the Group Policy Team Blog. When you import the template, you need to go through the following steps to see it in the Group Policy Editor.

1.       Click on Administrative Tools

2.       Client View on the menu bar. Click Filtering.

3.       Uncheck the “Only show policies that can be fully managed” check box.

4.       Click OK

We hope this template will make it easier to manage App-V 4.5!

– The App-V Product Team