With the release yesterday of vCenter 6.0.0b I decided to do a quick post on how to patch your VCSA appliance.
Please download VCSA patch from here.
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.
In a recent post I showed you how to update your hosts from 5.1 to 5.1u1, whilst it was a nice and simple exercise you mustn’t forget that you also need to update your vCenter server (or in this case appliance).
Following the steps below you will now update your vCSA appliance from 5.1 to 5.1u1.
1. Take a snapshot of your vCSA VM, you want to do this in case you need to roll back the update for any reason.
2. Point your browser to https://<vcsa-ip-address>:5480 This will give you access to the vCSA administrator console.
In my old lab I ran a lot of Windows 2008 R2 based infrastructure, not only was I running a fully deployed Active Directory Domain but I also had SQL 2008 R2 and SCCM 2007 but I was also running vCenter on 2008R2 as well, the main reason for this was due to the limitations that were in the original vCSA based on ESXi 5.0.
In Home Lab 2013 I decided to upgrade not just the physical side but also the virtual and that meant looking at some of my existing infrastructure and deciding on whether to keep it or upgrade.
Gone is the 2008 R2 based Active Directory Domain, in it’s place I am now running a 2012 Active Directory Domain Controller (no in place upgrade, I just deleted and started from scratch), that also meant that my SCCM 2007 infrastructure went (one of the technologies that I seem to get stuck with with every job so glad it’s gone really
), also gone is the vCenter server that was running on 2008R2, I had played around with installing it onto 2012 and whilst I managed to get it to work (you have to delete a service dependency) I wanted to ensure that all of my virtual infrastructure was actually properly supported so that meant looking at the vCSA.
With the release of vSphere 5.1 there was obviously the additional requirements for the SSO and Inventory services to be installed prior to installing vCenter, with the vCSA 5.1 release this comes bundled up as part of the OVF and makes the installation and configuration very simple (those of you who have installed vCenter 5.1 know that SSO can be a little bit ‘temperamental’).