From Field Book on Citrix/ App-V Integration: Ch9 – Dual Admin Mode Configuration

by Tim Mangan, CTP, Boston CUGC Leader

Chapter 9: If I use the App-V Server do I configure the App-V Client for the Publishing Server?

An on-going set of experiences in helping customers implement App-V in Citrix environments.


The customer is using XenApp and/or Xen Desktop 7.x with App-V 5.1 and is using the App-V Publishing Server (Dual Admin Mode). The logins are taking a long time.


Not applicable.


Citrix supports App-V Integration into Studio in two forms, which they refer to as “Dual Admin” and “Single Admin.” 

Dual Admin mode represents the original integration, and it leverages the App-V Server to aid in application delivery to the machine with the VDA. Single Admin mode was added in 7.9 (but only for apps and not connection groups; that was added in 7.11) but allows for working without an App-V Server  by working with the App-V Packages on the file-share directly.

If you use XenApp and/or Xen Desktop with the Dual Admin Mode integration to the App-V Server infrastructure, the virtual apps are automatically added and published, but it is the CtxAppLauncher executable that is responsible for working with the Publishing Server. When you configured Dual Mode in Studio, you entered the URL for the Management and Publishing Servers.  Studio only works with the Management Server, but passes on the Publishing Server through the Broker to CtxAppLauncher, which ensures the App-V Client is configured for the server.


While you are responsible for all other configuration of the App-V client (best done using the Microsoft GPO for the App-V client), you should not configure the App-V Client Publishing on VDAs in this scenario.  Citrix will automatically add a publishing entry into the App-V client configuration for you, so if you add your own configuration to the Publishing Server you end up with two entries.  This causes the publishing sync to run twice on every session creation (logon) on the VDA, causing no harm but slowing things down. 

Removing the publishing configuration from the GPO to those devices solved the issue.

Leave a Reply