Horizon Cloud Service supports dedicated, floating, and session desktops. Floating (nonpersistent) desktops are recommended in a Horizon Cloud Service implementation because they require less time, maintenance, and expense than the other options.
- Dedicated (persistent) desktops – A virtual desktop is assigned to users the first time they log in, and they use the same virtual desktop for subsequent logins. Like a physical computer, changes made to a persistent desktop stay with that desktop. You might choose to provide persistent desktops to developers who need to install their own software on their VMs. However, for most use cases, persistent desktops require more time to build, more effort to manage, and are more expensive.
- Floating (nonpersistent) desktops – A virtual desktop is assigned to users each time they log in, so users do not use the same virtual desktop for subsequent logins. When a user logs out, the nonpersistent desktop resets to a pristine state and changes to the desktop are lost. However, changes can be preserved by using profile management and folder redirection. For updating and patching, you update the image and push the update to the desktop assignment. For most use cases, nonpersistent desktops are the most convenient solution.
- Session (shared) desktops – An RDSH published desktop that is shared across multiple users. Also commonly known as a session-based desktop. Shared desktops should be locked down, and users should not be allowed to make system changes or install applications. For user-based changes, you can use Dynamic Environment Management and folder redirection to preserve settings. For image updates and patch management, you can update the image and push the update to the RDSH published desktop assignment.