Support  |  News & Events  |  Blog  |  About  |  Help  

Tag Archives: Licensing

A New Citrix Trade-Up Program

August 27, 2014 4:10 pm ⋅ Leave a Comment ⋅

At the recent Citrix Synergy conference, Citrix announced a new product bundle: the Citrix Workspace Suite, which consists of XenDesktop Platinum Edition plus XenMobile Enterprise Edition. The Workspace Suite is only licensed in a per-user model. Also, as we mentioned in an update to our blog post on Citrix Subscription Advantage, it appears that, with the advent of the Workspace Suite, Citrix is continuing to move to a more traditional model of “Software Maintenance,” that covers both product upgrades and 24×7 telephone support. Subscription Advantage by itself is not available for the Workspace Suite.

Purchasing the Workspace Suite does offer a bit of savings compared to purchasing the two products separately. A Workspace Suite license is $450 (MSRP) plus $99 for the required first year of Software Maintenance, for a total acquisition cost of $549. XenDesktop Platinum is $350 per named user, and XenMobile Enterprise is $226 per named user ($185 for the license plus $41 for the required first year of Software Maintenance), so buying the two products separately would cost you $27 more than buying the Workspace Suite.

Now, Citrix has announced a trade-up promotion for existing customers who would like to move to the new Workspace Suite. The cool thing about this promotion is that it is so widely applicable. If you own any version of XenDesktop, XenApp, or XenMobile, or if you own ShareFile Enterprise licenses, you can take advantage of this trade-up. If you own XenDesktop concurrent-use licenses or XenApp licenses (which have always been concurrent), you can get two Workspace Suite licenses for each license you trade up; otherwise it’s a 1 for 1 trade-up.

The trade-up price varies depending on what product you’re trading up from, what edition of that product you own, and whether you’re current on your Subscription Advantage. For example, the XenApp trade-up pricing looks like this:

Advanced Edition Enterprise Edition Platinum Edition
SA Current $373 $323 $298
SA Not Current $423 $373 $348

Note: All prices shown are MSRP and do not include any volume license program discounts.

Citrix is also offering a 10% discount on additional Workspace Suite licenses purchased on the same order as a trade-up, or a 35% discount if you purchase enough additional licenses to cover everyone in your organization.

You can find a handy trade-up calculator at www.citrixinformation.com/cwscalculator that will let you enter your existing license information and tell you what your trade-up will cost.

Posted in: Citrix, Licensing ⋅ Tagged: , , ,

The Elusive Windows “Companion Subscription License” - a Solution In Search of a Problem

July 25, 2014 12:10 pm ⋅ 1 Comment ⋅

In our post entitled “What Licenses Do I Need,” we discussed the licensing required, from both Citrix and Microsoft, for a XenApp or XenDesktop deployment. But there was still an unknown factor: When that post was published, Microsoft had recently announced something that, at the time, was being referred to as a “Companion Device License” – but no information was available yet on what it would cost or how it would be licensed.

The fog has finally cleared, and, unfortunately, it’s not particularly good news if you are a Small or Medium Enterprise.

The question at hand is what Microsoft licenses are required to legally operate a Virtual Desktop Infrastructure that serves up virtual instances of Windows 7 or Windows 8.x to your users. And the answer is that it depends on what the client device is that will be used to access the virtual desktop. If the client device is a Windows PC covered by Software Assurance, no problem – the right to access a virtual desktop instance is one of the benefits of Software Assurance. But if the client device is a Windows PC that is not covered by Software Assurance, or if it is not a Windows PC at all (e.g., Mac, Linux, thin client, etc.) then you must purchase a Virtual Desktop Access (“VDA”) license for that client device. That VDA license is available through Open Value Subscription licensing for roughly $100/year each.

So far, so good. But things start to get more complicated if you want to access that virtual desktop from a personally-owned client device.

According to the Microsoft Product Use Rights document (on pages 74 & 75 of the April, 2014, edition, in case you want to read along), the primary user of a Windows PC covered by Software Assurance, or of another client device to which a VDA license has been assigned, has “roaming use rights” that allow a virtual desktop to be accessed from a “Qualifying Third Party Device” such as a personal PC, MacBook, iPad, etc…”from anywhere off your or your affiliates’ premises.” And therein lies the problem: The user is not entitled to bring a personal device into the office and use it there to access a virtual desktop.

So, if your objective is to enable BYOD and let your people bring in whatever kind of device they want to use, and then use that device to access your virtual desktop infrastructure, what do you have to do? This question is what Microsoft attempted to address with what is now called a “Windows Companion Subscription License.” But it doesn’t address it very well. First of all, the Companion SL must be associated with another client device that is…yep, either a Windows PC with Software Assurance or some other client device that you’ve assigned a VDA license to. For every one of those you have, you can purchase a Companion SL, which will entitle the primary user of that device to access a virtual desktop from up to four Companion Devices in any given 90 day period. Therefore, the Companion SL doesn’t truly enable BYOD in the sense of eliminating the need to purchase company-owned client devices that are covered by either Software Assurance or a VDA license – because you have to have one of those before you can even purchase a Companion SL.

To make matters worse, unless your organization is large enough to have a Microsoft Enterprise, Select, or Select Plus agreement, you’re out of luck, because the Companion SL is not available through any Open License program. So, if you’re an SMB, your only option for legally licensing employee-owned devices for use on your premises to access your virtual desktop infrastructure is to purchase VDA licenses for those employee-owned devices.

If you do have an Enterprise or Select agreement, you can expect to pay an estimated $48 - $84 per year for a Companion SL, depending on your agreement, the size of your organization, and the concessions you’ve been able to wrangle out of your Microsoft account rep. So that may offer some cost savings for large enterprises that want to institute a BYOD policy – although it’s not clear to me how great the savings would be considering that you have to have a client device with either Software Assurance or a VDA license before you can even purchase the Companion SL.

For most organizations, in our opinion, the Companion SL is a solution in search of a problem.

Posted in: Licensing, Microsoft, VDI, XenDesktop ⋅ Tagged: , , , ,

Citrix Subscription Advantage

June 26, 2014 9:00 am ⋅ 3 Comments ⋅

Update 6/26/2014:
There was an interesting announcement at the recent Citrix Synergy conference that may indicate the future direction of Subscription Advantage. At that conference, Citrix announced a new product bundle called the “Citrix Workspace Suite,” which consists of XenDesktop Platinum Edition + XenMobile Enterprise Edition. It does not appear that Subscription Advantage, as we have known it for lo these many years, exists for this product. Instead, Citrix appears to have moved to a more traditional (in the software industry) Software Maintenance model that includes product upgrades and 7 x 24 telephone support.

The list price for the Workspace Suite is $450 per named user (there is no concurrent-use license model for this product), plus $99/user/year for Software Maintenance. Software Maintenance is mandatory for the first year (so the first year cost is actually $549/user, not $450…less whatever discount you can get on the license itself) and optional for subsequent years. But it appears that if you choose not to renew Software Maintenance, you will also lose your access to product upgrades, just as has been the case with Software Assurance.

***** End Update *****

I’ve noticed a pattern developing: It starts with a renewal notice, usually around 90-days before Subscription Advantage (SA) is set to expire. The reply email comes back within 48 hours: “What is Subscription Advantage?” I answer and then comes question #2: “Why do I need it?” So I think it’s time once again to shed some light on this mystical annual renewal.

Subscription Advantage IS NOT MAINTENANCE!

Subscription Advantage  IS NOT SUPPORT!

Subscription Advantage IS NOT A WARRANTY!

Ok, now that that is out of the way we can focus on what SA is because it is important that you know exactly what you are paying for. Citrix SA is annual license upgrade protection. The first year is included with your license purchase - after that, there’s an annual renewal cost. What does that mean? Well it means that you bought something that is not a set-it-and-forget-it item. Data centers grow and change all time and the tools used in that data center need to change as well. So as the Citrix products evolve (or change names) you as an owner of “upgrade protection” can take advantage of these upgrades, period.

(There is one exception: it is now possible to purchase a bundle of SA and Citrix telephone support for XenApp. We covered this in an earlier blog post.)

The good news is that Citrix SA doesn’t cost as much as traditional “Software Maintenance” from companies that bundle some kind of telephone support with their upgrade protection. The general rule of SA is that it costs about 11% - 13% per year of the cost of the license. In our experience, traditional Software Maintenance that includes support will typically run you 18% - 20% per year for 5 x 8 support, and 25%+ per year for 7 x 24 support.

However, if you have not renewed your SA and wish to upgrade you will need to pay a reinstatement fee or just buy new licenses. Which option is best for you will depend on how long it’s been since you renewed SA. If your SA has been expired for more than a year, it’s going to be pretty expensive to try to get it reinstated.

Citrix upgrades its products often! So what if I have my own Citrix expert on staff and don’t plan on upgrading for 5-6 years anyway? Well, as we all know, life is what happens while you’re making other plans. What about the rest of your data center? Do you not plan to upgrade that in the next 5-6 years either? In many cases old versions of Citrix products will not be compatible with new technology releases. E.g., Citrix just released XenApp 6, which is specifically designed for Windows Server 2008 R2. Earlier versions of XenApp are not compatible with 2008 R2.

Also, Citrix frequently releases “Feature Packs” for older product versions that add functionality (within the technological constraints of the older platform). If your SA is current, you can take advantage of the new features. If not, you…can’t.

Finally, no software company can afford to indefinitely support every product version that they’ve ever released. Everything has a lifecycle. For example, Presentation Server v4.0 hit the “End of Life” point at the end of 2009. That means there is no support available for the product other than the information you may be able to dig out of the Citrix on-line Knowledge Base. Furthermore, all the downloads have been removed, so you have no way to access any security patches, service packs, hotfixes, etc. This is obviously not a good situation for your production environment - so if you’re still running Presentation Server v4.0, you should be working toward upgrading your environment as soon as you possibly can.

Bottom Line: I recommend SA renewal to everyone who buys Citrix licenses. As the person who handles all the renewal notices for our customers, I have, time and time again, seen people try to save a dollar this year but end up spending more then necessary next year. Plus it is just a headache to realize that you need to upgrade - perhaps to solve a problem that (naturally) surfaced after hours or on a weekend - but can’t get the upgrade because your subscription has expired. So, when you get that email notice from me, just remember: I’m really trying to make your life easier by insuring that you’re upgrade rights are protected!

Posted in: Citrix, General, Licensing ⋅ Tagged: , ,

Licensing Office in a Remote Desktop Environment - Updated

April 30, 2014 5:00 pm ⋅ 8 Comments ⋅

Judging from the questions we continue to be asked, lots of people are confused about how to license the Microsoft Office Suite if you are accessing it via Microsoft’s Remote Desktop Services (a.k.a. Terminal Services) and/or Citrix XenApp. Hopefully, this will help clear up the confusion. We’ve also updated this post to include information about how to license the applications in a Cloud hosting environment.

First of all, it is important to keep in mind that desktop applications such as the Office Suite are licensed per device, not per user. According to the latest Microsoft “Product Use Rights” document dated April, 2014, a “Licensed Device” is “the single physical hardware system to which a license is assigned.”

That begs the question of what “assigned” means, and the answer - particularly for devices like thin clients, where you couldn’t install the application locally if you wanted to - is that you are on the honor system. You decide, in the privacy of your own conscience, which licenses you are assigning to which devices - with the caveat that, if you’re ever audited, you’d better be able to produce a license for every device people are using to run Office apps. You can reassign a license from one device to another, but not more often than every 90 days, unless it’s due to permanent hardware failure.

Once you’ve assigned each license you acquire to a device, you have the following rights (again quoting from the Product Use Rights document, with my commentary in italics):

  • You may install the software on the Licensed Device and a network Server.
  • Unless you license the software as an Enterprise Product or on a company-wide basis, you may also install the software on a single portable device. That would cover a user who, for example, had both a desktop PC and a notebook PC.
  • Each license permits only one user to access and use the software at a time. So, technically, it would be a license violation for someone else to run Office on your desktop PC while you’re in a hotel somewhere running it on your “portable device.”
  • Local use of the software running on the Licensed Device is permitted for any user. So it’s OK to let someone else use your desktop PC to run Office, as long as you’re not simultaneously running it on your “portable device.”
  • Local use of the software running on a portable device is permitted for the primary user of the Licensed Device. So, technically, it would be a license violation for you to let someone else run Office on your “portable device” under any circumstances.
  • Remote use of the software running on the Licensed Device is permitted for the primary user of that device from any device or for any other user from another Licensed Device. So if your Licensed Device is your desktop PC, it’s OK for you to use GoToMyPC or some similar remote access method to access and run that copy of Office, using whatever kind of client device you want - including, say, an iPad. However, any other user could not remotely access your desktop PC to run that copy of Office unless they were doing so from another Licensed Device.
  • And now the most important point relative to the subject at hand… Remote use of the software running on a network Server is permitted for any user from a Licensed Device. A Remote Desktop Server falls under the definition of a “network Server.” So any user who is accessing Office via Remote Desktop Services must be doing so from a Licensed Device.

In other words, if you can walk up to a device and use it to access a Remote Desktop Server and run Office, you must have an Office license for that device. It doesn’t matter whether that device is a PC or laptop that has the Office bits installed on its local hard drive, or whether it is a thin client device that only knows how to connect to a XenApp server, you need to have “assigned” a license to that device.

It’s also important to note that all of the above came from the Product Use Rights document for Microsoft Volume Licenses. You do not, never have had, and probably never will have the right to access Office on an RDS or XenApp server from a device that has an OEM Office license installed on it. If your PC or laptop came from the manufacturer with Office pre-installed on it, then you have an OEM license, and you do not have “network storage and use” rights. There is an excellent blog post over on the Microsoft SMB Community Blog that explains this in detail. Yes, it’s an old post (from July, 2005). No, the policy hasn’t changed.

Things get a bit more complicated when you move to the Cloud. For example, if you are a VQOffice® customer, and you want to run Office apps on our cloud servers, we can, of course, bundle the Office licenses into your monthly fee under our Microsoft SPLA (“Service Provider License Agreement”). But what if you already own volume licenses for Office? According to the Product Use Rights document, we can use your licenses “provided all such Servers and other devices are and remain fully dedicated to your use.” Given the highly virtualized environments of nearly all Cloud hosting providers (including us), that’s going to drive the cost of the solution up significantly unless you have enough users to justify dedicating hardware in our data center just for your use. For most small businesses, it will be less expensive to pay us for the use of our SPLA licenses than to pay us for dedicated hardware so you can use your own licenses.

What about Office 365? Office 365 is governed by a completely different use rights document - the Online Services Use Rights document. If you read through that document, you will find that, under the E3 plan for example, each user has the rights to activate the Office software on up to five devices, which is a pretty good deal. You will also find the following statement: “Each user may also use one of the five activations on a network server with the Remote Desktop Services (RDS) role enabled…” At first blush, you might think that means you could use your Office 365 E3 licenses to cover running Office apps in our Cloud hosting environment - and you would be right, provided that you’re running on dedicated hardware. So, basically, the same rules apply to Office 365 licenses as apply to volume licenses. We’d be delighted if the rest of the world added their voices to ours to try to get that policy changed.

Disclaimer: I do not work for Microsoft, nor do I define their license terms, which are subject to change, particularly when new product versions are released. I have, however, worked with them for a very long time, and had lots of discussions about what is, or is not, legal under the terms of various license models. The foregoing is my own interpretation of information that is publicly available on the Microsoft Web site - and I have helpfully provided you with links to that information. I highly recommend that, if you have any questions, you download the relevant Product Use Rights document and read it for yourself.

Posted in: Citrix, Licensing, Microsoft, XenApp ⋅ Tagged: , , , ,

What Licenses Do I Need….

May 16, 2012 1:41 pm ⋅ 56 Comments ⋅

Earlier this week, I had a long discussion with a client (you know who you are) about what licenses they would need for a deployment of “zero client” devices. We’ve written a lot about Microsoft and Citrix licensing, about XenDesktop and XenApp, about the Citrix trade-up, etc., but it occurred to me that it might be beneficial to pull all the licensing information together into one post instead of expecting you, gentle reader, to have to sort through multiple posts to pull it all together.

So, let’s discuss Citrix licensing first, then move on to the Microsoft licensing.

First of all, if all you want to do is to deploy VDI (Virtual Desktop Infrastructure), and you have a limited number of users, then you should probably purchase VDI-in-a-Box.

If you decide that VDI-in-a-Box is not the right fit foryou, the next question you need to answer is whether to use XenApp licenses or XenDesktop licenses. Beginning with the introduction of XenDesktop v4.0, Citrix concluded, reasonably enough, that an organization that was deploying VDI probably wouldn’t get much leverage from a concurrent-use licensing model, because their concurrency ratio (by which I mean the ratio of total users to concurrent users) would be pretty close to 1:1. So XenDesktop v4.0 was introduced with a per-named-user or per-device license model. These licenses were roughly half the cost of the comparable XenApp concurrent-use license: XenApp Enterprise Edition, for example, carries an MSRP of $450 per concurrent user. XenDesktop Enterprise Edition carries an MSRP of $225 per user/device.

At the same time, Citrix made the decision to include XenApp rights in the XenDesktop license. So if you buy XenApp, you get only XenApp. But if you buy XenDesktop, you get both XenDesktop and XenApp - so you can use XenApp to stream applications to your virtual desktops, or have your virtual desktops function as client devices that run published applications that execute on the XenApp servers, or simply deploy a mixture of XenDesktop and XenApp to your user community depending on what delivery method is best for a particular use case. This is what Citrix refers to as the “FlexCast” delivery model.

This created the interesting situation where, because of the difference in license cost, if your concurrency ratio was less than 2:1, you were better off financially to purchase XenDesktop licenses even if all you really wanted to run was XenApp. And, since delivering what Citrix calls “hosted shared” desktops from XenApp servers makes more efficient use of the underlying hardware and storage infrastructure, the bias should probably be toward XenApp unless there is a clear use case for why users need to connect to individual desktop OS instances rather than a shared XenApp desktop (and it isn’t just appearance, because with XenApp v6.5 on Windows Server 2008 R2 we can deliver a XenApp desktop that looks and feels like a Windows 7 desktop). But, for the sake of this discussion, let’s move on down the XenDesktop trail.

Citrix has re-introduced a concurrent-use license option for XenDesktop, which is a better choice for organizations who want to deploy both XenDesktop and XenApp, but have a concurrency ratio greater than 2:1, but so far, I haven’t seen very many use cases where that license model made sense.

If you already have XenApp licenses, and want the ability to deliver VDI as well, you can take advantage of the Citrix trade-up program to transform your XenApp licenses into XenDesktop licenses. And if you trade up all of your XenApp licenses, you can get two XenDesktop user/device licenses for each XenApp license. So 250 XenApp licenses would become 500 XenDesktop user/device licenses. If you want more information on how the trade-up program works, and what your trade-up options are, check out the handy Citrix Trade-Up Calculator.

As of the release of XenDesktop v5.0 Feature Release 1, the license service got pretty smart in terms of how it managed those user/device licenses. This is good news for, say, a hospital, which may have devices that are used by multiple users and other users who use multiple devices. The license server can intelligently and dynamically reassign licenses between users and devices to make the most efficient use of the available licenses. For example, consider the following scenario for a brand-new environment where no licenses have yet been assigned:

  • User 1 logs on from client Device 1. The license server will, by default, check out a license to User 1.
  • User 1 logs off, and User 2 logs on from the same client device. The license server, now sensing that two different users have logged on from the same device, will take the license that was assigned to User 1, and reassign it to Device 1. Any subsequent users who log in from Device 1 will not cause any action by the license server, because Device 1 is already licensed.
  • If User 1 logs on again from a different client device, the license server will again check out a license to User 1 (so, at this point, two licenses are checked out: one to Device 1 and one to User 1). Since User 1 has logged on from two different devices, the license will remain assigned to User 1 unless/until manually released by an administrator (e.g., in the case of the employee leaving the organization), or unless User 1 doesn’t log on for a period of 90 days, in which case it will be automatically released due to inactivity.
  • Likewise, since two different users have logged on from Device 1, that license will remain assigned to that device unless manually released or automatically released due to 90 days of inactivity.

So…how do you know how many licenses you really need? There is actually a formula that will tell you that. You need to know how many total users you have (let’s call that number “A”), how many shared devices you have (let’s call that “B”), and how many of your users will use only shared devices (let’s call that “C”). The formula is A - C + B. So, if you have 1,000 total users, 300 shared devices, and 600 of your users will use only shared devices, you need 1,000 - 600 + 300 = 700 total licenses.

For more information on exactly how this works, see the Citrix Community Blog post by Christophe Catesson, which in turn links to a recorded session from Synergy 2011 that was a deep dive discussion of XenDesktop licensing.

Now for the Microsoft licensing component.

If you have users who will be executing applications on a XenApp server, you will need a Remote Desktop Services (RDS) CAL for that user, or for the client device that user is using. It is very difficult to manage a mixture of user CALs and device CALs in a Remote Desktop Services environment, so, in most cases, you’re going to be better off purchasing user CALs.

If you have users who will be attaching to a virtual desktop instance, the licensing requirements are different, depending on the client device. If the client device is a Windows PC whose Operation System is covered by Software Assurance, you do not have to purchase any additional Microsoft license to use that PC to connect to a virtual desktop. If the client device is not a Windows PC, or that copy of Windows is not covered by Software Assurance, you need a Virtual Desktop Access (VDA) license for that client device. VDA licenses are only available under the Open Value Subscription license model at present, meaning that you will continue to pay for them every year. Forever.

But wait! That’s not all! As Gabe Knuth outlines in a recent article on Techtarget.com, there is a very strange loophole in the VDA license terms. If you have a VDA license for your primary device (or if it’s covered by Software Assurance), you have what Microsoft calls “Extended Roaming Rights,” which allow you to also use your home computer to access your virtual desktop, or use your iPad when you’re at home or traveling. But, technically, it does not entitle you to bring your iPad into the office and use it there! To solve that (using the term “solve” loosely), Microsoft recently announced something called a “Companion Device License” (CDL) which allows you to use up to four other devices (in addition to the primary licensed device) to access your virtual desktop. No word yet on what the CDL will cost.

So let’s see if we can summarize what our client would need for a deployment of “zero client” devices (like, for example, the Wyse Xenith thin client).

  • You’re going to need some kind of Citrix license, either VDI-in-a-Box, XenDesktop, or XenApp.
  • Since the thin client is not a Windows PC, and therefore cannot be covered by Software Assurance, you would need to purchase a Microsoft VDA license for it.
  • If the thin client will be used only to attach to a virtual PC desktop and execute applications within that desktop OS environment, no additional Microsoft license is needed. However, if the thin client will also be used to attach to applications that are executing on a XenApp server - either directly or indirectly by having the Citrix client baked into the virtual PC desktop - you will also need a Microsoft RDS CAL.
  • You do not need an RDS CAL if you are only using XenApp to stream packaged applications to a virtual (or physical, for that matter) desktop for execution there. Since you are not actually utilizing Remote Desktop Services by executing code remotely on a Remote Desktop Server, no RDS CAL is required.
  • If you want to institute a BYOD program, where users can bring whatever client device they wish into the office and use it to access your VDI, you’ll probably need some of the new Microsoft CDL licenses.

If I’ve overlooked anything, feel free to submit questions via comments on this post, and we’ll try to get them answered. Let the discussion begin!

Posted in: Application streaming, Application Virtualization, Citrix, Licensing, Microsoft, Remote Access, VDI, Virtualization, XenApp, XenDesktop ⋅ Tagged: , , , , , , , , ,