Ervik.As has compiled a great list of resources for optimizing VDI desktops.
Here’s the link
Ervik.As has compiled a great list of resources for optimizing VDI desktops.
Here’s the link
I’m currently working on comparing the costs associated with doing 100 users in a shared desktop model. I was looking for resources around sizing storage and stumbled across these fantastic calculators by Andre Leibovici. He’s created one for both Xendesktop and VMWare view. Both leverage ESX as the hypervisor currently.
Here are the links:
The rate of change in the technology field is relentless. Constantly there are new solutions and products changing the status quo. This is especially true in the area of virtualization. We now have:
So where does this get us, apart from learning a bunch of new solutions that all seem more complicated than the way things were one before. The answer is simplicity, these technical solutions are all leading to one thing: abstraction. What this means is that they are removing dependencies in the stack from one another. Less dependencies, less complexity, more agility and freedom.
They’ve talked about this model in many capacities in different areas of virtualization; a common one is the layers of cake, or simply the layers model in VDI. Where the OS is decoupled from the applications and user profile. All the components come together to achieve the end result of a functional user workspace, yet none of the components are dependent on the others.
This facilitates simplified rollouts, migrations and upgrades. Admins no longer need to be concerned of adverse interactions with the upgrade of any one particular component, instead each component can be dealt with independently. This vastly simplifies change management and regression testing. It also enhances portability, users can bring their profile or applications to any OS with minimal headaches.
I have been doing research into Microsoft SCVMM 2012 and that was when I saw this model being taken and applied to server virtualization. Let me tell you- it was impressive. Microsoft has a product called Server App-V which like its MDOP counterpart, which virtualizes desktop applications, it allows for the virtualization of server workloads. Things like IIS, SQL Reporting Services or XenApp for example can be virtualized.
The ability to virtualize server workloads really starts to shine when you look at the rest of the capability of SCVMM 2012. SCVMM is moving towards the goal of providing resources regardless of location or hosting platform. Resources are no longer merely virtual machines, storage and networking but are tied together as services including the application layer. These services can be templated and basically act as a “recipe” for fully functional services such as a online purchasing system or XenApp host. This facilitates simplified user self service for deployment of services on demand. The fact that all the components of the “recipe” are virtualized and abstracted means extreme portability (think moving to the cloud!). Components can be upgraded independently and without concern of the other components. Think of how much this will simplify deployment.
Server App-V can take an application that has a 200 page installation guide and contain it so that every deployment is identical after the first succesful one. It can be ported from development to production and back again without ever changing. Any application changes and config is captured as “state”. Server App-V can monitor and port this state data so it can be migrated simply as well. Server App-V is a feature of SCVMM 2012. This means that all this can be automated in SCVMM’s console. It lets you visually define the components of a service and save it as a service template.
It is really exciting to think that one day incompatability type issues will no longer be a major headache. Everything will just work, as it is no longer some huge infrastructure stack with hooks running between all the layers, but rather a series of clean, known good, abstracted layers. Layers that can be moved between the datacenter and the cloud. The vision is starting to shine, and the clouds are starting to clear
How to video : Sequencing an application with Server App-V
Video: Server App-V TechEd Presentation
Quest has released a handy tool for quickly refining your virtual desktop images to dramatically improve on performance. This tool makes a number of tweaks that can save on disk, cpu and even RAM usage in a virtual desktop environment. The tool works for all vendors and it’s free! So check it out:
Here’s an excellent PDF outlining what licensing is required for what scenario in a VDI model.
VMWare has rolled out vSphere 5 and with it comes major licensing changes. It now is licensed per CPU for the entire cluster and with each CPU comes a vRAM entitlement. This means that customers will need to be much more careful in allocating memory as it will be a basis of licensing cost.
read more in this link:
With VDI established as a real approach to desktop delivery and management now more than ever, I think it’s important to ask “Why VDI?”. If we don’t ask why, then projects to design and implement VDI will never succeed. Without an objective or goal, how can you be clear that anything was achieved?
I think its important to define what I mean by VDI. VDI is a term that means many different things to different people. VDI traditionally stands for Virtual Desktop Infrastructure, and for a while seemed to be a term owned by VMWare for desktops virtualized on ESX. As in the case of kleenex, it now seems to be a much broader term and used much more in the public domain. I will define VDI in the more logical sense as the abstraction and delivery of a desktop experience, the Windows OS to users. VDI is an alternate way of providing Windows to every user rather than the traditional method of locally installed systems bound to a piece of hardware (desktop/laptop) on every users desk.
So this all sounds very confusing, and it can be. Which leads us to the question as to why would we want to do this whole VDI thing? Why not just keep doing desktops in the traditional steps of: install, configure, deploy and manage. This leads us to our first reason or driver:
Simplified Efficient Management and Administration
While many people utilize the old school method of desktop management mentioned earlier, many also agree it can be painful and waste the valuable time of busy administrators who could instead spend time being proactive. Time spent supporting single desktop issues can become a blow to the TCO of the overall solution. Gartner has a good document on how improved desktop management can reduce TCO (Gartner Desktop Mgmt). Think of VDI as perhaps the ultimate form of desktop management. VDI can be deployed in a way that means a user gets a custom desktop that is as good as the day it was built (we all know desktop performance seems to deterioate with age!). It is delivered with all customizations, patches, configuration and security fixes in place on the first day and every day. Any hardware problem can simply be addressed by swapping the problematic device out and replacing it with an alternate. The user can log back into their same virtual desktop, possibly even to the same state including that email they were in the middle of! This can save administrators lots of troubleshooting time as well as make for happy productive users.
The next part of management is that of updating and patching. While there are good tools for deploying patches to traditional desktops – there still is the inevitable mix of patched and unpatched systems. Imagine an environment where you know every user is on the latest OS including the latest patches, and to roll out a patch you only need to do it once, to one system. VDI can make this a reality. Now, expand that to security configurations, application updates… you’re starting to see the picture now aren’t you!?
So we have this amazing, pristine, secure image that is personalized for users… Wouldn’t it be great if that was available to them internally as well as externally? Well that leads us to the next point:
Right now I would say VMWare View and Citrix XenDesktop are the leaders in the VDI space. Both of these companies include simple to use gateway products for use with their VDI solutions. This means users can simply log into a webpage from home, and access their VDI desktop. The very same desktop they use when they are in the office with all their applications and data. Imagine how this would help for the work from home initiative, pandemic planning, DR scenarios etc. Now add this to the fact that it can be done securely with granular control over how the remote client device can interact (clipboard, drive mappings etc) and you start to see the power of this solution. Users can be given an environment where no data can move between the home device and the virtual desktop and vice versa. Extend this solution to cover the myriad of remote devices including, iphones, ipads, androids, macs and linux machines. You can see how the flexibility of VDI really prepares a company for what I call workforce 2.0, or you may know them as those teenagers with their faces buried in their iphone/ipad etc . With VDI based remote access, VPN access and the security concerns around adding a node to your network are eliminated.
So now you’re on board, sounds great…. In the words of those late night informercials – “But Wait! There’s more!”..
Flexibility and Scalability
Since VDI is heavily based on virtualization, it inherently scales well. Most solutions out there are designed with scalability in mind. For example, with an acquisition your company suddenly needs to provide desktops to 200 more users. In the traditional model this would have meant a couple weeks of work, with VDI this could be done in an afternoon.
Lets think of an alternate scenario, imagine windows 8 comes out, I know, I know… But lets say it does and you now need to migrate your 1000 users to Windows 8. In a VDI deployment this is a breeze, simply create your new image and assign it to users. On next logon they can be happily (or unhappily) using windows 8! Sure this might be a slight over simplification, but VDI will make it much simpler than the traditional visit to every desktop scenario.
Another example of the flexibility of VDI is that legacy hardware or thin clients can be used to run environments that they could never support. Don’t want to replace the aging desktops for all your users? No worries, just have them log into their VDI desktop where they can be running the latest OS and applications at speeds they haven’t even experienced on their local desktop.
Now I could go on and on about VDI… It’s my job, that’s what I do- But I think this is a good place to stop. VDI changes the game, and there’s a lot more to VDI and the various deployment options available. We haven’t even got into local mode, client virtualization, or desktop streaming etc., but that’s an article for another day. What matters is why you want to virtualize your desktops – and I think we’ve listed some pretty compelling reasons.
There’s lots of info out there, all sorts of product matrixes and fact sheets. However time and again customers want to know, what does it all mean to me, what should I pick.
I’ve tried to go through and look at the features that really matter to customers and are clear differences between the two and list them here. I’ve not taking into account cost (although indicated where additional licensing would be required).
Effectively this is a comparison of Xendesktop Enterprise and VMWare View 4.6 Premier, the only items listed are items where the competitor can provide what the other lacks.
These items often change rapidly so forgive me if this list contains items that are no longer valid or incorrect. Feel free to comment below and I will maintain this list with any feedback I receive.
A key resource was this whitepaper by Ruben Spruit entitled VDI Smackdown
Here is a link to VMWare View pricing
I could not find a clear link to XenDesktop pricing but here is a link to the XenDesktop Editions List
Interesting article stating that VMWare has removed the profile management portion of the View 4.5 solution.
This is critical as customers need a way to manage and centralize user profiles. Also the fact that View is being pushed back in shipping leads me to have some concerns….
With both Citrix and VMWare leading the VDI charge with their respective XenDesktop and View technologies this has definitely become a hot topic.
Both of these technologies offer interesting and compelling use scenarios to deliver a customized desktop to your end users. However they both have high investment costs as far as physical resources (CPU, Memory and in some cases huge SAN usage). Additionally the number of moving parts can be quite high and administration skill level is something that can be intimidating to those who are new to the field.
One solution that I am finding consistently meets the needs of many customers who are interested in VDI is a simple published desktop delivered via XenApp. With the latest version of XenApp – version 6 running on W2K8 R2 a lot of the XenApp shortcomings that were not issues in XenDesktop and View are now integrated in XenApp.
Items such as:
Many of these items vastly improve a user who is leveraging XenApp as a traditional desktop replacement.
I like to combine the published desktop with a PNAgent (XenApp online services plugin) so I can deliver customized applications to a standard desktop. This lets me maximize the number of users that a single XenApp server can support without the need to silo into multiple servers.
This PNAgent when configured correctly will allow users applications to populate the start menu and/or desktop and do passthrough session sharing. This session sharing is the secret to a great user experience. Applications launch immediately without the need for another session to be created, and allows drag and drop functionality within the desktop.
This solution is often the final destination for those who have heard of VDI and come looking to find out more.