How to add a PowerShell host to vRO

When you add a PowerShell host to vRealize Orchestrator (vRO) you are able to kick-off PowerShell scripts from your vRO workflows or just from the vSphere WebClient! Which can make your day to day work so much easier. So here is a short post about how you can add a PowerShell host to vRO.



  • vRealize Orchestrator
  • vRO PowerShell Plug-in v1.0.6.2442318 (link)
  • Windows 2008 R2+ with PowerShell 2.0+
    In the past I had some issues with the vRO v1.0.5 Plug-in and the default realm so please check which vRO PowerShell Plug-in you are using!

    For a Stand-alone PowerShell host :

    Then logon to your PowerShell host and configure Windows Remote Management.

    Open an elevated command prompt and run the following commands :

    Now the PowerShell host has been configured the PowerShell host can be added to vRO.
    Read More

    Create vRealize Operations certificate for Load Balancing

    For a project I’m currently working on, we are designing a large vRealize Operations (vROps) cluster with Load Balancing and High Availability requirements. Because I wanted to test all the vROps Load Balancing and HA features myself, I needed to create a proper certificate before putting the vROps appliances behind a Load Balancer. This article describes the steps you will have to take to create a proper certificate.


    To create the Certificate Request first download OpenSSL for Windows and install it in the default location : C:\OpenSSL-Win32

    After OpenSSL is installed we can create the configuration file : C:\OpenSSL-Win32\Certs\vrops.cfg and add the following information. Change the marked values starting and ending with % to your own specification.

    Read More

    VMware SRM and EMC VNX NFS IPv6 issue

    Today I was updating VMware Site Recovery Manager (SRM) for a customer after their EMC VNX arrays were upgraded to a new firmware level.

    It all went smooth and SRM seemed pretty happy with all green checkboxes, so it was time to run the Test Recovery Plan. But then the Test Recovery Plan failed, and returned the following error : “Error – Failed to recover datastore ‘DatastoreName’. An error occurred during host configuration”.


    And another beautiful “An unknown error has occurred” message appeared in the Task & Events tab of the ESXi hosts where SRM tried to configure the NFS Export on.


    According to the message the issue seems to be that the NFS Export couldn’t be mounted on the ESXi host, which is weird because a. the NFS exports could be mounted before and b. the hosts have active mounted NFS exports from the same storage array.

    After some troubleshooting and digging through the log files the only thing that seemed different than before was that now the IPv6 addresses were added to the “Access hosts” list of the fail-over test NFS Export that SRM created. This is because SRM queries the ESXi hosts for all (!!) VMkernel ports and add those IP addresses to the “Access hosts” of the fail-over test NFS Export, including the IPv6 addresses.

    Fortunately for me this customer doesn’t use IPv6 internally so it was quite easy to test if disabling IPv6 would solve the issue. And it did! After disabling the IPv6 the NFS Exports were mounted and the VMware SRM Recovery Plans were finished successfully.

    IPv6 can disabled on a v5.x or v6.x ESXi host by running the following command from the CLI :

    Or through the Web Client : Host -> Manage -> Networking -> Advanced -> Edit -> IPv6 Support -> Disabled


    Or just from the good old vSphere Client : Host -> Configuration -> Networking -> Properties -> Uncheck “Enable IPv6 support on this host system”


    And then reboot the host.

    We have submitted a SR to EMC and I’ll update this article if we receive any feedback on this issue.