Citrix XenClient vs VMware View Client

Some time ago I posted a first look post on XenClient.  My overall impression was that it was an interesting technology but the hardware support was too limited.  I’ve continued to keep my eye on it from a distance because VDI is always promising but the expanded use case I keep running into are client that want to “checkout” desktops to allow offline use of the “VDI” session.  The primary reasoning is not to streamline desktop deployments but to allow a BYOD solution.  So, I thought I’d do a quick hit comparison of the two solutions based on the use case.

What do they do? 

From this use case both clients seem to do the same thing. They allow offline use of VDI sessions hosted on their respective backend solutions.  You can, in theory and sometimes even in practice “checkout” a desktop VDI session from you vSphere or XenServer environment.  The image runs as a VM within the respective client giving “offline” access to the corporate image on potentially resources not owned by the organization.

Both solutions allow the administrator to setup basically DRM to require periodic checkins to ensure the end user has continued rights to the corporate image and ensures that the image is up to date with the latest software and security patches maintained by the administrator.

How do they do it?

Now this is where the differences get exposed between the two solutions. Both clients are based on hypervisor technologies but leverage two different approaches to virtualization.  VMware View Client is based on VMware Player/Workstation technology.  This means that the View client is a Type 2 hypervisor which means that it would run under Windows (or Mac) and require the end user to have the view client installed on the OS that is factory installed.  This allows View to be installed on a wide range of desktops and laptops.  There’s not a modern Windows laptop or Desktop configuration that I can think that wouldn’t support a standard corporate installation of VMware View.

On the other side, XenClient is a Type 1 hypervisor.  This is also known as a “Bare Metal” hypervisor meaning that XenClient is standalone OS.  Type 1 hypervisors generally should perform better than Type 2 hypervisors.  This means in theory your corporate image should perform better under XenClient than View.  In practice, I don’t know how much truth if any there is in this statement.  If you are worried about performance then this approach to VDI more than likely isn’t for you.  One major drawback is that the machine needs to be re-imaged and have the consumer OS re-installed.  Another disadvantage is that there is a bit less driver support for XenClient.  One major requirement had been the requirement to have a certain video card platform.

So which is better?

It depends.  Did you really think I was going to make it that easy for you?  I doubt you would find that either solution will meet all of your requirements just around this use case.  If you are considering either client it’s because you have a larger VDI effort in play.  I can almost guarantee that other requirements would drive your decision just as much if not more than checking out a VDI session.  I’ve used some variation of both solutions.  XenClient is a cool technology but requires a lot of heavy lifting on the backend and a lot of disruptive installation for the client.  VMware View traditionally hasn’t had the large enterprise management tools Citrix is known to provide.

If you aren’t satisfied with this answer I’m more interested in why you want to use a VDI solution for BYOD.  I’d love to hear your argument for or against VDI for laptop BYOD strategies.

Published by Keith Townsend

Now I'm @CTOAdvisor

8 thoughts on “Citrix XenClient vs VMware View Client

  1. We are currently running xenclient together with vdi in the box which is in my opinion best of both worlds for our different type of users. Fully agree there is no right system. It all depends on your current hardware, licenses, information protection policies and expectations of your business. Bside that our number of issues decreased with more than 25%.

  2. Hi Keith,

    I’m currently assisting a Customer to check out this approach to BYOD and they are examining Mirage , MokaFive and XenClient – it will be interesting to see the outcome.

    Feel free to drop me a note to discuss more.

    Dave Caddick

  3. This is pretty wrong, the VMware View Client is not a hypervisor. Its software that used to remotely access a centralized virtual desktop across the LAN/WAN.
    You never run the desktop locally with the View Client. You used to be able to with ‘Local mode’ but no one used that feature. I assume you are talking about local mode, but you need to be specific since the View client is primarly and LAN/WAN client rather than a hypervisor

    1. Oleg, you realize this post is two years old? Local Mode was current as of the post and I had a customer who had local mode as a requirement.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: