The first step in the process of deploying a pool of cloned desktops is to create a virtual machine in vSphere , install and configure the operating system.
Create a Virtual Machine in vSphere You can create a virtual machine in vSphere from scratch or by cloning an existing VM. This procedure describes creating a VM from scratch.
Install a Guest Operating System After you create a virtual machine, you must install a guest operating system.
Prepare a Guest Operating System for Remote Desktop Deployment You must perform certain tasks to prepare a guest operating system for remote desktop deployment.
Prepare Windows Server Operating Systems for Desktop Use To use a Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 virtual machine as a single-session virtual desktop (rather than as an RDS host), you must perform certain steps before you install Horizon Agent in the virtual machine. You must also configure Horizon Administrator to treat Windows Servers as supported operating systems for Horizon 7 desktop use.
Install Desktop Experience on Windows Server 2008 R2 For published desktops and applications, and for virtual desktops that are deployed on single-user virtual machines that run Windows Server, scanner redirection requires that you install the Desktop Experience feature on the RDS hosts and the single-user virtual machines.
Install Desktop Experience on Windows Server 2012, 2012 R2, 2016, or 2019 For published desktops and applications, and for virtual desktops that are deployed on single-user virtual machines that run Windows Server, scanner redirection requires that you install the Desktop Experience feature on the RDS hosts and the single-user virtual machines.
Configure the Windows Firewall Service to Restart After Failures Some Windows Server 2012 R2, Windows 2016, Windows 2019, Windows 8.1, and Windows 10 machines that are deployed as single-session desktops do not become available immediately after they are provisioned. This issue occurs when the Windows Firewall service does not restart after its timeout period expires. You can configure the Windows Firewall service on the parent (master image) or template virtual machine to ensure that all machines in a desktop pool become available.