vRO 7.x – Adding Windows PowerShell Host

This article will walk you through the process of configuring Windows PowerShell host and adding it to vRealize Orchestrator for PowerShell Script executions. Because vRO does not support PowerShell natively, it needs Windows Server to handle the tasks. Keep in mind this article will show how to configure PS Host to use basic authentication intended for lab environment. For PROD, you will require additional steps to harden or secure the PS Host not covered in this article.

Building Windows PowerShell Host

  1. Deploy Window Server or use existing. For this exercise I deployed a fresh Windows 2012R2 server.
  2. Enable WinRM. From your server open PowerShell prompt and run > winrm quickconfig 
  3. Enable Basic Authentication and Unencrythed traffic. This is the quickest way to get a test PS Host started. Note: I was having issues running the winrm commands from PowerShell Prompt so switched to CMD as administrator.
    • To enable Basic Authenticathion:

winrm set winrm/config/service/auth @{Basic=“true”}

  • To allow unencrypted data:

     winrm set winrm/config/service @{AllowUnencrypted=“true”}

  • Because server is not joined to Domain need to be trusted.

      winrm set winrm/config/client @{TrustedHosts=“IP of Orchestrator”}

    4. Create a service account on PS Host. Normally you would join the server to the domain and use a domain service account. But because I am not doing so, will be creating a local user account.

Adding PowerShell Host to Orchestrator

Next is to run a workflow to add a PowerShell host and configure the host connection parameters.

  1. Log into Orchestrator and click the Workflows view.
  2. Browse to Library > PowerShell > Configuration and navigate to the Add a PowerShell host workflow.
  3. Start Workflow : Add a PowerShell Host.
  4. Enter enter Name and Host/IP. Port is 5985, leaving it blank worked for me as well.

5. Specify host type:

  •  PowerShell host type: WinRM
  • Transport protocol: HTTP
  • Authentication: Basic

6. User Credentials:

  • Session mode: Shared Session
  • Username and Password

7. Select your Shell Code and Submit

8. After submission, if everything is alright, the workflow should finish success.

You can verify a proper functionality by checking the available Snapins via the vRO Inventory View:




Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *