Desktop-VDI
Five Ways to Avoid Common VDI Deployment Mistakes

Five Ways to Avoid Common VDI Deployment Mistakes

Avoid expensive mistakes and dissatisfied users with these best practices.

When deploying new technologies, it’s common to cross some speed bumps along the way—and when it comes to virtual desktop infrastructure (VDI), it's no different. However, if you plan ahead and are aware of the top mistakes that organizations tend to make when deploying VDI, you’ll be less likely to make the same errors.

David Johnson, principal analyst at Forrester Research, says that when deploying VDI, it’s very important to understand which people in the organization are going to use VDI and match the technologies to what they really need. “A lack of understanding of who and how people will use VDI, along with not fully knowing what the user experience will be like and what the technologies are and are not capable of, are all factors that can create obstacles,” Johnson says.

Here's what you need to know to avoid common VDI deployment mistakes: 

1. Understand When You Should Spend and When You Will Save

Cost savings is typically the no. 1 driver for VDI interest, Johnson says. However, organizations often set themselves up for disappointment when they neglect to invest in the ideal solution components to meet their specific needs—in the name of saving money. “If cost savings is your primary reason for turning to VDI, you could be working against yourself,” Johnson warns, explaining that slightly higher upfront costs can actually save money and time over the long-term. “A lack of end user acceptance is one of the major reasons why VDI can fail, and if you’re not spending money on the right things, that can negatively impact the final product,” he says. For example, spending more upfront on graphics virtualization can help you avoid the long-term, and often higher costs, of supporting a dissatisfied workforce.

2. Get Outside Help

It’s common for organizations to think they can tackle any project, but Johnson explains that he regularly finds that companies regret not getting more outside help throughout both the planning stages and the execution phase. If a company is set on doing this in-house, Johnson says it’s important to find a specialist who has a lot of experience with VDI and have him work closely with the tech vendor of your choice. If you opt to go with a service provider, Johnson suggests looking for one that best matches the project’s scope.

3. Understand Who Will Be Using VDI

Deploying VDI is about empowering employees in the company to work in ways that they couldn’t work before, whether that involves more freedom of choice when it comes to applications or allowing them to work remotely and benefit from increased flexibility. Johnson says an organization’s IT leadership should take a close look at those who will be using VDI, survey them, question them about their needs and desires, and tailor the technologies to help them reach their end goals.

4. Use the Right Tools for the Job

Johnson says VDI might be the best tool for the job in many cases, but when and if it’s not, an organization shouldn’t be afraid to enlist the help of additional technologies. “Sometimes it means using three or four different technologies to have the right delivery model for the way people want to use the software,” Johnson says.

5. Understand Your Priorities

Aside from helping employees get their job done more efficiently, there are a number of other factors driving VDI interest, from better performance and security to increased manageability. If you have a clear idea of which factors are driving your VDI interest, it will be easier to implement technologies to complement those priorities—which will lead to a better and more rewarding experience overall.

Underwritten by HPE, NVIDIA and VMware. 

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish