Category : VRealize Orchestrator
Written by Christopher Lewis on November 4, 2016 .
OK so you’ve finally deployed vRealize Automation 7.x and you’re pretty chuffed with yourself because it only two 2 rollbacks on the Windows VMs, a new VA deployment and some on the fly configuration tweaks to get it working… You’re #Awesome.
You’re following VMware best practice and you have your embedded vRealize Orchestrator instance on your vRealize Automation Virtual Appliance(s). You #RockThisWorld
You’re on a role. but now you now have to install a new plugin for vRealize Orchestrator (lets say for Infoblox IPAM or F5 LTM), so you try https://vra.fqdn:8281/vco like you did on the vRO 6 appliance but get a “this site cannot be reached” message. You then remember, configuration was on 8283, so you try https://vra.fqdn:8283/vco-confg again with no luck and a “this site cannot be reached” message.
- Operating a Private Cloud - Part 3: Creating a Pricing Card in VMware Aria Automation
- Operating a Private Cloud - Part 2: Creating a Pricing Card in VMware Aria Operations
- Operating a Private Cloud - Part 1: Understanding Pricing Cards in VMware Aria
- Zero2Hero - Using Aria Automation to Deploy Multiple Machines with Multiple Disks - Part 5
- Zero2Hero - Using Aria Automation to Deploy Multiple Machines with Multiple Disks - Part 4