I prefer to do as much as I can with powershell, so that it is repeatable no matter where I happen to be installing things. Since I have to create a new VRops for Horizon installation at work, I decided to take this oppurtunity to create documentation about it.
I would assume that if you are reading this you already have powershell setup with the VMware Powercli module. If that’s the case, jump down to the OVA setup section. If you need a quick refresher on getting that installed, here are the steps:
Install-Module -Name VMware.PowerCLI
Install-Module -Name VMWare.Automation.Core
The first thing we have to do with the vRealize ova is convert it from SHA256 to SHA1.
- Download the OVF Tool from here: Always pick the current version on the VMware site
- Install the OVF Tool
- Open a command prompt and change into the directory where the OVF Tool is installed
cd "\Program Files\VMware\VMware OVF Tool"
- Run the ovftool against the OVA saving it as a SHA1 file.
ovftool.exe --shaAlgorithm=SHA1 c:\temp\vRealize-Operations-Manager-Appliance-184.108.40.20657692_OVF10.ova c:\temp\vRealize-Operations-Manager-Appliance-220.127.116.1157692_OVF10-sha1.ova
Now that we have an ova file that will work with powershell, it’s time to connect to our vcenter, and get the configuration options we need to provide.
- Connect to your vcenter
- Build the options object
$ovaoptions = Get-OvfConfiguration -ovf C:\temp\vRealize-Operations-Manager-Appliance-18.104.22.16857692_OVF10-sha1.ova
- Output the object
$ovaoptions.ToHashTable() | ft -AutoSize
- Now we prepare the script to build the OVA. Update lines 4, 6, 11-33, 36, and 38 to match your environment.
- Run the script as many times as needed, in my case I will run it 4 times to create a Continously Available environment. More details on that configuration will be in the next post.
You can find a copy of this script, with prompts at my VROps Gist.