6.1

5 If you are using a virtual appliance, use the following command to change permissions of the file to
make it readable:
chmod 644 /usr/java/jre-vmware/lib/security/krb5.conf
6 Verify that the PowerShell host (that is, the physical machine that needs to be registered) and the
domain controller host names can be resolved from the vRealize Orchestrator server.
The DNS of the vRealize Orchestrator must be the same as the DNS of the domain controller, or you can
add the machine names or IP addresses of the physical machines and domain controller to the hosts file
on the vRealize Orchestrator server.
On a virtual appliance, this file is located at /etc/hosts.
7 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.
What to do next
Add physical machines as PowerShell hosts. See “Run Workflows to Add Physical Machines as PowerShell
Hosts,” on page 74.
NOTE As an alternative to running the PowerShell workflows, you can use the Add Physical Machines to
Pool workflow, available in the Workflows/Example folder. This workflow combines the actions of the
Register Machines to Pool workflow and the PowerShell workflows mentioned in “Run Workflows to Add
Physical Machines as PowerShell Hosts,” on page 74. Before you run the Add Physical Machines to Pool
workflow, you must perform the tasks described in “Configure a Physical Machine for an Unmanaged
Pool,” on page 71 and “Prerequisites for Adding Unmanaged Machines to Pools,” on page 69.
Run Workflows to Add Physical Machines as PowerShell Hosts
You must run some PowerShell plug-in workflows to complete the process of adding physical machines and
non-vSphere virtual machines to desktop pools using the Horizon vRealize Orchestrator plug-in.
NOTE As an alternative to running the PowerShell workflows listed in this procedure and the Register
Machines to Pool workflow, you can run the Add Physical Machines to Pool workflow, available in the
Workflows/Example folder.
Prerequisites
n
Verify that you have the vRealize Orchestrator Plug-In for Microsoft Windows PowerShell, which
contains the workflows required for this procedure.
n
Verify that you have administrator credentials for the Orchestrator server. The account must be a
member of the vRealize Orchestrator Admin group configured to authenticate through vCenter Single
Sign-On.
n
Run the Register Machines to Pool workflow to register all machine DNS names into manual
unmanaged desktop pools in View. The Register Machines to Pool workflow returns a token (one for
each registered DNS) that will be pushed into the Windows Registry of the machines when you run the
PowerShell command described in this procedure.
Procedure
1 Log in to Orchestrator as an administrator.
2 Click the Workflows view in Orchestrator.
3 In the workflows hierarchical list, select Library > PowerShell > Configuration and navigate to the Add
a PowerShell host workflow.
Using the Horizon vRealize Orchestrator Plug-In
74 VMware, Inc.