Category Archives: Top 10 Virtual Desktop Mistakes
The virtual desktop top 10 list is complete! Of course there are numerous things people can do to mess up their environment, but the 10 discussed are probably the 10 most critical. If you get them wrong, you will struggle to survive.
But the list doesn’t end there. My colleagues (Tarkan Koçoglu, Nicholas Rintalan and Doug Demskis) and I couldn’t limit ourselves to just 10 mistakes which is why we have honorable mention status to a few more items J. It’s our way of keeping the top 10 list while allowing ourselves some leeway. Besides, Top 10 is so much better than Top 13 or Top 19 (top 10 has worked for David Letterman for years).
So what are these honorable mentions I speak of?
- NIC Teaming: Provisioning services streams the desktop image to the virtual desktop. Provisioning services NICs should be teamed for throughput/aggregation and not just for failover/redundancy.
- NIC Optimization: Although Provisioning services can run with the default NIC configurations, the environment can run faster with optimizations like Disable Large Send Offload
- Common Image: Reducing the number of images helps simplify management and updates as fewer image updates are required. However, using a single image across multiple physical end point platforms can become difficult to maintain. Specific hardware drivers can potentially conflict and installing multiple device drivers results in image bloat. It is often better to create different images for different hardware (not applicable if the end point is virtualized).
- VDI for Wrong Reason: Organizations should do virtual desktops because there is a business reason to provide users with a Windows XP/Windows 7 desktop interface. Without a business reason, the virtual desktop solution will be seen as extravagant and costing too much money for no value.
That completes the current Top 10 list and honorable mention for virtual desktop mistakes. If you want, you can see the entire blog series via the Top 10 Virtual Desktop Mistakes link. If you prefer documents, then sign up for the XenDesktop Design Handbook where you will get the Top 10 list plus so much more.
Enjoy and good luck
Daniel – Lead Architect
I’ve spent the last month or so discussing the top 10 mistakes seen on desktop virtualization implementation so you can learn from other’s mistakes. I’ve discussed 9 different things so far and they were:
And now it is time for the #1 thing that people mess up with desktop virtualization? Read the rest of this entry
Default configurations are great in that they make the setup and configuration easy. Unfortunately, they don’t work for all environments. In fact, if you simply use the defaults for an entire virtual desktop deployment, you will miss out on tons of optimizations to allow your environment to scale. Simply following the defaults is the 2nd most common mistake people make when implementing XenDesktop. Read the rest of this entry
It almost sounds like I’m talking about personal finances. You better plan your cache appropriately or you will run out. I’m not talking about money; I’m talking about system memory (although if you plan poorly we will quickly be talking about money).
It comes down to this… system cache is a powerful feature allowing a server to service requests extremely fast because instead of accessing disks, blocks of data are retrieved from RAM. Provisioning services relies on fast access to the blocks within the disk image (vDisk) to stream to the target devices. The faster the requests are serviced, the faster the target will receive. Allocating the largest possible size for the system cache should allow Provisioning services to store more of the vDisk into RAM as opposed to going to the physical disk. Read the rest of this entry
Building a virtual desktop is simply a matter of installing the Windows operating system. Right? Slow down… although this will work, it won’t give you the best performance and scalability. One of the items that many people mistakenly forget to accomplish is to optimize the base operating system. This is the 7th mistake out of the top 10 mistakes made with virtual desktops: Read the rest of this entry