Use this check list to verify that you have performed all the tasks required to run the appropriate workflow for adding the machine to a manual unmanaged pool.
Separate workflows are available to allow a delegated administrator to add physical and virtual machines to manual desktop pools in View.
Use the Add Unmanaged Machines to Pool workflow for unmanaged machines that are in fact managed by a vCenter instance, but the vCenter instance has not been added to View.
Use the Add Physical Machines to Pool workflow, available in the Workflows/Example folder, for adding physical machines and non-vSphere virtual machines, such as those you can create with Citrix XenServer, Microsoft HyperV, or VMware Workstation. Alternatively, you can run the other workflows as described in Adding Physical Machines and Non-vSphere Virtual Machines to Pools.
Before you run a workflow for adding unmanaged machines to a pool, verify that you have performed the following tasks:
Add guest credentials by running the Add Guest Credentials workflow of the Horizon vRealize Orchestrator plug-in.
This workflow is located in the Configuration/Horizon Registration Configuration folder. The guest credentials must be for logging in as an administrator or domain administrator on the virtual machine.
Run the Manage Delegated Administrator Configuration for Registration workflow, in the Configuration/Horizon Registration Configuration folder, to allow the delegated administrator to use the guest credentials and have access to the datacenter and virtual machine folders.
Run the Manage Self Service Configuration for Registration workflow, in the Configuration/Horizon Registration Configuration folder, to allow end users to use the guest credentials and have access to the datacenter and virtual machine folders.
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.
Install the appropriate version of View Agent in the unmanaged machine. See Horizon vRealize Orchestrator Plug-In Functional Prerequisites.
For step-by-step instructions, see the topic "Install View Agent on an Unmanaged Machine," in Setting Up Desktop and Application Pools in View.
If the unmanaged machine is a Windows Server machine, enable the server to be used as a remote desktop:
Log in to View Administrator.
The View Administrator interface uses a URL with the following format: https://connection-server/admin.
Select the General tab and click Edit.
Select the Enable Windows Server desktops check box and click OK.
For vSphere virtual machines, configure the vCenter Server instance to use the Share a unique session option for managing user logins:
Log in to the vRealize Orchestrator configuration console.
The configuration console uses a URL with the following format: https://vco-server:8283.
Go to vCenter Server and click Edit for the vCenter Server instance.
Under Specify which strategy will be used for managing the users logins, select Share a unique session and click Apply changes.
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.
For physical machines and non-vSphere virtual machines, you must perform additional configuration tasks. See Configure a Physical Machine for an Unmanaged Pool and Configure vRealize Orchestrator to Use Kerberos Authentication with Physical Machines. 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.