Having installed vRealize Operations Manager a couple of times recently in my home lab I came across an error that initially caused me to rip out the lab and build it again changing the way my networking was being done. Why? Well the following error was being presented to me when I logged in to the Operations Manager console.
In a home lab environment this confused me because, well it’s a home lab environment and there wasn’t a lot going on (I had 5 VMs running across three hosts at the time).
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.
Playing around in my home lab over the last couple of months I carried out an installation of vCenter Operations Manager (vCOPS), had a look around it and then promptly deleted the vApp after a month or so.
Spring forward a couple of months and going through the new vROPS 6 installation and going through the vCenter registration process with vROPS 6 I received the following error message.
Because this installation isn’t actually replacing an existing instance I decided against overriding the existing registration and decided to go with a de-registration, thereby allowing a fresh registration of vROPS 6.
Using the MOB incorrectly can lead to you breaking your vCenter server so please do so carefully.
In the previous blog post I left you at the Getting Started vRealize Operations Manager screen.
In this blog post I will be going through both the Express and New Installations, continue reading for more information.
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.