Share this post

XenApp 7.5 is an application and desktop virtualization solution that delivers Windows applications as a secure mobile service to any device, over any network, while providing a touch-enabled user experience that looks and feels native.

In this post I will concentrate only on features that are missing or have significantly changed in latest version of XenApp. I just installed XenApp 7.5 in my lab and it can happen that I will update this post in near future or will create additional post to inform you about my new findings.

Features that are not currently in or are no longer supported by this release are described the post related to missing features in XenDesktop 7.

The following table helps to map XenApp 6 functional elements to new features introduced in XenApp 7:

XenApp 6.5XenApp 7.5
Independent Management Architecture (IMA)FlexCast Management Architecture (FMA)
FarmDelivery Site
Worker GroupSession Machine Catalog

Delivery Group
WorkerVirtual Delivery Agent

Server OS Machine

Desktop OS Machine
Zone and Data CollectorDelivery Controller
Delivery Services ConsoleCitrix Studio and Citrix Director
Publishing applicationsDelivering applications
Data storeDatabase
Load EvaluatorLoad Management Policy
AdministratorDelegated Administrator



Let’s talk about missing features. The most commonly seen complains about lack of functionalities are the following:

1. It is not possible to limit only one instance of application for each user or limit the instances of application allowed to run in server farm.

This is a feature used very often where number of running application instances must be strictly controlled. In XenApp 7.5 control options no loner exist in Citrix Studio.
Workaround: See citrix document related to XenApp 6.5 here: CTX135154. This is different from setting concurrent limits on the properties of a published application which allows for limiting an application instance on a per-user or per-farm basis but should meet some business requirements. I will verify this solution on XenApp 7.5 in next coming days.

2. Load Management Policy cannot be applied to application

A common use of load evaluator is to limit the number of user load for a particular application on the XenApp servers. In XenApp 7.5, the load evaluator has moved into Citrix policies but it cannot be applied to specific applications anymore.
Workaround: Unfortunately, there is no easy way to achieve something similar without intense scripting.

3. Worker node can only belong to 1 Delivery Group.

In XenApp 6,5 it was possible to to publish application to servers and/or to worker groups. In XenApp 7.5, applications are published to delivery group, and a worker node cannot be assign to multiple delivery groups. So if your delivery group with App1 has the 5 servers, you can’t assign 2 of the 5 servers to another delivery group with App2.
Workaround: The powershell command can be used to fix this problem. Use Add-BrokerApplication cmdlet to assign published application to delivery group.

 Add-BrokerApplication-Name"Publised App Name"-DesktopGroup"Delivery Group nr 1"

4. Load Balancing with Worker Group Preference

This is a useful feature in XenApp 6.5 where you can set a preferred groups of XenApp servers to run your applications. You can use this feature to failover users to a backup group of XenApp servers if their local XenApp servers are not available. In XenApp 7.5,  this option no loner exist in Citrix Studio.
Workaround: The powershell command can be used to fix this problem. Use Add-BrokerApplication cmdlet to assign priority to application:

Add-BrokerApplication-Name"Publised App Name"-DesktopGroup"Delivery Group nr 1"-priority1

By default the priority is O and this is a highest priority. The priority can be used to either load balance the group, when both Delivery Groups have the same priority, or in failover order as the priority descends. By setting different priority to a application from different delivery groups, the XenApp Controller will direct user connections to servers from delivery group with the higher priority.