Creating and managing App-V virtualized applications
Applies to:
- Windows 10
- Windows 11
After you've properly deployed the Microsoft Application Virtualization (App-V) sequencer, you can use it to monitor and record the installation and setup process for an application to be run as a virtualized application.
For more information about configuring the App-V sequencer, sequencing best practices, and an example of creating and updating a virtual application, see the Microsoft Application Virtualization 5.0 Sequencing Guide.
Note
The App-V Sequencer cannot sequence applications with filenames matching "CO_<x>" where x is any numeral. Error 0x8007139F will be generated.
Sequencing an application
You can use the App-V Sequencer to perform the following tasks:
Create virtual packages that can be deployed to computers running the App-V client.
Upgrade existing packages. You can expand an existing package onto the computer running the sequencer and then upgrade the application to create a newer version.
Edit configuration information associated with an existing package. For example, you can add a shortcut or modify a file type association.
Note
You must create shortcuts and save them to an available network location to allow roaming. If a shortcut is created and saved in a private location, the package must be published locally to the computer running the App-V client.
Convert existing virtual packages.
The sequencer uses the %TMP% \ Scratch or %TEMP% \ Scratch directory and the Temp directory to store temporary files during sequencing. On the computer that runs the sequencer, you should configure these directories with free disk space equivalent to the estimated application installation requirements. Configuring the temp directories and the Temp directory on different hard drive partitions can help improve performance during sequencing.
When you use the sequencer to create a new virtual application, the following listed files are created. These files comprise the App-V package.
- .msi file. This Windows Installer (.msi) file is created by the sequencer and is used to install the virtual package on target computers.
- Report.xml file. In this file, the sequencer saves all issues, warnings, and errors that were discovered during sequencing. It displays the information after the package has been created. You can us this report for diagnosing and troubleshooting.
- .appv file. This file is the virtual application file.
- Deployment configuration file. The deployment configuration file determines how the virtual application will be deployed to target computers.
- User configuration file. The user configuration file determines how the virtual application will run on target computers.
Important
You must configure the %TMP% and %TEMP% folders that the package converter uses to be a secure location and directory. A secure location is only accessible by an administrator. Additionally, when you sequence the package, you should either save the package to a secure location or make sure that no other user is allowed to log in during the conversion and monitoring process.
The Options dialog box in the sequencer console contains the following tabs:
General. Use this tab to enable Microsoft Updates to run during sequencing. Select Append Package Version to Filename to configure the sequence to add a version number to the virtualized package that is being sequenced. Select Always trust the source of Package Accelerators to create virtualized packages using a package accelerator without being prompted for authorization.
Important
Package Accelerators created using App-V 4.6 are not supported by App-V.
Parse Items. This tab displays the associated file path locations that will be parsed or tokenized into in the virtual environment. Tokens are useful for adding files using the Package Files tab in Advanced Editing.
Exclusion Items. Use this tab to specify which folders and directories shouldn't be monitored during sequencing. To add local application data that is saved in the Local App Data folder in the package, click New and specify the location and the associated Mapping Type. This option is required for some packages.
App-V supports applications that include Microsoft Windows Services. If an application includes a Windows service, the service will be included in the sequenced virtual package as long as it's installed while being monitored by the sequencer. If a virtual application creates a Windows service when it initially runs, then after installation, the application must be run while the sequencer is monitoring for the Windows Service to be included in the package. Only services running under the Local System account are supported. Services configured for AutoStart or Delayed AutoStart are started before the first virtual application in a package runs inside the package’s Virtual Environment. Windows Services that are configured to be started on demand by an application are started when the virtual application inside the package starts the Service via API call.
- Automatically provision your sequencing environment using Microsoft Application Virtualization Sequencer (App-V Sequencer)
- How to Sequence a New Application with App-V
- Automatically sequence multiple apps at the same time using Microsoft Application Virtualization Sequencer (App-V Sequencer)
App-V shell extension support
App-V supports shell extensions. Shell extensions will be detected and embedded in the package during sequencing.
Shell extensions are automatically embedded in the package during the sequencing process. When the package is published, the shell extension gives users the same functionality as if the application were locally installed.
Requirements for using shell extensions
- Packages that contain embedded shell extensions must be published globally. The application requires no extra setup or configuration on the client to enable the shell extension functionality.
- The “bitness” of the application, Sequencer, and App-V client must match, or the shell extensions won’t work. For example:
- The version of the application is 64-bit.
- The Sequencer is running on a 64-bit computer.
- The package is being delivered to a 64-bit App-V client computer.
The following table lists the supported shell extensions:
| Handler | Description |
|---|---|
| Context menu handler | Adds menu items to the context menu. It's called before the context menu is displayed. |
| Drag-and-drop handler | Controls the action where right-click, drag and drop, and modifies the context menu that appears. |
| Drop target handler | Controls the action after a data object is dragged and dropped over a drop target such as a file. |
| Data object handler | Controls the action after a file is copied to the clipboard or dragged and dropped over a drop target. It can provide more clipboard formats to the drop target. |
| Property sheet handler | Replaces or adds pages to the property sheet dialog box of an object. |
| Infotip handler | Allows retrieving flags and infotip information for an item and displaying it inside a pop-up tooltip upon mouse hover. |
| Column handler | Allows creating and displaying custom columns in Windows Explorer Details view. It can be used to extend sorting and grouping. |
| Preview handler | Enables a preview of a file to be displayed in the Windows Explorer Preview pane. |
Copy on Write (CoW) file extension support
Copy on write (CoW) file extensions allow App-V to dynamically write to specific locations contained in the virtual package while it's being used.
The following list shows the file types that can exist in a virtual package under the VFS directory, since App-V 5.1, but which can't be updated on the computer running the App-V client. All other files and directories can be modified.
- .com
- .exe
- .dll
- .ocx
Modifying an existing virtual application package
You can use the sequencer to modify an existing package. The computer on which you do this modification should match the chip architecture of the computer you used to create the application. For example, if you initially sequenced a package using a computer running a 64-bit operating system, you should modify the package using a computer running a 64-bit operating system.
For more information, see How to Modify an Existing Virtual Application Package.
Creating a project template
An App-V project template (.appvt) file is a project template that can be used to save commonly applied, customized settings. You can then more easily use these settings for future sequencings. App-V project templates differ from App-V Application Accelerators because App-V Application Accelerators are application-specific, and App-V project templates can be applied to multiple applications. Additionally, you can't use a project template when you use a Package Accelerator to create a virtual application package. The following general settings are saved with an App-V project template:
A template can specify and store multiple settings as follows:
- Advanced Monitoring Options. Enables Microsoft Update to run during monitoring. Saves allow local interaction option settings
- General Options. Enables the use of Windows Installer, Append Package Version to Filename.
- Exclusion Items. Contains the Exclusion pattern list.
Starting with Windows 10 version 1703, running the new-appvsequencerpackage or update-appvsequencepackage cmdlets automatically captures and stores all of your customizations as an App-V project template. If you want to make changes to this package later, your customizations are automatically loaded from this template file.
Important
If you attempt to load another template through the TemplateFilePath parameter while already having an auto-saved template, the customization value from the parameter will override the auto-saved template.
For more information, see How to Create and Use a Project Template.
Creating a package accelerator
Note
Package accelerators created using a previous version of App-V must be recreated using App-V.
You can use App-V package accelerators to automatically generate a new virtual application package. After you've successfully created a package accelerator, you can reuse and share the package accelerator.
In some situations, to create the package accelerator, you might have to install the application locally on the computer that runs the sequencer. In such cases, you should first try to create the package accelerator with the installation media. If multiple missing files are required, you should install the application locally to the computer that runs the sequencer, and then create the package accelerator.
After you've successfully created a Package Accelerator, you can reuse and share the Package Accelerator. Creating App-V Package Accelerators is an advanced task. Package Accelerators can contain password and user-specific information. Therefore you must save Package Accelerators and the associated installation media in a secure location, and you should digitally sign the Package Accelerator after you create it so that the publisher can be verified when the App-V Package Accelerator is applied.
For more information, see the following articles:
- How to Create a Package Accelerator
- How to Create a Virtual Application Package Using an App-V Package Accelerator
Sequencer error reporting
The App-V Sequencer can detect common sequencing issues during sequencing. The Installation Report page at the end of the sequencing wizard displays diagnostic messages categorized into Errors, Warnings, and Info depending on the severity of the issue.
You can also find additional information about sequencing errors using the Windows Event Viewer.