Deploying the App-V 5.0 Sequencer and Client
Updated: November 1, 2012
Applies To: Application Virtualization 5.0
The App-V 5.0 Sequencer and client enable administrators to virtualize and run virtualized applications.
Deploy the client
The App-V 5.0 client is the component that runs a virtualized application on a target computer. The client enables users to interact with icons and to double-click file types, so that they can start a virtualized application. The client can also obtain the virtual application content from the management server.
|Installation of the standard version of the App-V 5.0 client on computers that run Windows Server is not supported. Installation of the App-V 5.0 Remote Desktop services client is only supported for RDS enabled servers.|
By default, after you install the App-V 5.0 client, the client information is stored in the registry in the following registry key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ MICROSOFT \ APPV \ CLIENT. When you deploy a virtualized package to a client, the associated package data is stored in the following location: C: \ ProgramData \ App-V. However, this location can be re-configured with the following registry key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ MICROSOFT \ SOFTWARE \ MICROSOFT \ APPV \ CLIENT \ STREAMING \ PACKAGEINSTALLATIONROOT
If App-V 5.0 redirection is enabled, App-V 5.0 always stores data under the %LocalAppData%, and when the corresponding virtual environment shuts down, the data that will be roamed will be zipped up and copied to the %AppData% path. Entries to the %AppData% folder are done using the user context and not system context. To provide redundancy, App-V 5.0 keeps three copies of the compressed data under %AppData%.
The App-V 5.0 client moves the files from %LocalAppData% to %AppData% when it detects that %AppData% is a network share set up for folder redirection. As a benefit of this design, there is always a local copy of the data and offline use is always supported without the need of Offline Files.
The following directories must be available on a local volume for each user that logs into the computer running the App-V 5.0 client:
|App-V 5.0 can’t write to a network drive. Additionally, configuring LocalAppData as a network drive is not supported.|
%APPDATA% \ Microsoft \ AppV \ Client \ VFS.
%LOCALAPPDATA% \ Microsoft \ AppV \ Client \ VFS
For computers running App-V 5.0 SP2:
%APPDATA% \ Microsoft \ AppV \ Client \ VFS \ Package GUID \ VFS directory name
Note App-V 5.0 SP2 supports appdata folder redirection. When the virtual environment is started, the roaming appdata state from the user’s roaming appdata directory is copied to the local cache. Conversely, when the virtual environment is shutdown, the local cache associated with a specific user’s roaming appdata is transferred to the actual location of that user’s roaming appdata directory.
For log file information that is associated with the App-V 5.0 client, search in the following log:
Event logs / Applications and Services Logs / Microsoft / AppV.
Finally, packages that are currently stored on computers that run the App-V 5.0 client are saved to the following location: C:\ProgramData\App-V\<package id>\<version id>.
You can also deploy the App-V 4.6 client side-by-side with the App-V 5.0 client. Client coexistence requires that you add or publish virtualized applications by using either a deployment configuration file or a user configuration file, because there are certain settings in these configuration files that must be configured in order for App-V 5.0 to function with App-V 4.6 clients. When a package is upgraded by using either the client or the server, the package must resubmit the configuration file. This is true for any package that has a corresponding configuration file, so it is not specific to client coexistence. However, if you do not submit the configuration file during the package upgrade, then the package state will not function as expected in coexistence scenarios.
App-V 5.0 dynamic configuration files customize a package for a specific user. You must create the dynamic user configuration (.xml) file or the dynamic deployment configuration file before you can use them. To create the file it requires an advanced manual operation.
When a dynamic user configuration file is used, none of the App-V 5.0 information for the extension in the manifest file is used. This means that the dynamic user configuration file must include everything for the extension that is specific to App-V 5.0 in the manifest file, as well as the changes that you want to make, such as, deletions and updates. For more information about how to create a custom configuration file, see How to Create a Custom Configuration File Using the App-V 5.0 Management Console.
Client Configuration Settings
The App-V 5.0 client stores its configuration in the registry. You can gather some useful information about the client if you understand the format of data in the registry. You can also configure many client actions by changing registry entries.
Configure the client by using the ADMX template and Group Policy
You can use the Microsoft ADMX template to configure the client settings for the App-V 5.0 client and the Remote Desktop Services client. The ADMX template manages common client configurations by using an existing Group Policy infrastructure and it includes settings for the App-V 5.0 client configuration.
|You can obtain the App-V 5.0 ADMX template from the Microsoft Download Center.|
After you download and install the ADMX template, perform the following steps on the computer that you will use to manage Group Policy. This is typically the Domain Controller.
Save the .admx file to the following directory: Windows \ PolicyDefinitions
Save the .adml file to the following directory: Windows \ PolicyDefinitions \ <Language Directory>
After you have completed the preceding steps, you can manage the App-V 5.0 client configuration settings with the Group Policy Management console.
The App-V 5.0 client also stores its configuration in the registry. You can gather some useful information about the client if you understand the format of the data in the registry. You can also configure many client actions by changing registry entries.
Deploy the client by using the Shared Content Store mode
The App-V 5.0 Shared Content Store (SCS) mode enables the SCS App-V 5.0 clients to run virtualized applications without saving any of the associated package data locally. All required virtualized package data is transmitted across the network; therefore, you should only use the SCS mode in environments with a fast connection. Both the Remote Desktop Services (RDS) and the standard version of the App-V 5.0 client are supported with SCS mode.
|If the App-V 5.0 client is configured to run in the SCS mode, the location where the App-V 5.0 packages are streamed from must be available, otherwise, the virtualized package will fail. Additionally, we do not recommend deployment of virtualized applications to computers that run the App-V 5.0 client in the SCS mode across the internet.|
Additionally, the SCS is not a physical location that contains virtualized packages. It is a mode that allows the App-V 5.0 client to stream the required virtualized package data across the network.
The SCS mode is helpful in the following scenarios:
Virtual desktop infrastructure (VDI) deployments
Remote desktop services (RDS) deployments
To use SCS in your environment, you must enable the App-V 5.0 client to run in SCS mode. This setting should be specified during installation. By default, the client is not configured to use SCS mode. You should install the client by using the suggested procedure if you plan to use SCS. However, you can configure an existing App-V 5.0 client to run in SCS mode by entering the following PowerShell command on the computer that runs the App-V 5.0 client:
set-AppvClientConfiguration -SharedContentStoreMode 1
There might be cases when the administrator pre-loads some virtual applications on the computer that runs the App-V 5.0 client in SCS mode. This can be accomplished with PowerShell commands to add, publish, and mount the package. For example, if a package is pre-loaded on all computers, the administrator could add, publish, and mount the package by using PowerShell commands. The package would not stream across the network because it would be locally stored.
Deploy the Sequencer
The Sequencer is a tool that is used to convert standard applications into virtual packages for deployment to computers that run the App-V 5.0 client. The Sequencer helps provide a simple and predictable conversion process with minimal changes to prior sequencing workflows. In addition, the Sequencer allows users to more easily configure applications to enable connections of virtualized applications.
For a list of changes in the App-V 5.0 Sequencer, see What's New in App-V 5.0.
App-V 5.0 client and Sequencer logs
You can use the App-V 5.0 Sequencer log information to help troubleshoot the Sequencer installation and operational events while using App-V 5.0. The Sequencer-related log information can be reviewed with the Event Viewer. The following line displays the specific path for Sequencer-related events:
Event Viewer \ Applications and Services Logs \ Microsoft \ App V. Sequencer-related events are prepended with AppV_Sequencer. Client-related events are prepended with AppV_Client.
Other resources for deploying the Sequencer and client
You can learn more about MDOP in the TechNet Library, search for troubleshooting on the TechNet Wiki, or follow us on Facebook or Twitter.