6.1

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
[e-mail]. 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 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.
12 Click Submit to run the workflow.
The View Agent token on the machine is now paired with the View Connection Server instance.
Chapter 7 Working with Unmanaged Machines
VMware, Inc. 75