Category Archives: Upgrades

How do I define failover servers for delivery groups


Although XenApp 6.5 worker groups do not exist in XenApp 7.x, we’ve seen how similar functionality is available.

Instead of comparing XenApp 6.5 with XenApp 7.x, let’s put some of these new technologies into practice by solving the following design requirement.

  • Define a set of XenApp hosts as failover servers for a group of XenApp hosts delivering the primary app? In addition, the failover servers have the following conditions:
    • The failover servers are a subset of servers hosting their own set of apps
    • The failover servers only host the primary app in the event the primary hosts are unavailable

Continue reading How do I define failover servers for delivery groups

Advertisements

How do I increase Delivery Group (Worker Group) capacity


As described in the blog How do I migrate a XenApp worker group structure, we saw how the use of Delivery groups, application groups and tags allow us to replicate XenApp 6.5 worker group capabilities to XenApp 7.x. There are some operational differences between Worker Groups and Delivery Groups, namely, how do increase the capacity of the delivery/worker group.

One of the more interesting capabilities of XenApp 6.5 worker groups was in the ways an admin could increase worker group capacity.  By adding a server into a worker group, the capacity of the worker group increased.

Many organizations took this approach a step further by basing worker group membership on Active Directory group membership or Active Directory OU membership.  In the XenApp console, each worker group was assigned to a single Active Directory group or OU. Any server in the Active Directory group or OU would be a member of that worker group.

Continue reading How do I increase Delivery Group (Worker Group) capacity

How do I migrate a XenApp worker group structure


In XenApp 6.5, there is the concept of a worker group.  Before that, we called them load managed groups or application silos.  Basically, it is  group of XenApp servers publishing the same set of applications.  If you publish an app on one server, that published app is also available across every other server in the worker group.

workergroup

In XenApp 7.x, you can think of a delivery group like a worker group.  A delivery group is associated to a machine catalog, which is a group of XenApp servers.  If I publish an app within the delivery group, all XenApp servers in that delivery group also publishes the application.

deliverygroupThis is basic functionality, which has been around for a very long time.

However, worker groups also had an interesting characteristic in that XenApp servers could belong to multiple worker groups at the same time.

This means I could have a group of XenApp servers hosting a set of applications.  A subset of those servers could also belong to another worker group publishing another group of applications. The list of resources a particular XenApp server delivers is the sum of the apps from all assigned worker groups.

wgadvBased on this example,

  • XenApp servers 1 and 2 deliver applications 1-4 and 5-6.
  • XenApp servers 3 and 4 deliver applications 1-4 and 7-8.

With XenApp 7.x, the rules for a delivery group are more strict.  A XenApp server can only belong to a single delivery group.  In order to create the same structure in XenApp 7.x that we had in XenApp 6.5, we have to change our approach.

In XenApp 7.x, we need to create a superset of published resources and assign at the Delivery Group layer.  We then use VM and app group tags to create subsets by limiting which applications can be hosted from which XenApp servers.

dgadvThe result is the same as XenApp 6.5.

  • XenApp servers 1 and 2 deliver applications 1-4 and 5-6.
  • XenApp servers 3 and 4 deliver applications 1-4 and 7-8.

Remember this:

  • In XenApp 6.5, you create subsets and merge into supersets
  • In XenApp 7.x, you create supersets and divide into subsets

And to make your move from XenApp 6.5 to XenApp 7.x easier, use your XenApp 6.5 worker group names as your XenApp 7.x app group tags and VM tags.

If you wish to learn more, tune in to Tech Talks To Go, with the first episode focusing on Worker Groups.

Daniel (Follow on Twitter @djfeller)
Citrix XenApp and XenDesktop 7.6 VDI Handbook
XenApp Best Practices
XenApp Videos

How Do I Create ICA Files


In older versions of XenApp (6.5 and earlier), we could create ICA files, which were essentially shortcuts, and email them to users or place them on a static web page.

With XenApp 7.x, ICA files are no longer available.  However, StoreFront provides an alternative with a little option called “Website Shortcuts”.

It is a feature I was unaware of until I needed it for a project.

After you setup your environment with StoreFront servers, Delivery controllers and VDI resources, you do the following:

  1. Launch the StoreFront console
  2. Select “Stores”
  3. Select your store
  4. Select “Manage Receiver for Websites”
  5. Select “Configure”
  6. Select “Website Shortcuts”

This should give you a screen like the following

websiteshortcutIf you plan to host the resource links from an internal web site, you want to add the website’s URL into the websites section. This will trust launches from that location only.  (note: A URL must be entered or the resource will not start)

Once the trusted websites are defined, selecting the “Get Shortcuts” link will send the admin to StoreFront, where each resource will contain a unique shortcut.  Those shortcuts can be added into the web site.

appshortcuts

But what if you want to email the link to users?

Those same links can be used, but because they are not on the trusted list of websites, users will receive a warning message they must acknowledge.

untrusted

This prompt can be disabled by going to “Advanced Settings” and deselecting “Prompt for untrusted shortcuts”.  (Note: A URL must still be added to the list of websites or else the resource will not launch.  Any URL can be used).

trustconfigAdditional options:

  1. Pass through authentication: If users must use their domain credentials to launch the resource, it might be worthwhile to setup pass through authentication so the users are not subjected to authentication challenges.
  2. Unauthenticated users: If the application incorporates its own authentication, it might be worthwhile to enable unauthenticated user access to the resource.

Daniel (Follow on Twitter @djfeller)
Citrix XenApp and XenDesktop 7.6 LTSR Handbook
XenApp Best Practices
XenApp Videos