You add a PowerShell host and configure the host connection parameters by running a workflow. You can set up a connection to a remote or a local PowerShell host.

Procedure

  1. Log in to the Automation Orchestrator Client as an administrator.
  2. Navigate to Library > Workflows and enter the powershell and configuration tags in the workflow search box.
  3. Locate the Add a PowerShell host workflow and click Run.
  4. In the Name text box, enter the name of the host.
  5. In the Host / IP text box, enter the address of the host.
    Note: The Kerberos authentication requires a Fully Qualified Domain Name (FQDN) host address.
  6. (Optional) In the Port text box, type the port of the host. You use port 5985 for the HTTP or 5986 for the HTTPS protocol.
  7. On the Host Type tab, specify the PowerShell host type that the plug-in connects to.
    1. Select a transport protocol.
      Note: If you use the HTTPS transport protocol, the certificate of the remote PowerShell host is imported into the Automation Orchestrator keystore.
    2. Select the authentication type.
      Important: If you want to use Kerberos authentication, you must enable it on the WinRM service.
  8. On the User Credentials tab, select the type of session mode that the plug-in uses to connect to the PowerShell host.
    Option Description
    Shared Session The plug-in uses shared credentials to connect to the remote host. You must provide the PowerShell host credentials for the shared session.

    The PowerShell host credentials must belong to a member of the local administrators group.
    Session per User The Automation Orchestrator client retrieves credentials from the user who is logged in. You must log in with a user@domain format to Automation Orchestrator to use the Session per User mode.
  9. On the Advanced Options tab, from the Shell Code Page drop-down menu, select the type of encoding that the PowerShell uses.
  10. Click Run.

Results

After the workflow runs successfully, the PowerShell host appears in the Inventory view.

Troubleshooting

If the workflow fails with the Cannot Locate KDC (Dynamic Script Module name: addPowerShellHost#30) error, see Troubleshooting the workflow Add a PowerShell host in VMware Aria Automation Orchestrator.