Upgrading

In this post I will go over upgrading my 8.x vRA appliance to 8.6. As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.6. Instructions can be found here. The upgrade already includes the latest Product Support Pack so an update to the Product Support Pack is not required. Downloading the Upgrade Binaries To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware) ...

I was recently going through a vCenter upgrade and got stuck at an error Exception occurred in postinstallHook. I tried reverting from snapshot and trying again but I ran through the same issue. The issue in my case was that the catalina.properties had the wrong permissions. The fix was to change the permissions to perfcharts:cis and then resuming the update in the VAMI interface. The catalina.properties is located /usr/lib/vmware-perfcharts/tc-instance/conf/catalina.properties. The command to fix it is ...

I recently upgraded my vCenter to 7.0.3 18700403 and I noticed that when I went to Lifecycle Manager I was welcomed with this error. “Authentication failed, Lifecycle Manager server could not be contacted.” Im not aware of a fix for this issue however using the administrator@vsphere.local seems to be working.

In this guide I will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.6 release. The release notes can be found here The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section Go to settings -> System Upgrade ...

In this post I will go over upgrading my 8.x vRA appliance to 8.5. As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.4.1. Instructions can be found here. You will also need to apply the latest Product Support Pack (version 8.4.1.4). The instructions can be found here. Downloading the vRA 8.5 Upgrade Binaries To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware) ...

In this guide I will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.4.1 Patch 1 release. The release notes can be found here. If you are not yet on 8.4.1.1, I covered upgrading vRSLCM to 8.4.1.1 in a previous post. The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section ...

In this guide I will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.4 release. The release notes can be found here The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section Go to settings -> System Upgrade ...

In this post I will go over upgrading my 8.x vRA appliance to 8.4. As a pre requirement we do need to have vRSLCM (vRealize Lifecycle Manager) upgraded to 8.4. Instructions can be found here Adding the Upgrade Binary in vRSLCM To get started we can go to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> Binary Mapping. (If you haven’t added your My VMware credentials you will need to do that first by going to vRealize Lifecycle Manager -> Lifecycle Operations -> Settings -> My VMware) ...

In this guide I will go over the steps of getting an existing 8.x vRSLCM appliance upgraded to the latest 8.4 release. The release notes can be found here The first step is to lo in to vRealize Suite Lifecycle Manager under the Lifecycle Operations section Go to settings -> System Upgrade ...

If you are like me and you tried to perform an upgrade of vIDM 3.3.x to 3.3.4 you were most likely greeted by no network connectivity after upgrade with the following screen: If you made a backup of the network configuration this is where we would restore it. If not we can perform it manually by running /opt/vmware/share/vami/vami_config_net Press 6 and go through the screens to configure the ip ...