6.1

n
For vSphere virtual machines, install the latest version of VMware Tools in the unmanaged virtual
machine.
For step-by-step instructions, see the VMware vSphere help.
n
Install the appropriate version of View Agent in the unmanaged machine. See “Horizon vRealize
Orchestrator Plug-In Functional Prerequisites,” on page 13.
For step-by-step instructions, see the topic "Install View Agent on an Unmanaged Machine," in Setting
Up Desktop and Application Pools in View.
n
If the unmanaged machine is a Windows Server machine, enable the server to be used as a remote
desktop:
a Log in to View Administrator.
The View Administrator interface uses a URL with the following format: https://connection-
server/admin.
b Go to View Configuration > Global Settings.
c Select the General tab and click Edit.
d Select the Enable Windows Server desktops check box and click OK.
n
For vSphere virtual machines, configure the vCenter Server instance to use the Share a unique session
option for managing user logins:
a Log in to the vRealize Orchestrator configuration console.
The configuration console uses a URL with the following format: https://vco-server:8283.
b Go to vCenter Server and click Edit for the vCenter Server instance.
c Under Specify which strategy will be used for managing the users logins, select Share a unique
session and click Apply changes.
d Restart the vRealize Orchestrator Server service.
If you are using vCenter Orchestrator 5.5.2, the name of the service is vCenter Orchestrator Server
service.
The Add Unmanaged Machines to Pool workflow, for vSphere virtual machines, has some important
limitations. See “Add Unmanaged Machines to Pool,” on page 27.
For physical machines and non-vSphere virtual machines, you must perform additional configuration tasks.
See “Configure a Physical Machine for an Unmanaged Pool,” on page 71 and “Configure vRealize
Orchestrator to Use Kerberos Authentication with Physical Machines,” on page 73. You can then run the
Add Physical Machines to Pool workflow, available in the Workflows/Example folder, or else run the Register
Machines to Pool workflow and the PowerShell workflows mentioned in “Run Workflows to Add Physical
Machines as PowerShell Hosts,” on page 74.
Adding Physical Machines and Non-vSphere Virtual Machines to
Pools
Several configuration tasks are required for adding physical machines and non-vSphere virtual machines,
such as those you can create with Citrix XenServer, Microsoft HyperV, or VMware Workstation, to manual
unmanaged desktop pools.
After you satisfy the requirements listed in “Prerequisites for Adding Unmanaged Machines to Pools,” on
page 69 you must complete the following tasks:
1 Enable Windows Remote Management, set remote execution policies, add the Orchestrator server as a
trusted host, and enable communication with the PowerShell plug-in. For instructions, see “Configure a
Physical Machine for an Unmanaged Pool,” on page 71.
Using the Horizon vRealize Orchestrator Plug-In
70 VMware, Inc.