General guidelines

It is important to correctly configure your guest operating systems so that they run optimally in the virtualized environment. In this chapter, we will show you how to configure different operating systems, but these are some general guidelines you can follow for any kind of guest:

  1. Install the flexVDI guest tools. They include device drivers for paravirtualized devices that will drastically increase the guest performance. They also include the tools and agents that enable some of flexVDI features, like Follow-me Printing and Single Sign-On.
  2. Disable swap partitions/pagefiles. They will make clone images grow very fast. If you are getting out of memory errors in the guests, just increase their allocated RAM.
  3. Disable fancy desktop effects. The virtual GPU is software based, and the Spice presentation protocol must transmit all the screen changes, so the perceived performance will drop if they have to show a full-screen animation, like a vanishing window.
  4. Configure your virtual hard drives as SSD disks. You will avoid unnecessary write operations.
  5. In template-based guests, disable system updates.

For information on particular guest operating systems, refer to the corresponding section:

Volatile guests

Volatile desktops are those desktops that fulfill the following conditions:

As a result, desktops can be 'recycled' periodically. That is, they can be destroyed and cloned again without an impact on the user experience. This volatility has several advantages:

Volatile desktops are commonly used in environments where all users must use a common, specific set of applications, e.g. a classroom, a call center or the accounting department of an enterprise. However, cloning the gold image into physical computers can become tedious. Instead, they are best suited for VDI environments because template-based guests can be cloned almost instantly. flexVDI encourages using volatile desktops whenever possible through Desktop Policies with the following features:

However, volatile desktops require a particular configuration of the guest operating systems (e.g. using roaming profiles and remote users), and the deployment of additional elements (an authentication server, a storage space for user and configuration data, a licensing server, etc). Please, refer to the corresponding section of each guest operating system for additional information.