May 28, 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. App-V and Microsoft User State Virtualization (USV) provide access to applications and data, regardless of location and connection to the Internet.

The following table lists supported versions. (The App-V 4.6 2 client is no longer supported.)


XenDesktop and XenApp versions


Delivery Controller



XenDesktop 7 through current XenApp 7.5 through current

7.0 through current

5.0 SP1

XenDesktop 7 through current XenApp 7.5 through current

7.0 through current

5.0 SP2

XenDesktop 7 through current XenApp 7.5 through current

7.1 through current

5.0 SP3 and 5.1

XenDesktop 7.6 XenApp 7.6


The supported App-V client does not support offline access to applications. App-V integration support includes using SMB shares for applications; the HTTP protocol is not supported.

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 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 and stores user-specific virtual application settings, such as registry and file changes in each user’s profile.

You can launch App-V applications from Server OS and Desktop OS Delivery Groups:

  • Through Citrix Receiver
  • From the Start menu
  • Through the App-V client and Citrix Receiver
  • Simultaneously by multiple users on multiple devices
  • Through Citrix StoreFront

Modified App-V application properties are implemented when the application is started. For example, for applications with a modified display name or customized icon, the modification appears when users start the application.

There is no change in App-V applications performance when a desktop and application Delivery Group is changed to an application-only Delivery Group.

Only an App-V server-based deployment in which an administrator uses an App-V management server and publishing server to manage App-V applications is supported.

Configure App-V

To deliver App-V applications:

  1. Deploy App-V, as described in the instructions in
  2. Publish the App-V applications on the App-V management server. Configure settings such as permissions and File Type Association. These settings already exist if you already deployed App-V.
  3. Optionally, change App-V publishing server settings; see below.
  4. Install the App-V client on VDAs.
  5. During Site creation in Studio, specify the App-V publishing and management server URLs with port numbers. These servers are automatically used by the Delivery Groups.
  6. Install the App-V client in the master image for machine catalogs. Configured the client with settings such as ShareContentStoreMode and EnablePackageScripts. (You do not need to configure the App-V Publishing Server in the master image because it is configured during application launch.)
  7. During Delivery Group creation, select the App-V applications.

The applications are now available.

You can specify or change App-V server information after you create a Site. Select Configuration > App-V Publishing in the Studio navigation pane and then selecting entries in the Actions pane. You can add App-V publishing by specifying URLs with port numbers for the App-V management and publishing servers. You can also edit or remove those addresses. If you refresh the App-V applications, the display indicates if there is a problem connecting to a server and removes entries for applications that are no longer available.

App-V publishing server settings

To change publishing server settings, Citrix recommends using the SDK cmdlets on the Controller.

  • To view publishing server settings, enter Get-CtxAppvServerSetting -AppVPublishingServer <pubServer>.
  • To ensure that App-V applications launch properly, enter Set-CtxAppvServerSetting –UserRefreshonLogon 0.

The following cmdlet changes the settings of the App-V publishing server on the Controller. Not all parameters are mandatory.

``` pre codeblock Set-CtxAppvServerSetting –AppVPublishingServer

-UserRefreshOnLogon -UserRefrehEnabled -UserRefreshInterval -UserRefreshIntervalUnit <Day/Hour> -GlobalRefreshOnLogon -GlobalRefresfEnabled -GlobalRrefreshInterval -GlobalRefreshIntervalUnit <Day/Hour> ``` Note: If you previously used GPO policy settings for managing publishing server settings, the GPO settings override any App-V integration settings, including the previous cmdlet settings. This may result in App-V application launch failure. Citrix recommends that you remove all GPO policy settings and configure the same settings using the SDK. ## Troubleshoot - If the Test connection operation returns an error when you specify App-V management server and publishing server addresses in Studio, check the following: 1. The App-V server is powered on: either send a Ping command or check the IIS Manager (each App-V server should be in a Started and Running state). 2. PowerShell remoting is enabled on the App-V server. If it is not, follow the procedure in <>. 3. The App-V server is added to Active Directory. If the Studio machine and the App-V server are in different Active Directory domains that do not have a trust relationship, from the PowerShell console on the Studio machine, run winrm s winrm/Config/client ‘@(TrustedHosts=”\<App-V server FQDN\>”)’. If TrustedHosts is managed by GPO, the following error message will display: “The config setting TrustedHosts cannot be changed because use is controlled by policies. The policy would need to be set to “Not Configured” in order to change the config setting”. If this message displays, add an entry for the App-V server name to the TrustedHosts policy in GPO (Administrative Templates \> Windows Components \> Windows Remote Management (WinRM) \> WinRM Client). 4. The Studio administrator is also an App-V server administrator. 5. File sharing is enabled on the App-V server: enter \\\\\<App-V server FQDN\> in Windows Explorer or with the Run command. 6. The App-V server has the same file sharing permissions as the App-V administrator: on the App-V server, add an entry for\\\\\<App-V Server FQDN\> in Stored User Names and Passwords, specifying the credentials of the user who has administrator privileges on the App-V server. For guidance, see <>. - If Application discovery fails, check the following: 1. Studio administrator is an App-V management server administrator. 2. The App-V management server is running. Check this by opening the IIS Manager; the server should be in a Started and Running state. 3. PowerShell remoting is enabled on the App-V servers. If either is not enabled, follow the procedure in <>. 4. Packages have appropriate security permissions for the Studio administrator to access. - If App-V applications do not launch, check the following: 1. The publishing server is running. Check this by opening the IIS Manager; the server should be in a Started and Running state. 2. App-V packages have appropriate security permissions so that users can access. 3. On the VDA: - Make sure that Temp is pointing to the correct location, and that there is enough space available in the Temp directory. - Make sure that the App-V client is installed, and no earlier than version 5.0. - Make sure you have Administrator permissions and run Get-AppvClientConfiguration. Make sure that EnablePackageScripts is set to 1. If it is not set to 1, run Set-AppvClientConfiguration -EnablePackageScripts $true. Citrix recommends that you perform this step when you create a master image so that all VDAs created from the master image have the correct configuration. - From the Registry editor (regedit), go to HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Policies\\Citrix\\AppV. Make sure that the AppVServers key has the following value format: AppVManagementServer+metadata;PublishingServer (for example:; - Make sure that CtxAppVCOMAdmin has administrator privileges. During VDA installation CtxAppVCOMAdmin is usually created and added to the Local Administrators Group on the VDA machine. However, depending on the Active Directory policy, this user might lose the administrative association. Run compmgmt.msc and browse to Local Users and Groups Users. If CtxAppVCOMAdmin is not an administrator, edit the group policy or contact your administrator, so that this user account retains its administrative association. 4. On the master image where the App-V client is installed, the PowerShell ExecutionPolicy should be set to RemoteSigned because the AppV client module provided by Microsoft is not signed, and this ExecutionPolicy allows PowerShell to run unsigned local scripts and cmdlets. Use one of the following methods to set the ExecutionPolicy: - Logged in as administrator, enter the following PowerShell cmdlet: Set-ExecutionPolicy RemoteSigned. - From Group Policy settings, go to Computer Configuration \> Policies \> Administrative Templates \> Windows Components \> Windows PowerShell\> Turn on Script Execution. 5. Check the publishing servers: - Run Get-AppvPublishingServer \* to display the list of publishing servers. - Check whether UserRefreshonLogon is set to False. If not, the first App-V application launch typically fails. - With Administrator privileges, run Set-AppvPublishingServer and set UserRefreshonLogon to False. If these steps do not resolve the issues, enable and examine the logs. ## Enable logs To enable Studio logs: 1. Create the folder C:\\CtxAppvLogs. 1. Go to C:\\ProgramFiles\\Citrix\\StudioAppVInegration\\SnapIn\\Citrix.Appv.Admin.V1 and open CtxAppvCommon.dll.config in a text editor such as Notepad, as an administrator. Uncomment the following line: \<add key =”LogFileName” value=”C:\\CtxAppvLogs\\log.txt”/\> To enable VDA logs: 1. Create the folder C:\\CtxAppvLogs. 1. Go to C:\\ProgramFiles\\Citrix\\ Virtual Desktop Agent, and open CtxAppvCommon.dll.config in a text editor such as Notepad, as an administrator. Uncomment the following line: \<add key =”LogFileName” value=”C:\\CtxAppvLogs\\log.txt”/\> 1. Uncomment the following line and set the value field to 1, as shown in the following example: \<add key =”EnableLauncherLogs” value=”1”/\> All configuration-related logs are located at C:\\CtxAppvLogs. The application launch logs are located at: - XenDesktop 7.1 and later, and XenApp 7.5 and later — %LOCALAPPDATA%\\Citrix\\CtxAppvLogs. - XenDesktop 7.0 — %LocalAppData%\\temp\\CtxAppVLogs LOCALAPPDATA resolves to the local folder for the logged in user. Make sure to check in the local folder of the launching user (for whom application launch failed). 1. As administrator, restart the Broker service or restart the VDA machine to start logging.