
Typically, when people think about desktop design, the first thing they think about is what provisioning engine they want to use. So before you go shopping for storage arrays and servers, you need to start looking at your desktops. Virtual desktop environments are all about the end user and what they need. If you want to learn more about the art and science of designing VDI environments, I highly recommend The VDI Design Guide by Johan van Amersfoort. This post will provide an overview of the topic and help you understand all of the considerations that go into designing an environment. I couldn’t do it justice in one blog post. This post, Part 3, will discuss design considerations for the Horizon virtual desktops, and Part 4 will discuss design considerations for Active Directory.īefore I begin, designing an infrastructure to support a virtual desktop environment is a complex process. So before we move into installing the actual components for a Horizon environment, we’ll spend the next two posts on design considerations. If care isn’t taken, the wrong design could be put into production, and the costs of fixing it could easily outweigh the benefits of implementing the solution.

Whether it is Horizon, XenDesktop, or a cloud-based Desktop-as-a-Service provider, the implementation of a virtual desktop and/or published applications environment requires a significant time investment during the design phase.
