Product Documentation

Microsoft Application Virtualization (App-V) integration

Mar 09, 2016

Microsoft Application Virtualization (App-V) lets you deploy, update, and support applications as services. Users access applications without installing them on their own devices. Applications and user settings are preserved whether users are online or offline.

This release supports App-V 5.0.

The App-V 5.0 client does not support offline access to applications.

The App-V 4.6 2 client is no longer supported.

App-V and Microsoft User State Virtualization (USV) provide access to applications and data, regardless of location and connection to the Internet.

App-V integration support includes using SMB shares for applications; the HTTP/HTTPS protocol is not supported.

Microsoft App-V components

See App-V 5.0 Supported Configurations for system requirements.

With App-V, individual applications are transformed from locally installed products into centrally managed services. Applications are available seamlessly without any pre-configuration or changes to operating system settings. App-V contains the following components:
  • Management Server — Provides a centralized console to manage App-V 5.0 infrastructure and deliver virtual applications to both the App-V Desktop Client as well as a Remote Desktop Services Client. The App-V Management Server authenticates, requests, and provides the security, metering, monitoring, and data gathering required by the administrator. The server uses Active Directory and supporting tools to manage users and applications.
  • Publishing Server — Provides App-V Clients with applications for specific users, and hosts the virtual application package for streaming. It fetches the packages from the management server.
  • Client — Retrieves virtual applications, publishes the applications on the client, and automatically sets up and manages virtual environments at runtime on Windows devices. The App‑V Client is installed on the VDA in XenDesktop and stores user-specific virtual application settings, such as registry and file changes in each user's profile.

XenDesktop components

You provide App-V applications to users in XenDesktop Studio using the following components:

  • Studio App-V publishing — Configures access to App-V Publishing and Management servers so that Studio can discover and use App-V applications.
  • Machine catalogs — Collections of physical computers and virtual machines on which applications reside. The machines and their resources are assigned to users through Delivery Groups. During machine catalog creation, the App-V Client must be installed on the master image, and configured through settings such as ShareContentStoreMode and EnablePackageScripts.
    Note: You do not need to configure the App-V Publishing Server in the master image, since it is configured during application launch.
  • Delivery Groups — Provides access to applications for specific groups of users, such as departments or teams.
  • Applications — Delivered to users by assigning them to Delivery Groups