The most fundamental question to consider is whether a certain type of user needs a persistent desktop or a non-persistent desktop. Whether you use persistent or non-persistent desktops depends on the specific type of worker.

Persistent Desktop

Persistent desktops have data in the operating system image itself that must be preserved, maintained, and backed up. For example, users who need to install some of their own applications or have data that cannot be saved outside of the virtual machine itself (such as on a file server or in an application database) require a persistent desktop.

There are several ways to create persistent desktops in Horizon 8:

  • You can create pools of full clones (also known as full virtual machines).
  • If you have already created virtual desktops or physical desktops (vCenter virtual machines, non-vCenter virtual machines, or physical PCs), you can import them into Horizon 8 as persistent desktops using the dedicated-assignment manual desktop pool.

Persistent desktops give users the highest degree of flexibility and control over their own desktops, however, they consume more compute resources and are more difficult to manage by IT. These desktops might require traditional image management techniques. Persistent desktops can have low storage costs in conjunction with certain storage system technologies. Since each persistent desktop is unique and must be preserved, backup and recovery technologies are important when considering strategies for business continuity.

Non-persistent Desktop
Non-persistent desktops are stateless images that are identical to one another. They are primarily used by users who do not need to install or preserve their own applications. Non-persistent desktops have many advantages, such as being easier to support and having lower storage costs. Other benefits include a limited need to back up the virtual machines and easier, less expensive disaster recovery and business continuity options. The virtual desktops themselves do not need to be protected as there is no unique user data stored. In the event that the virtual desktops are destroyed, you can simply re-create them from the golden image. Folder redirection and various profile technologies can optionally be used to storage user profile and user data. In Horizon 8 you can create non-persistent desktops by leveraging instant clones.

You can also specify how users are assigned desktops in a pool.

Dedicated-assignment pools Each user is assigned a particular virtual desktop and returns to the same desktop at each login. Dedicated assignment pools require a one-to-one desktop-to-user relationship. For example, a pool of 100 desktops are needed for a group of 100 users.
Floating-assignment pools Using floating-assignment pools also allows you to create a pool of desktops that can be used by shifts of users. For example, a pool of 100 desktops could be used by 300 users if they worked in shifts of 100 users at a time. The remote desktop is sometimes deleted and re-created after each use, offering a highly controlled environment.

Pools for Task Workers

Because task workers perform repetitive tasks within a small set of applications, you can utilize non-persistent desktops, which saves on storage an compute costs and make desktop management easier.

Use the following pool settings for instant-clone desktop pools:

  • Use-floating assignment for the instant-clone desktop pool so that users log in to any available desktop. This setting reduces the number of desktops required if everyone does not need to be logged in at the same time.
  • Configure the option to automatically logoff after disconnect, which deletes the instant clone whenever a user logs out. A new instant clone is created and ready for the next user to log in, thus effectively refreshing the desktop on every log out.
  • To optimize compute resource utilization, use the dynamic pool provisioning capability of instant-clone desktop pools to grow or shrink the desktop pool based on demand. Be sure to specify enough spare desktops to satisfy the login rate.
  • Consider storing instant-clone desktops on local ESXi data stores. This strategy can offer advantages such as utilizing inexpensive hardware, and faster virtual- machine provisioning. For a list of limitations for storing instant clones on local datastores, see Reducing Storage Requirements with Instant Clones.
    Note: For information about other types of storage options, see Managing Storage for Virtual Desktops.
  • Use profile management tools such as VMware Dynamic Environment Manager or Microsoft FSLogix so that users always have their preferred desktop appearance and application settings with Windows user profiles.

Pools for Knowledge Workers and Power Users

Knowledge workers usually are required to create complex documents and have them persist. Power users often need to install their own applications and have them persist. Depending on the nature and amount of personal data that must be retained, they require either a non-persistent desktop or a persistent desktop.

Use the following settings with non-persistent desktops for knowledge workers who do not need to install their own applications:

  • Create dedicated-assignment desktop pools so that each user is guaranteed to have a virtual desktop anytime they login.
  • Implement folder redirection, roaming profile, or another profile management solution to store and persist the user profile and user data.

For workers who must install their own applications, which adds data to the operating system disk, the best option is to create full-clone virtual machine desktops.

Pools for Kiosk Users

Kiosk users might include customers at airline check-in stations, students in classrooms or libraries, medical personnel at medical data entry workstations, or customers at self-service points. Accounts associated with client devices rather than users are entitled to use these desktop pools because users do not need to log in to use the client device or the remote desktop. Users can still be required to provide authentication credentials for some applications.

Virtual machine desktops that are set to run in kiosk mode use non-persistent desktops because user data does not need to be preserved in the operating system disk. Kiosk mode desktops are used with thin client devices or locked-down PCs. You must ensure that the desktop application implements authentication mechanisms for secure transactions, that the physical network is secure against tampering and snooping, and that all devices connected to the network are trusted.

As a best practice, use dedicated Connection Server instances to handle clients in kiosk mode, and create dedicated organizational units and groups in Active Directory for the accounts of these clients. This practice not only partitions these systems against unwarranted intrusion, but also makes it easier to configure and administer the clients.

To set up kiosk mode, you must use the vdadmin command-line interface and perform several procedures documented in the kiosk mode topics in the Horizon Administration document.

As part of this setup, you can use the following instant-clone desktop pool settings.

  • Use-floating assignment for the instant-clone desktop pool so that users log in to any available desktop. This setting reduces the number of desktops required if everyone does not need to be logged in at the same time.
  • Configure the option to automatically logoff after disconnect, which deletes the instant clone whenever a user logs out. A new instant clone is created and ready for the next user to log in, thus effectively refreshing the desktop on every log out.
  • Consider storing instant-clone desktops on local ESXi data stores. This strategy can offer advantages such as utilizing inexpensive hardware, and faster virtual- machine provisioning. For a list of limitations for storing instant clones on local datastores, see Reducing Storage Requirements with Instant Clones.
    Note: For information about other types of storage options, see Managing Storage for Virtual Desktops.
  • Use an Active Directory GPO (Group Policy Object) to configure location-based printing, so that the desktop uses the nearest printer. For a complete list and description of the settings available through the Group Policy Administrative templates (ADMX files), see the Horizon Remote Desktop Features and GPOs document.
  • Use a GPO or Smart Policies to control whether local USB devices are connected to the desktop when the desktop is launched or when USB devices are plugged in to the client computer.