Prepare a non-vSphere Machine For Omnissa Horizon 8 Management

You must perform certain tasks to prepare a non-vSphere machine to be managed by Horizon 8.

Note: Starting with Horizon 8 2406 release, you can use Amazon WorkSpaces Core for automated desktop pools. To prepare an Amazon WorkSpaces Core machine for that use case, instead of the steps below, follow the steps in Amazon WorkSpaces Core - Creating and Preparing Sources for Automated Desktop Pools.

Prerequisite

• Verify that you have administrative rights on the non-vSphere machine.

• To make sure that remote desktop users are added to the local Remote Desktop Users group of the non-vSphere machine, create a restricted Remote Desktop Users group in Active Directory except when the non-vSphere machines are physical machines.

  Note: Starting with Agent 2503, Horizon Agent simplifies authentication for Horizon Physical PCs by removing the requirement for Remote Desktop Users group membership.

Procedure

1. Power on the non-vSphere machine and verify that it is accessible to the Connection Server instance.

2. Join the non-vSphere machine to the Active Directory domain for your remote desktops.

3. Configure the Windows firewall to allow Remote Desktop connections to the non-vSphere machine.

What to do next

Install Horizon Agent on the non-vSphere machine. See Install Horizon Agent on a Non-vSphere Machine.