Code Library

Microsoft’s best practices for sequencing applications, walk you through the steps of creating an App-V package, and explain the various options for publishing that application.

Before sequencing, familiarize yourself with installation and use of the target application. Failure to fully understand the configuration and functionality of the application prior to sequencing may lead to an inefficiently sequenced package; one that may not work all. Specifically,

» What are all of the application components needed to complete the installation of the application?

» What updates such as adding new files to the package will need to be performed while sequencing?

» What postinstallation configuration steps need to take place while sequencing?

» How is the application commonly used by its target users?

When sequencing on Windows Vista or Windows 7, configure the User Account Control (UAC) as it will exist on the target desktops. Disable the UAC if it is disabled on your target client machines.

Always use the Comments field in the sequencer to include details about the package you may want to reference in the future. This allows the sequencer to maintain a log of your actions.

Always sequence to a unique, 8.3 directory name. This applies to both the Asset and Installation directories. (‘Q:\MYAPP’ and ‘Q:\MYAPP.001’ are correct, ‘Q:\My Application’ is incorrect.)

Sequence to a folder in the root of the drive, not to a subdirectory (‘Q:\MYAPP’ is correct; ‘Q:\’ is incorrect; ‘Q:\Temp_Junk\MYAPP’ is incorrect). If the suite has multiple parts, install each application in a subdirectory of the Asset Directory. For example, if a package contains a primary application with the Java Client, use Q:\AppSuite as the Asset Directory; sequence the application to Q:\AppSuite\APP; and sequence the Java Client to Q:\AppSuite\JavaClient.

Use globally unique paths and Package names across the set of application sequencings. For example, place multiple Microsoft Office sequencings in the same Asset Directory name. Use a standardized naming scheme that can be incremented, for example, Q:\OFFXP.v1 or Q:\OFFXP.001.

Launch, configure, and test the application during the installation phase. Often this requires performing several manual steps that are not part of the application installation process, such as configuring database connections, copying updated files, etc. Launch and use the application multiple times in order to ensure that all of the most common features are utilized and captured properly by the sequencer. For example, run the application to get past any registration or initial pop-up dialog boxes. Some applications perform different tasks on first launch, second launch, and sometimes subsequent launches. Multiple launches ensure relevant application code makes it into Feature Block 1 during the execution phase. Use the Application Wizard to launch each executable in a suite of applications; do not just browse to their location under All Programs. Doing so may result in the sequencer failing to grab the proper first launch data for the primary feature block.

Some applications have the option to Install on First Use for certain components. Do not sequence applications with this option selected.

Disable any Auto Update features. Some applications have the ability to check a Web site or a server for the latest application updates. Leaving this feature enabled will not break the application, but it may affect version integrity should the application ever be resequenced to apply updates.

There are applications that cannot or should not be sequenced, and there are limitations within App-V. The following list of applications that SHOULD NOT be sequenced is provided by Microsoft:

» Applications (when sequenced) that are over 4 GB in size. If the application is too large the sequencer will not save the application. It will attempt to compress the file.

» Applications that start services at boot time. App-V requires a logged in user initiate the launch of an application.

» Applications that require device drivers. App-V cannot virtualize drivers, but it may be possible to bypass this issue and install the driver locally on the target computer, outside of the App-V package.

» Applications required by several applications for information or access. For example, a program that launches another program. Normally you want to include both programs in the same suite. However, this is not always possible. This is especially true if one of the reasons you are deploying App-V is to avoid application conflicts. Remember that the virtual “bubble” can see the OS and what is installed on it but the OS can neither see the “bubble” nor interact with it.

» Applications that are a part of the operating system, such as Internet Explorer.

» Applications that use COMþ. COMþ is dynamic and initiates at runtime. The sequencer cannot capture this information.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation