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.

Before you begin

  • Verify that you have the vRealize Orchestrator Plug-In for Microsoft Windows PowerShell, which contains the workflows required for this procedure.

  • 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.

  • 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.

About this task

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.

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.
  4. Right-click the Add a PowerShell host workflow and select Start workflow.
  5. Provide the host name and fully qualified domain name of the physical machine and click Next.

    If the machine is not in a domain, you can use the IP address. If you do not supply the port number, the default port is used.

  6. Complete the form that appears and click Next.

    Option

    Action

    PowerShell remote host type

    Select WinRM from the drop-down list.

    Transport protocol

    Select HTTP from the drop-down list.

    Authentication

    If the machine is in the domain, select Kerberos from the drop-down list. If the machine is not in the domain, select Basic.

  7. Complete the form that appears.

    Option

    Action

    Session mode

    Select Shared session from the drop-down list.

    User name

    If the machine is in a domain, use the format administrator@domain.com. If the machine is not in a domain, use the user name of the local administrator account.

  8. Click Submit to run the workflow.
  9. When the workflow finishes, right-click the Invoke a PowerShell Script workflow, located in the PowerShell folder, and select Start workflow.
  10. Select the host you just added and click Next.
  11. (Optional) Add the Identity registry key.
    1. Check whether the hklm:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Identity registry key exists.
    2. If the registry key does not exist, run the following command:
      New-Item -Path "hklm:\SOFTWARE\VMware, Inc.\VMware VDM\Agent" -Name Identity
  12. In the Script text area, enter the following command:
    New-ItemProperty -Path "hklm:\SOFTWARE\VMware, Inc.\VMware VDM\Agent\Identity" -Name Bootstrap -PropertyType String –Value “TokenReturnedByWorkflow” –Force

    For TokenReturnedByWorkflow, use the token returned by the Register Machines to Pool workflow that you previously executed to register machine DNS names.

  13. Click Submit to run the workflow.

Results

The View Agent token on the machine is now paired with the View Connection Server instance.