Seven desktop virtualization mistakes

Seven desktop virtualization mistakes

Desktop virtualization has hit the mainstream for businesses of all types and sizes.  In fact, it’s gradually becoming considered best practice by many who are driven to virtualization by the promise of improved agility, manageability, security and user productivity. There are some common desktop virtualization mistakes of which it is important to be mindful.  But the migration doesn’t have to be massively complex according to a recent eBook from Citrix called The 7 Big, Bad Pitfalls of Desktop Virtualization Deployment.

desktop virtualization mistakes

Here is an overview of the seven common desktop virtualization mistakes and pitfalls from Citrix…

1. Not starting with clear agreement on goals

If virtualization programs run into problems, it often comes down to this simple issue: different people went into it for different reasons – desktop virtualization touches just about every department.  Not being in agreement on the agenda before you begin the process is a critical error.

2. Treating all your users alike

No two users are alike. Sales teams are very different from engineers, accountants or traders. The use and demand each department and each individual put on the desktop are very different from each other.  Therefor each requires a different approach to virtualization.

3. Failing to accurately estimate your hardware needs up front

It’s important to estimate just how many servers and how much storage you’ll need for your virtualization program.

4. Failing to understand your apps before migrating

Application migration is too often an afterthought in desktop virtualization programs. But apps are a critically important variable.

5. Leaving your users out of the loop

You aren’t migrating desktops you are migrating users.  If you aren’t delivering an improved user experience then the  migration won’t deliver the value it needs.  You can’t improve the user experience by leaving them out of the loop.

 6. Don’t just scale up your Proof of Concept

A proof of concept will help assure you can stand up a simple design with the hardware and applications you expect to support, but many desktop virtualization deployments go pear-shaped because they simply scale up the basic PoC architecture to be rolled out to an enormous user base.

 7. Not planning for the future

Take to time to evaluate your entire virtualization from the get-go.  Even if you’re choosing to go with a phased roll out starting with a single group, having a strong idea where you’re going in the future will you make more informed short-term decisions.

No Comments

Post A Comment