How the App-V 4.6 Service Pack 1 Sequencer helps you implement best practices

The new App-V 4.6 SP1 Sequencer introduces some major changes in the user interface and the sequencing workflow. These changes have been designed to assist the sequencing engineer with virtualising applications in App-V while aligning with best practices.

If you’re a seasoned sequencing engineer the Sequencer has some major UI changes, but let me show you why I think that once you’ve had an opportunity to use the new Sequencer, you’ll be smiling. (Minimise during sequencing is back too which will make plenty of people even happier)

Sequencer Installation

Built-in best practices are implemented right from installation – the first change you’ll see is during the installation of the Sequencer. Setup will ask for the virtual drive letter:

If this drive letter does not already exist as an actual partition or volume within your sequencing computer, Setup will create a drive substitution for you. (The substitution is to %ProgramData%\Microsoft\Application Virtualization Sequencer\Package Root\).

Another best practice is implemented during installation – the creation of a dummy ODBC connection. Both a system DSN and a user DSN for the current user are created:

Sequencer Templates

App-V 4.6 SP1 introduces Sequencer Templates which can be used to standardise commonly applied settings when you create new virtual application packages. This will help streamline the process of creating virtual application packages, especially if your own best practices differ from the default settings.

Sequencer Templates (.sprt files) are single XML files than can be copied into your sequencing VM and applied to new packages. These will become an important part of any packaging team’s methods for standardising their packages.

A master template or templates for specific application types can be used to ensure everyone is using the same settings for their sequences.

Preparing for Sequencing

When sequencing an application the Sequencer will now ensure that the sequencing computer has been prepared correctly. In the example below you can see four issues that the Sequencer has detected:

Windows Defender is running

The Windows Search service is running

Some applications are open before starting the sequencing process

My virtual machine has not been reverted to a clean state before starting wizard

The Sequencer is recommending a solution for each issue before proceeding:

Getting this type of information directly from the Sequencer is a fantastic feature because it will assist in creating successful and cleaner packages.

Creating Packages

The SP1 Sequencer now directly assists in capturing the type of application you are sequencing. Making a decision at this point about the type of application changes the sequencing workflow so that the Sequencer can guide you through the capture process.

Getting this process correct is especially important for add-ons or middleware components that you might link to a primary application using Dynamic Suite Composition.

Editing Packages

The same approach has been taken when editing packages:

By choosing the package edit task within the Sequencer, you will be guided through an edit or update task, making it simpler to generate a new version of a package. The workflow will change depending on the task that you choose.

Install Phase

During the installation phase, the Sequencer will prompt for a package name. You’ll notice here that the Sequencer is auto-creating the Primary Virtual Application Directory and using a name that does not adhere to a previous best practice of using an 8.3 naming convention:

Behind the scenes the Sequencer is taking care of the 8.3 folder for you, making sequencing that one step simpler. You can however, continue using your existing naming conventions if you have them by using the Edit (Advanced) check box.

At this point, the Sequencer will also remind you to where to install the application you are sequencing:

A small UI change, but a simple one that will assist those new to the sequencing process.

First Run Tasks

In previous versions of the Sequencer, it wasn’t very clear that you should perform first run tasks after installing an application. First run tasks are now placed front and centre in a separate step during the sequencing process:

Identifying potential virtualization issues

How do you record excluded files and registry keys or even features that won’t work once an application has been virtualised and isolated from the OS today? It’s not simple and I would guess that for many organisations this information is not documented. Thankfully the new Sequencer exposes much of this information with package reports – excluded files and unsupported application features (such as shell extensions) are recorded and listed and the end of the sequencing process.

The screenshot below shows a couple of examples when sequencing Adobe Reader – shell extensions that won’t be available once Reader has been virtualised and files that have been excluded from the package:

Opening these items will display detailed information:

This information is then saved for each package in a new file named report.xml: