EHC 4.1: ESXi Host Migration Process (vCenter Host Migration with ViPR Export Groups)

This procedure details the steps to execute in order to remove an ESXi host from a source ViPR Export Group and add to an existing target Export Group.

Note: this procedure applies to ViPR 3.0 and below, ViPR 3.6 introduces a more automated procedure which I intend to cover in a future post.

Host Removal – remove ESXi Host from a ViPR Export Group

Please ensure there are no EHC StaaS or VIPR native tasks being executed while performing the following procedure.

Note: Ensure the version of SMI-S complies with the EHC ESSM stated version.

The following steps detail the procedure for removing a host from a vSphere ESXi cluster in vCenter and utilizing the ViPR CLI to remove the same host from the cluster Export Group. Continue reading

vRealize Automation Blueprint Creation – vSphere Templates not Displaying

While in the process of creating a vRA blueprint, none of my vSphere templates were displaying as an option for selection. This led me to verify some of my previous config, which led to identifying the source of the problem to be a misplaced template. Thanks @HeagaSteve for pointing me in the right direction!

As you can see when I click on the ellipsis in order to select a template I receive ‘No data to display’ in the list box:

vrabptemplate1a Continue reading

vRealize Automation 7.1 – Create Endpoints & Fabric Groups (Part 3)

vRealize Automation 7.1 – Create Tenant & Configure Authentication (Part 2)

Following on from the tenant & authentication post above, the following steps detail the creation of an Endpoint & Fabric Group in vRA 7.1.

This post will show how to create a vCenter endpoint followed by a Fabric Group, a vRO endpoint and the credentials required to connect vRA to these endpoints.

Begin by logging into the new tenant with a user who has the IaaS Administrator privileges:


Nice flow chart from


1. Store Credentials:

Login into your tenant:



Continue reading

vRealize Automation 7.1 Wizard Install – vCenter Agent Name not aligned with IaaS Host

Looks like there maybe a bug in the vRA 7.1 wizard deployment. I’m running vRA version  7.1 build 4270058 and Windows 2012 R2 build 9600.

Even though we configured the vCenter endpoint name as cloudvc01 during the vRealize Automation wizard based install, the IaaS Agent server was displaying the vCenter agent name using the FQDN cloudvc01.ppsilver.lab.local (screen captures below):

Wizard input – ‘Agents’:


Continue reading