Desktop Virtualization is not Server Virtualization

Following an interesting article from Harry Labana where Larry explains the top reasons whyVDI projects will fail if they are done with a presumption that desktop virtualization is similar to server virtualization.

  1. Desktop Virtualization is about user experience and agility, Server Virtualization is about consolidation and cost savings.
  2. Wrong, both are meant for cost savings and  hardware optimization. The difference is that you don’t design it the same way. The user desktop experience is a major factor when designing a VDI project. 

  3. In the physical world, do your server administrators manage your desktop infrastructure?
  4. Big companies have several teams/departments, and for every project that spans several areas, they meet each other to provide the best design/solution.  Would that be different with VDI? Of course not!

  5.  The management workflow for desktops is different.
  6. Sure it is and Desktop Teams will be involved, and the procedures will have to be adapted.

  7. Desktops require a different security model.
  8. Correct, and so far only VMware can give you the granularity you need to assign Desktop Admins rights and permissions down to a VMs.

  9. Desktop scale means rethinking your virtualization infrastructure.
  10. I’m wondering why Larry says “virtualization infrastructure…”  without a “S” like in Silo because frankly I won’t mix in the same virtualizaton infrastructure my virtual servers and my virtual desktops, would you ? No you won’t, you build different environment to cope with the load and type of virtual desktops/users.

  11. Optimize virtual infrastructure for user experience.
  12. Basically you must assign the right virtual desktops to he right users.  The CAD/CAM user will hate you if you give him a virtual desktop and you will be sacked if your boss cannot connect his iPhone to his virtual desktop 🙂

  13. Desktops management is different and does not require the high end features of Server Virtualization that add to cost.
  14. Don’t overcomplicate things that you wouldn’t normally do for a desktop. If you get your organization to understand this and behave accordingly it will resolve many debates about how best to implement. Simply put your questions and actions in the context of it’s a desktop.


About PiroNet

Didier Pironet is an independent blogger and freelancer with +15 years of IT industry experience. Didier is also a former VMware inc. employee where he specialised in Datacenter and Cloud Infrastructure products as well as Infrastructure, Operations and IT Business Management products. Didier is passionate about technologies and he is found to be a creative and a visionary thinker, expressing with passion and excitement, hopefully inspiring and enrolling people to innovation and change.
This entry was posted in Uncategorized. Bookmark the permalink.

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