Link to home
Start Free TrialLog in
Avatar of janhoedt

asked on

VMWare view: why use it? ... and why not Xendesktop?


I have a VMWare Vsphere environment lab (3 ESX servers) and am curious about VMWare view. I know more or less what it does.

Just in short: why would I use it, who uses it and the ones who are using it are they happy :-) (why not use Xendesktop which looks more sophisticated)? Never used View nor I played with Xendesktop, therefore this question.

Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I can speak from the View side. Some of the pluses I've seen with View is how efficiently it uses resources by using Linked Clone pools. If you have your pool setting set to refresh upon logoff then it will recreate the vm based on the replica image. This in turn returns the vm to it's original state.

Some of the challenges that I've encountered have been Thinapp and profile management. You have several options to help combat this problem.

As for for the the question of why would you use it, simply put because of potential cost savings. I can use a 21 inch monitor and zero client solution for around $600. The idea is that in addition to the savings compared to a desktop that you will not have to replace this hardware as often as a desktop. Using this thinking along with efficiently sizing your pools and vm's, you will be able to keep storage and server costs as low as possible. Also, think of potential power savings, and lowering your desktop support tickets as well.
Avatar of janhoedt


Wow, what a document/review! Thx!
1 more thing: what s the difference between publishing  a desktop in XenApp and XenDesktop? I guess enduserexperience is the same but backend is different?
thin client session = xenApp

virtual machine = xendesktop
Right, got it. But 1 vm takes at least 4gb (win 7, less for only running os but still some GB) whereas an session  takes almost. What a waste of memory, CPU!
our Windows 7 VMs are 2GB, 2vCPU.

But we can also get 75 concurrent users thin client on a Dual Quad Core Processor , 4GB RAM, because of memory sharing.

User Experience can be better with a full VM.
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks, I still have to read the docs but have some remarks.
I DID already work with XenDesktop! Just didn't know it was ... Xendesktop.

Was ok, but don't really see advantages above an RDP session aside from a better multimedia experience.

Setup looks piece of cake, where I used it, it was integrated in XenApp website. Can you set it up without XenApp?

Now I'm curious how VMWare View "behaves" versus XenDesktop ....
Yes, you can setup with XenApp.

You've spotted why it's better than an RDP session, "better multimedia experience.".

Also some software requires a phsyical/virtual PC to run on, and not a session.
Ok, I was able to make it work (XenDesktop), however, my RDP session is -a lot- faster.
Could be due to fact that I'm running the XenDesktop on virtual machine with only 2GB memory ... however, isn't it just a "passing" of my session to the machine (not used after connection)?

VMWare view I won't "bather" since the principle behind is the same and I already have XenApp so don't see the use of  testing/using View.
VMware View does uses RDP or PCoIP (different and better protocol).

It depends on how you've been testing.
Ok, but you need an extra plugin for View, whereas most companies have already a Citrix client installed these days.
Thanks for all the updates, I'll close this call now!
1 more thing,  (how) can I publish a XenDesktop within a site of XenApp?
different and new question.

You would only have the Citrix Client, if you were a Citrix site!
Right, this question can be closed.