In previous posts I have demonstrated the installation and initial configuration for the vRealize Operations Manager 6 installation. At the end of the last post we were left at the log on screen to continue the configuration.
Log in with the admin user and password and let’s continue after the break to configure vRealize Operations Manager.
Accept the agreement and click Next
Enter your product key, click Next
Please note the following with regards to licensing – vRealize Operations Manager 6.0 allows customers to install multiple Advanced and Enterprise editions in the same vRealize Operations Manager deployment. This enhancement in 6.0 enables customers to deploy a-la-carte and suite licenses together.
License counting for individual license keys is handled via licensing groups – a feature that is introduced in 6.0. You can mix editions or licensing models in one of the following ways:
- Customers can deploy vCloud Suite Standard, vSphere with Operations Management, and vRealize Operations Standard together in one deployment.
- Customers can deploy vCloud Suite Advanced or Enterprise, vSphere with Operations Management Advanced, vRealize Operations Insight, and vRealize Operations Advanced or Enterprise in one deployment.
- Note that customers cannot deploy a Standard edition license with either an Advanced or Enterprise license in the same deployment.
Next we are prompted to install the vCenter Server (Solutions)
We have two adapters that we need to configure for the vCenter Solution, the standard adapter allows you to retrieve the data from vCenter and the vCenter Python adapter allows you to send commands to the vCenter.
I chose you use a service account that has permissions to the entire vCenter stack. Once you have entered all the required information click Test Connection
Click OK and then click Save Settings
Next I configured the Python adapter, go through the same test and once happy click Save Settings and then click Next
Instead of sticking with the default I decided to Overcommit both CPU and Memory, other then that I left the rest of the settings as they came out of the box. Click Next
Even after a couple of minutes you can see that it’s picked up an issue with my configuration, something to look in to over the next couple of days
Q. So after migrating to vRO 6… and unregistering vCOPS 5.8.x, what about the vsphere web-client badges … were did they go? Are they not supported?
I have the same question as Jeff asked December 31st.
You can reference the below posts for the answer
Found from the VM community post: