Citrix announces details of XenApp Feature Pack 2, available Sept 29.

Since I first wrote this, I learned none of the "core" XenApp features are for Server 2008. The core XenApp updates are for 2003 only.

[UPDATE: Since I first wrote this, I learned none of the "core" XenApp features are for Server 2008. The core XenApp updates are for 2003 only.]

Yesterday Citrix announced details of the next release of XenApp which will be called “XenApp Feature Pack 2.” (This is the XenApp release that was codenamed “Cache.”) Unlike the first Feature Pack for XenApp 5 which was essentially just changes in which features where bundled into which editions of the product, Feature Pack 2 has a lot of new features. (Citrix claims over fifty.) Some are pretty significant new capabilities, while others are just refinements to stuff that’s been around for years.

In this article, I’ll take a quick look at the new features, starting with the two most important ones: VM-hosted apps and power & capacity management.

VM-hosted apps

VM-hosted apps is the capability to publish seamless remote ICA applications from single user desktop OSes instead of a multi-user Terminal Server. You could almost think of it like “XenApp for desktops” instead of “XenApp for Terminal Server.” (The name is a bit misleading because the apps don’t have to be published from a workstation running in a VM. A blade would work too.)

This solves a scenario where you have an app that you’d like to deliver seamlessly via a remote display protocol, but for whatever reason you can’t install it on a terminal server. Maybe the app is really intense and you need to run one instance for each user on a blade? Maybe it’s just not terminal server compatible? Maybe you want the “per user” mobility of being able to live migrate a “session” (since there’s only one session on a server).

The only real downside to VM-hosted apps is that since you’re connecting to a Windows desktop OS instead of a Terminal Server session, you’ll need a VECD license on top of your TS CAL. Now what’s really messed up about this is that if you decided to build this exact same thing with terminal server (with each terminal server only hosting a single session), you wouldn’t need VECD at all (and you’d have the same thing, except on terminal server instead of Windows XP). So there’s just another example of how stupid VECD is. (Combine that with the power & capacity management feature from the next section and you’ve got a VECDless VDI environment!)

It’s nice that Citrix added this feature though. It’s been in Quest’s vWorkspace product for years, and I always wondered why Citrix never added it. (Again, since you could basically do it anyway with TS, why not just make it official and let users create their own “single user TS” farms.)

By the way, we discussed this whole VM-hosted app feature on a few months ago. Check out that conversation for more thoughts about this concept and feature.

Power and Capacity Management (Server 2003 only. Too bad if you're on 2008!)

Power and capacity management seems to be the feature that people are most excited about. In a nutshell, this capability changes how XenApp’s load balancer works. The current version of XenApp will always try to evenly spread the user load across all your servers. So if you have 50 servers and 50 users, you’ll get one user per server. Of course now all of the sudden people care about power consumption, and they think, “Hey, I could easily fit these 50 users on a single server and power off the other 49 servers.”

Sounds great! Except making this change requires a complete change in how Citrix’s load balancing engine works. Rather then rewrite the load balancer, Citrix created some new components to sort of “game” the system. To use power & capacity management (PCM), you configure a control server and then put agents on all your XenApp servers. Then you configure all sorts of groups and rules and thresholds and hardware profiles and stuff. It works pretty much as you’d expect: You can specify the minimum number of servers you want on at any given time, how many users you want on the powered on servers before the system starts powering on additional systems, etc.

PCM can work with physical and virtual servers. (The tech preview only worked with XenServer-based VMs. I haven’t touched the release code yet so I don’t know whether ESX or Hyper-V support made it in or not.)

PCM also works in reverse, to power down servers as they’re not needed. Unfortunately there’s still no way to “live migrate” a single session from one XenApp server to another (where’s LufLogix?), so all PCM can do is put a server in “drain mode” which is a fancy way of saying it disables logons to hopefully slowly get everyone off the server so it can be shut down. (Okay, technically it doesn’t disable logons—it just gooses the server’s load index to prevent new sessions from being routed there.)

I think this PCM capability has a lot of potential for Citrix. For example, one could imagine that in the future, PCM would not only understand the hardware capabilities of a XenApp server, but also which XenApp server VMs were on which physical hosts. Then when there is excess capacity in the whole system, it wouldn’t have to completely drain a whole server to power it off. It could just live migrate and consolidate those running VMs onto fewer physical hosts. In other words, maybe the “normal” operating load is six XenApp VMs with 100 users each (600 users per physical server). Towards the end of the day, you might only have an average of 5 users per VM, (30 users per physical server), across maybe 20 servers. So PCM could live migrate the XenApp VMs so that you had maybe 20 per physical host instead of 5.(Since each one only has 5 users instead of the normal 100.) Then it could power off 14 of the 20 physical hosts.

Other new but less important features

As I said, there are quite a few smaller features and tweaks that are also part of this Feature Pack:

HDX Flash Redirection (Server 2003 only. Too bad if you're on 2008!)

This is something we demoed back in Brian Madden TV Episode 12 from Citrix Synergy in Las Vegas. The Flash remoting basically means that Flash content will be redirected from the remote host and seamlessly executed on the client. (It’s like multimedia redirection, except for Flash.) Citrix’s implementation seems pretty tight, with window scaling, client-host volume sync, support for windowless mode, and multi-tab browser support.

Hot add/remove for USB drives (Server 2003 only. Too bad if you're on 2008!)

Client USB drive mapping has been around forever, but now XenApp can handle this dynamically within a session. In other words, if you stick a USB drive in your client device while you’re in the middle of an ICA session, the drive will pop up in your remote session.

Windows 7 support

Feature Pack 2 supports Windows 7 across the board. You can use Windows 7 as your client (for both ICA sessions and for running streamed apps). You can profile apps on Windows 7. (“Profiling” is Citrix’s term for packaging apps for streaming.) Windows 7 is also supported as a host for VM-hosted apps.

App Streaming

[NOTE: This section has been updated since the original article was posted.]

Citrix XenApp Streaming gets revved to version 5.2 for Feature Pack 2. There are two main focus points with this release:

  • Performance: Launching apps (initially and from cache) is generally 20-30% faster across the board, in part to a new capability called "sandbox reuse" where additional virtualized apps can launch into existing sandboxes. (More here)
  • A more evolved isolation environment: Citrix is continuing to tweak the balance between "isolation" and "interoperation" of its sandboxes. More on the changes in 5.2 is here.

Profile Management

Profile Management in Feature Pack 2 will be version 2.1, up from the current 2.0.1. Citrix’s David Wagner is planning on blogging about the details in a few days, which I’ll link to here once it’s live.

Provisioning Server

Citrix Provisioning Services doesn’t have any major changes—just some refinements to fault tolerance. Provisioning Server will play a key role for delivering VM-hosted apps though.

Service Monitoring

Service Monitoring is now hypervisor aware. So it can figure out that “Hey, all these XenApp servers are experiencing the same problem, and they’re all VMs on the same physical host.”

Workflow Studio 2.0

Workflow Studio 2.0 got revved to 2.0. While there are new APIs, it still seems that you’ll need to do a lot of work to do anything useful with it. Workflow Studio’s PowerShell commandlets capability that everyone wants is still in Tech Preview mode though.

What’s missing?

Um, how about Windows Server 2008 support? (Seriously, this seems like kind of a big hole. Maybe not though? I guess most of the people I know are still on 2003 and will just go straight to 2008 R2. Gabe will investigate tomorrow.)

Also there’s no PowerShell support yet. (I’m talking general PowerShell for XenApp, not the Workflow Studio stuff.) That’s in tech preview now if you want to play with it.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

I just wondered if many other customers were disappointed to discover that HDX MediaStream for Flash is missing in XenApp5 FP2 for Windows Server 2008. Citrix skipped this (and one or two other FP2 features) for the Win2008r1 platform, but offer it for the Win2003 platform.  Seems odd that users on an older Win2003-based environment can enjoy the benefits of HDX M/S for Flash, but Win2008 users can't. True, a lot of people are on Win2003 and plan to leap to Win2008r2.  However, right now, if I had Win2008r2, Citrix don't have a version of XenApp available that I can use.  The latest is XenApp5 for Win2008r1 - which is what I have.  However I am going to miss out on HDX M/S for Flash, whereas the older Win2003 platform can have it.  


At each version, for every product of every company, this is the same debate regarding "how useful/not useful this feature will be for me"...

What will be the key missing feature in XenApp you will ike to get for next version ? Brian gave a clear view of "201X VDI requirement"... but for App Virtualization...


I see what you're saying Kata, but I was just stating a fact from my perspective, while asking if any other customers were disappointed that HDX MediaStream for Flash is missing in XenApp5 FP2 for Windows Server 2008.


Get your point... Not disapointed because I'm W2K3/32 and plan to move directly to W2K3R2/64... Main challenge now is application migration from x32 to x64... More happy by the storage Plug n Play feature I was waiting for a long time.

the feature I will found technically great but will probably not play with it is live session motion between XenApp servers... there is much better other way to get to HA (look Citrix blog entry on XA5FP2 on PCM).

I will really appreciate "application publication template" where you can specifiy that all applicaiotn in this group have the foolowing settings (video, audio, security, published to...) and when simply by moving app from a group or another, you dynamically change the settings... If you were able to move the app from farm to farm (based on the isolation and streaming feature), it will ease my pre-production to production move and my migration path...



Someone told me that Citrix told them that this feature:

"PCM also works in reverse, to power down servers as they’re not needed."

will not be available until a later release.  Can you confirm?


I've updated the article based on the clarifications in these comments and more info from Citrix. Thanks for pointing all this out.

Gabe will do a piece tomorrow about the versions and Citrix does / doesn't support. Citrix's current view is that most customers are on 2003 and will jump directly to 2008 R2, so they want to focus resources accordingly. Does that sound right? (It does to me, actually, I'm just curious about others.)


I agree with the 2003 -> R2 comment.  When Harry asked what features we'd like to see in 2008, I responded "none".  Citrix needs to focus on R2 not 2008 at this point. In addition the Parra release must support mixed OSes of 2003 and R2.  And I don't mean in the traditional sense where Citrix says, "Yes, but we don't recommend interoperability mode for long periods on times.  Just for migrating"

Second, VM-Hosted apps isn't much of a feature at the moment.  It will only support 1 app per VM.  So publishing that Suite (Adobe CS4) is out of reach.  This is  technical issue that Ctx is working through due to a lack of foresight on Citrix's part.


For those of you still running Server 2003, are you planning to purchase Extended Support agreements from MS in 10 months?  Or will you "wing it" and hope you won't need to obtain any non-security hotfixes?  I'm curious because we're facing this situation, but upgrading to Server 2008 is obviously going to mean less XenApp features.  Surely Citrix realizes that not all organizations can afford MS Extended Support?


Citrix + Microsoft = prolonging Redmond's dominance and lack of real progress.


I'm sure glad to know that those thousands of dollars we've spent the past couple years on SA renewals are really paying off!! /sarcasm


It is obvious at this point that Citrix is focusing on Windows 2008 R2. If you haven't already upgraded to Windows 2008 for Terminal Services it doesn't make sense to upgrade now. Stay on 2003 until Citrix releases a 2008 R2 version of XenApp.


We have clients who moved to W2008 R1 and are now disappointed that they can not use HDX technology until W2008 R2.

Any chance that they can add HDX to R1?


We're havin' some customers that is disappointet and somewhat confused for what to do. Will there be any further updates for XenApp 5.0 on Windows Server 2008 or will Citrix "skip" this release and only focus on Windows Server 2008 R2 and Parra? Anyone who knows?


I agree skip 2008 R1, and plan for R2. The key questions here is your app compat confidence on x64. If there is not confidence on x64 I'd suggest to MS they release an R2 for 2008 32 bit. Unless they do that, it's a very clear single what MS wants the world to do, move to x64. Is this another Vista on their hands? Perhaps, but I actually have many apps on x64 and they run just fine. Perhaps x32 becomes the exception. I agree with Joe Shonk, true mixed Farm support will be required for a while. Blame MS.


I'm a product manager on XenApp and want to first thank everyone for your comments and feedbacks about XenApp 5 Feature Pack 2.

In response to your comments here about WS08, I think Vinny Sosa's feedback on his "What's new in XenApp 5 Feature Pack 2 in plain English" summed it up pretty well the other day when he said "we've heard this concern from a number of customers who have already made the move to XenApp 5 on Windows Server 2008. I can tell you we are NOT overlooking our WS08-based customers and that additional updates for those of you on WS08 are in the works. Since we released XenApp 5 last September 2008, we've released two feature packs with a ton of value in them for our customers on SA. In this particular release, VM hosted apps, load testing, provisioning services, and voice service improvements apply to both Windows Server 2003 and 2008 environments. Although we'd love to have everything roll out at once, the fact is that WS03 and WS08 are different development platforms for us and ended up having different time to market constraints. We do apologize that your organization and other WS08 adopters will have to wait a little longer for selected new features to reach you. In the meantime, the WS08 R2 platform is making its way to the market and we invite you to pre-register for our XenApp tech preview for R2 slated for later this year. We need and want feedback from customers like you on your platform adoption plans and the hurdles you face. There will be some major improvements in XenApp for R2 that I know you are going to love. Hang tight."

I'd like to reiterate our apologies to WS2008 customers that they'll have to wait a bit longer but we are focused on quality and satisfying as many customers as possible in the shortest timeframe possible. In the meantime, you can pre-register for the tech preview on R2 at My team and I always appreciate your comments and feedback.