For those that haven’t heard, vCenter Operations (known better as vC Ops) has been not only updated but renamed. It’s new name is vRealize Operations (or, probably, vR Ops) and it is officially version 6.0. Previously the system was deployed in a vApp containing a UI VM and an Analytics VM. The new systems incorporates a roles for the VMs such as Master, Master Replica, Data and Remote Collecter.
However, this blog post isn’t to focus on what’s been updated. It’s to take a look at making the deployment a little easier since most installs will have at least two nodes. If you would like some further information on the update, please check out VMware’s website: vRealize Operations
After running the script below, you’ll find an output similar to the following:
Before getting to the script, lets cover some of the assumptions and requirements made in the script:
- The OVA has already been downloaded and is placed somewhere available to the system running the script. (Example: local disk, SMB or DFS share, etc.)
- The VM is being placed in a resource pool.
- The local system is able to successfully run and resolve the VM name via Resolve-DnsName cmdlet which is available in PowerShell v4.
- The subnet being used is a /24 or 255.255.255.0. This is easily modified on line 126.
- The VLAN ID is based on the third octet of the system’s IP address. This information is set on line 128 and the portgroup is set on line 133.
- The gateway ends with ‘.254’. This is easily modified on line 129.
- DNS should be modified to match your environment which is based on line 130.
Note: this was a script that worked in my environment. There is no warranty or support with this script, please use at your own risk.