I’ve been waiting for the 6.1 release, so I’m glad to see the announcement on my inbox this morning.
I shared the process to update from version 6.0 to version 6.0.1 here. The process to update or upgrade from 6.0.x to 6.1 is the same, so kindly review the above. No need to fill the Internet with duplicate info 🙂
From the official Release Notes:
- If you have customized the content that vRealize Operations Manager provides such as alerts, symptoms, recommendations, and policies, and you want to install content updates, a best practice is to clone the content before performing the upgrade. In this way, you can select the option to reset out-of-the-box content when you install the software update, and the update will provide new content without overwriting customized content.
The above is the reason why I advise customer to always clone. You then prefix the cloned object with your company name. If the object is a personal object, then prefix it with your initial. If your company name is Super Duper Transparent Inc, then prefix the object with SDT will help you quickly identify them in the sea of objects. I found it useful as I can sort by name. For the personal object, I prefix all mine with e1, so other users will not be confused.
Tomas Baublys corrected me that I missed the Linux OS update. He has written an excellent guide here.
As shared here, the upgrade is identical. So I will just provide additional screenshots here. The first step is to upload the .pak file. It can take a few minutes.
Once it is uploaded, click Next to proceed.
The upgrade will automatically log off (as the system is down, obviously 🙂 ). It takes minutes, so go and get a cup of coffee 🙂 You can review the progress from the System Status and Software Update links on the left side of the screen. Below is the System Status menu.
…. and here is the Software Update screen.
Back from your coffee break? You should see something like this at the end.
The Release Notes states that “After an upgrade, the vSphere Web client might not display Health, Risk, and Efficiency badges for a machine that vRealize Operations Manager is monitoring. If that happens, use the Solutions page in vRealize Operations Manager to re-register vRealize Operations Manager with your vCenter Server”.
From the screenshot above, you know it did not happen to me. It’s happily collecting already.
Once upgraded, it’s now ready to get visibility inside the Guest OS! I’ve written some articles to help you started: