XenApp 7.5 missing features

//XenApp 7.5 missing features

XenApp 7.5 missing features

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

Role

Scope

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.

By | 2016-12-18T19:21:34+00:00 May 6th, 2014|XenApp|14 Comments

About the Author:

I’m a Citrix Architect with 17 years experience in Microsoft and Citrix infrastructure. I have been working with Citrix since Metaframe 1.8 and my primary focus is on Server, Desktop and Application virtualisation with a preference for Citrix products. I’m an enthusiast of Citrix XenDesktop and Provisioning Server.

14 Comments

  1. Chip Duncan June 11, 2014 at 5:27 pm - Reply

    Question for you. I have a new 7.5 XENAPP environment built with two DDC If I turn off my original (primary) DDC, I would expect the second (alternate) DDC to take up the slack. It doesn’t work that way. If I down the original as I test the environment, the entire farm (SITE) just stops working. I’m thinking something must be established with a powershell command,or in registry with the list of DDCs registry key, or with one or more Config files, but I can’t determine what I should do to resolve this. I want to scale to HA, but without a redundant DDC pair I just can’t get to a point where I’d feel comfortable putting into production testing. Thanks if you can reply to the email address.

  2. Kjetil June 18, 2014 at 12:57 pm - Reply

    Thanks for sharing this nice article as this is important information not mentioned very much elsewhere.

    I have a challenge regarding the missing “limit only one instance of application for each user” and therefore I’m wondering if someone have a good solution to fulfill only one instance of an application per user in a site.

    • Andrzej Gołębiowski June 23, 2014 at 7:14 am - Reply

      Hi,
      I have an idea for a workaround. I will test it this week and let you know.

      Andrzej

      • Stva June 10, 2015 at 2:41 pm - Reply

        Hi,
        I’m very interested in this workaround! Did you find a solution for this?

        I’m currently testing a powershell solution to count the instances via:
        $instance_count=(Get-BrokerApplicationInstance -ApplicationName “”).count
        and afterwards launch the application if the count is below a limit of x

        the problem I’ve: I’ve to run this script on the server where the App needs to be launched(VDA installed) but on the Server with the VDA there is no powershell-snapin for Get-BrokerApplicationInstance…

        Thanks,
        BR

  3. Chip Duncan July 18, 2014 at 8:15 pm - Reply

    Did you ever come up with a solution to this person’s question. I’m having an identical problem. Two DDCs. When I down the primary or the original one, my Storefront’s stops working entirely. I have done propagation as I am supposed to do.

    Question for you. I have a new 7.5 XENAPP environment built with two DDC If I turn off my original (primary) DDC, I would expect the second (alternate) DDC to take up the slack. It doesn’t work that way. If I down the original as I test the environment, the entire farm (SITE) just stops working. I’m thinking something must be established with a powershell command,or in registry with the list of DDCs registry key, or with one or more Config files, but I can’t determine what I should do to resolve this. I want to scale to HA, but without a redundant DDC pair I just can’t get to a point where I’d feel comfortable putting into production testing. Thanks if you can reply to the email address.

    Andrzej Gołębiowski June 16, 2014 at 12:11 pm – Reply
    Hi,
    What do you mean by entire farm /site just stop working ?
    Are the resources displayed in the StoreFront website ?
    When you select Controlers node in the left pane of Citrix Studio are both DDC displayed ?
    Is the StoreFront configured with both DDC ?
    You can contact me at: andrzej[at]citrix24[.]com

    Andrzej Gołębiowski June 16, 2014 at 12:15 pm – Reply
    Did you try to use XDPing tool ?
    Please see: https://blog.citrix24.com/xendesktop-7-deep-dive-part-3-install-configure-vda/

    Kjetil June 18, 2014 at 12:57 pm – Reply
    Thanks for sharing this nice article as this is important information not mentioned very much elsewhere.
    I have a challenge regarding the missing “limit only one instance of application for each user” and therefore I’m wondering if someone have a good solution to fulfill only one instance of an application per user in a site.

    Andrzej Gołębiowski June 23, 2014 at 7:14 am – Reply
    Hi,
    I have an idea for a workaround. I will test it this week and let you know.
    Andrzej

  4. Jonathan Cartagena December 19, 2014 at 5:01 pm - Reply

    Have you had a chance to compare 7.6 yet? Many of the features that were missing from 7.5 came back in 7.6. I came upon your blog while researching features that can be lost if you upgrade from 6.5 to 7.6. Any input would be appreciated. Thank you.

  5. coopercav December 30, 2014 at 5:36 am - Reply

    I have a similar issue to Chip. I originally built 2 DDCs but I’ve now built and added 2 new DDCs, so 4 in total. I want to decommission the original 2 DDCs, so first off I turned them both off just to see what might stop working. I soon identified that 1 of these DDCs in particular being turned off, caused Citrix Studio to perform really badly. By this I mean it took several minutes to open and then whatever I clicked on (Admins, Controllers, Machine Catalogs, Delivery Groups), it took around 30 seconds to return the data. As soon as I turned the DDC back on, all was back to normal and pretty much instant. The other original DDC being turned off made no difference, so that has been subsequently removed from the site and the server left off with no ill effect. So I’m left with the 2 new DDCs, plus one of the original DDCs that seems to be more equal than the others in some way. I cannot find out why this is despite reading many articles, so any suggestions gratefully received.

    • Andrzej Gołębiowski December 30, 2014 at 11:36 am - Reply

      I had similar problem some time ago. I will check my LAB and will send you en email.
      One more question: do you have StoreFront installed on DDC you want to remove ?

      • coopercav December 30, 2014 at 8:09 pm - Reply

        Nope, StoreFront is not installed on the DDCs. Any info you can get back would be appreciated, thanks for checking.
        BTW missed off some basic info sorry, they’re all 2012 R2 Servers with XA7.6.

  6. coopercav January 27, 2015 at 3:17 am - Reply

    Looks from the replies to another post, that this is a known issue and a fix is available as a private hotfix reference LC1891.
    Please see: http://discussions.citrix.com/topic/359249-citrix-studio-issues-only-when-a-particular-ddc-is-turned-off/page-1#entry1853034

  7. coopercav January 28, 2015 at 12:27 am - Reply

    To confirm, LC1891 fixed it for me

Leave A Comment

To protect our website from spam. * Time limit is exhausted. Please reload the CAPTCHA.