App-V: Prepare an application for sequencing
Before sequencing an application, understand what it does and whether it can be virtualized. Keep the 80–20 rule in mind. The App-V Sequencer monitors installation and records the files, services and registry settings needed to run the application in a virtual environment. The resulting package can then be delivered to an end user.
Applications or services that install boot or device drivers cannot be sequenced. Some applications can be packaged if their dependencies are installed on the host outside the App-V environment. For example, a USB print driver can be installed locally while a scanning application is sequenced. The virtual application then depends on services available on the host.
Sequencer machine configuration
A good package starts with preparation and a documented internal process. For every application we sequence, that process should help us make the best package we can and allow the work to continue when the usual packager is out of the office.
This checklist covers preparation and the sequencing process:
- Sequence on a machine that matches the production clients: the same operating system, patch level and core applications.
- Choose a physical or virtual machine based on the application and environment. I prefer Hyper-V virtual machines, but host dependencies sometimes require a physical machine.
- Add a hard disk or create a virtual disk for the Q:\ drive.
- Shut down programs and services such as virus scanning, Windows Search, Windows Update, Defender and the SCCM client.
- Create a step-by-step recipe. Obtain the information, binaries and configuration files from the application owner or requester before starting.
- Familiarize yourself with the installation before sequencing.
- In Windows Explorer Folder Options, enable “Show Hidden Files, folders and drives”, show “Protected operating system files” and enable “Launch folder windows in a separate process”. This helps reveal files created during installation.
- Extract the installation files before running the installation. The Sequencer captures interactions throughout the monitoring process.
- After installing App-V Sequencer, leave it closed until you are ready to sequence. Creating a snapshot with the Sequencer already open and reverting to it will generate the same package GUID.
- Create an 8.3 directory name, for example Q:\MSWORD.v01.
- Start App-V Sequencer and follow the wizard to create the virtual package.
- Use a consistent package name, for example Microsoft_Word_2010-MNT.
MNT = mounted on the Q:\ drive, when the destination folder can be changed.
VFS = virtual file systems, when the application installs on C:\ without an option to change the location. - Run setup and choose a custom installation if available. Install all required components.
- Run the executable and configure the application settings, such as disabling automatic updates. Close the application and run it a few more times.
- Stop monitoring and check the Q:\MSWORD.v01\VFS folders. Microsoft installations create C:\MSOCache to store installation binaries. Start the monitoring wizard again and move the contents of MSOCache to a library to reduce the package size.
- Add or remove the applications to publish to the user. Notepad, Internet Explorer and other applications detected by the Sequencer are often unnecessary. Know your application.
- Save the application with the name chosen at the start, and use a consistent folder structure on the server's Content file share.