You can add an endpoint and configure the PowerShell plug-in to connect to a running PowerShell host, so that you can call PowerShell scripts and cmdlets from vCenter Orchestrator actions and workflows, and work with the result.

Prerequisites
■

Verify that you have access to a Windows PowerShell host. For more information about Microsoft Windows PowerShell, see the Windows PowerShell documentation.

■

Log in to the vCloud Automation Center console as a tenant administrator.

Procedure
1

Select Administration > Advanced Services > Endpoints.

2

Click Add (Add a new resource action).

3

Select PowerShell from the Plug-in drop-down menu.

4

Click Next.

5

Enter a name and, optionally, a description.

6

Click Next.

7

Specify the PowerShell host details.

a

Enter the name of the host in the name text box.

b

Enter the IP address or the FDQN of the host in the hostName text box.

8

Select the PowerShell host type to which the plug-in connects.

Option

Action

WinRM
a

Enter the port number to use for communication with the host in the port text box under the PowerShell host details.

b

Select a transport protocol from the transportProtocol drop-down menu.

Note

If you use the HTTPS transport protocol, the certificate of the remote PowerShell host is imported to the vCenter Orchestrator keystore.

c

Select the authentication type from the authentication drop-down menu.

Note

To use Kerberos authentication, enable it on the WinRM service. For information about configuring Kerberos authentication, see Using the PowerShell Plug-In.

SSH

None.
9

Enter the credentials for a shared session communication with the PowerShell host in the sharedUserName and sharedUserPassword text boxes.

10

Click Add.

You added an Windows PowerShell host as an endpoint. Service architects can use the Advanced Service Designer to publish PowerShell plug-in workflows as catalog items and resource actions.