This is a multipart blog post detailing the installation and configuration of the new vRealize Operations Manager product.
Unlike the previous vCenter Operations Manager release this is a single VM only product and doesn’t rely on the two node UI and Analytics VM vAPP.
Now deploying the appliance is pretty straight forward, in fact if you have already deployed an OVA file before you can deploy vROPS as well but for those of you who haven’t deployed an OVA \ vApp before please continue on.
Click Browse and choose the location of the OVA file. Click Next
Click Accept, click Next
Choose your Name and Location
Now this is one of the changes between vROPS 6 and vCOPS 5, in the previous version of vCenter Operations Manager you only had three choices for your deployment size: Small, Medium and Large.
With vROPS 6 you still have the options of Small, Medium and Large but now you also have the options of Remote Collector (Standard), Remote Collector (Large) and Extra Small.
Once you have decided on your configuration option click Next
Click the Cluster, click Next
Choose your Storage, click Next
Choose the disk format, in a production environment I would always suggest a thick provisioned disk but in my home lab I have gone for the thin provisioned option. Click Next
One of the differences between vCOPS and vROPS is that the newer vROPS doesn’t require you to have an IP Pool configured and associated with your Destination Network, the first time you try and start up the vCOPS vApp you would be presented with the following
The above message is presented when you try and start up the old vCOPS vApp the first time and you haven’t configured an IP Pool and assigned it to a network.
Enter your details and click Next
The VM powering up for the first time.
Appliance up and running, ready to connect to.
The Initial Setup screen.
In the next post I will detail the differences between the New Installation and Express Installation choices.