You must edit a configuration file on your vRealize Orchestrator server to specify the domain name and domain controller name.

Prerequisites

You must have the root password if you are using the vRealize Orchestrator virtual appliance or the administrator credentials if vRealize Orchestrator is installed in a Windows server.

Procedure

  1. Log in as root (or as an administrator if you have a Windows server).
  2. Search for the krb5.conf file and rename it to krb5.conf.back.

    On a virtual appliance, this file is located in etc/krb5.conf, if it exists.

  3. Create a krb5.conf file in the appropriate directory.

    Server Type

    Description

    Virtual appliance

    /usr/java/jre-vmware/lib/security/

    Windows server

    C:\Program Files\Common Files\VMware\VMware vCenter Server - Java Components\lib\security\

  4. Open the krb5.conf file with a text editor and add the following lines, with the appropriate values:
    [libdefaults]
       default_realm = YOURDOMAIN.COM
       udp_preference_limit = 1
    [realms]
       YOURDOMAIN.COM = {
          kdc = yourDC.yourdomain.com
          default_domain = yourdomain.com
       }
    [domain_realms]
    . yourdomain.com= YOURDOMAIN.COM
    yourdomain.com= YOURDOMAIN.COM
  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.

What to do next

Add physical machines as PowerShell hosts. See Run Workflows to Add Physical Machines as PowerShell Hosts.

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. 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 and Prerequisites for Adding Unmanaged Machines to Pools.