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 the previous post we installed and configured access to vCenter 5.5, it’s great that we have vCenter installed but with no datacenter or Hosts configured we aren’t going to be doing too much with our new installation so what we need to do is add a new datacenter and a host to allow us to work with the vSphere suite.
Launch the Windows based vCenter Client
This post will detail all the steps required to install vCenter 5.5a on to a Windows 2012R2 guest machine, I should add that at the time of writing 2012R2 isn’t on the supported OS list and that there is an additional step that needs to be done to ensure that the installation succeeds first time.
You will need to get a copy of OCSetup.exe because for some insane reason Microsoft dropped the use of it in Windows 2012R2 (it’s present in 2012). As a side note you can also use a copy of the file from Windows 2008R2 if you don’t have 2012 available. Once you have a copy place it in the C:\Windows\System32 folder.
After a recent upgrade to our vCenter 5.1 infrastructure we discovered that we were getting the following error when trying to use the log browser component of the web client.
Having tried a number fixes from the usual sources (Derek Seamans excellent blog) none of them seemed to resolve the issue, a reboot of the infrastructure, a re-install of the Web Client all resulted in the same error cropping up. In the end it took the eyes of a VMware BCS Engineer to have a look at our ca_certificates.crt file and discover some white space present.
The strange thing here is that there wasn’t any date change on the file since the initial deployment back last year and we had no issues with the log browser working before the upgrade.
If you experience any issues with the log browser it may be worth checking the C:\ProgramData\VMware\SSL\ca_certificates(_2).crt file to make sure that there isn’t any white space present in the file first.