Digital Desktop Facilities (vdi) Faq

Additionally, those workers with high-performance desktop needs — such as engineers or creative professionals — can seldom be successfully integrated into a VDI architecture, due to performance issues with applications such as photo editing and 3D graphics. A VDI feasibility assessment is typically the first step taken to analyze and categorize the desktop environment in the organization, and the results can then be used to design a pilot VDI project. Should thin-client hardware replace the existing desktops in a VDI? Not necessarily. True thin-client terminals provide additional benefits such as reduced IT support and hardware costs. But in most cases, the existing desktop PC hardware can easily be converted for use as a remote desktop, either by installing a specialized thin-client OS (Linux) on it or customizing Windows by uninstalling everything but the remote-access client and launching it upon startup. A good approach is to use your existing desktop hardware as remote desktop clients and phase in true thin-client hardware over time as the desktops are retired. How long should a virtual desktop infrastructure solution deployment take? Most in-house VDI architectures can take anywhere from four to 12 months to assess, analyze, architect and deploy. A good portion of this time is spent assessing the existing desktop environment and designing a suitable VDI replacement. A pilot implementation will usually last two to six months to ensure the design goals can be met in a full-scale implementation. VDI solutions from a solution provider bring the benefit of turn-key solutions where resources can be allocated on-demand in most cases. This can significantly reduce the implementation time to as little as several weeks for a pilot project. What is the best way to address network performance issues with VDI? Ensuring that the end-user experience is as close to a real desktop as possible is one of the challenges that must be overcome with a virtual desktop infrastructure solution, particularly if the back-end VDI server infrastructure is located in a remote data center. Each VDI session must have adequate bandwidth to ensure that end-user performance expectations are met. When session traffic traverses a LAN, this is seldom an issue. However, over high-latency WAN links this can become problematic, especially over the Internet. This can be addressed using dedicated VDI WAN links to the data center, traffic management technologies and/or remote access protocols better suited for latent connections. How should the VDI architecture be designed for resource load? Ensuring that adequate resources are designed into a new virtual desktop infrastructure design is one of the most critical factors for success. The key to doing so is assessing the existing desktop CPU, storage, networking and memory usage patterns in the organization. Metrics should be monitored and collected over a sufficient timeframe (two to four weeks) from representative samplings of the desktop population to form a performance baseline for each category of user class. In addition, every application should be tested within the VDI environment to ensure it performs adequately and correctly. What is the best way to determine virtual desktop infrastructure host server sizing? This is a very difficult question to answer without a good baseline assessment to draw upon. But in general, you can estimate approximately five to seven virtual desktops per CPU core, assuming a relatively modern CPU such as the Intel Xeon 3GHz quad-core processor. So a single server with dual quad-core processors could accommodate a workload of approximately 40 to 50 virtual desktops, assuming adequate memory exists on the host. More on desktop virtualization Check out our desktop virtualization services resources . When it comes to each VDI user, what’s better: virtual machine pooling or dedicated VMs? Virtual machine (VM) pooling refers to maintaining a pool of available VDI VMs that are always available to be "checked out" by users. A user may get any VM within the pool and will not get the same VM each time they log into their desktop environment. By contrast, with dedicated virtual machines, the user will always get the same VM each and every time they log into their desktop environment. Dedicated VM environments are typically easier to set up and do not require the services of a "connection broker" like VM pooling requires. The connection broker provides the pooling services and manages the provisioning and tear-down of VMs based on organizational policy. Most organizations will prefer to use a connection broker due to the advanced features that it provides, such as automatic provisioning and the deployment of VMs.
For the original version including any supplementary images or video, visit


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 )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s