Learn about the differences between the different upgrade paths for Update Manager and learn how to upgrade Update Manager.
- [Narrator] Now we're going to talk about upgrading Update Manager itself. Now this is a little difficult and a little confusing, so you got to pay attention here. So first off, there's two roads in our Upgrade path, okay? If you have Update Manager installed on a Windows box, meaning if you have a 6.0 or below implementation of Update Manager, or you have a 6.5 implementation of Update Manager that's installed on Windows, you have a completely different path than you would have if you had the vCenter Server Appliance, which is actually embedded in version 6.5 and beyond, into vCenter Server itself.
So, there's a big line in the sand, right? Especially at 6.0. 6.0 and Below you had to install Update Manager on a Windows device. You had to point to an external database if you were running even a mediocre size environment, anything over five hosts or 50 VMs. So that's where you were. That update process, if you're going to keep that Windows Server running Update Manager is completely different than if you have a 6.5 vCenter Server Appliance because Update Manager's already embedded in there.
Let's take a look at this process for a little bit. First off, the prerequisites. Before you do anything or even think about touching Update Manager, you need to upgrade the vCenter Server. Now, once you upgrade the vCenter Server to the new version, you're going to get a notification that there's some incompatibility because it is an older version of Update Manager. The two aren't compatible. So, what do you need to do? Well, first you need to take the Update Manager service and stop it.
Take your time, back up all the data you need to, but that service needs to be stopped so we can begin the upgrade process. If you are running your Microsoft Sequel External Database, you're fine. That will be rolled into the installation process, but if you're running an Oracle database, you're going to have to create a DSN connection for this new upgraded Update Manager. One of the other things you're going to need here is the Installation Media. Now, if you're going to migrate, and we'll show you how to do that later, you're going to need to add the VMware Migration Assistant software as well.
So, kill two birds with one stone. Get the new version of Update Manager and the VMware Migration Assistant if that's what you're doing. Okay, so let's look at the Upgrade Process for 6.0, keeping the Windows Server, or even 6.5 if you're keeping the Windows Server for Update Manager. We have the Update Manager software. We install that software on the server that is running Update Manager. We go to the Autorun.exe. This is a Script install, you click a lot of confirms, you click a lot of yeses, you choose your databases.
It's a very easy configuration. Next, we verify it. The last window, it's going to ask you to verify your configuration for this updated Update Manager. Last but not least, you need to go in and adjust the configuration. That's when you would go into your vCenter Server, your Update Manager itself. Go to the Administrative Pane, and take a look at your download repository schedule and all the different images that are installed. So, you would be cleaning up your Update Manager.
Now, let's take a look at the other side of the coin here. What does it look like for a vCenter Server Appliance upgrade with 6.5? In 6.5 like I've said before, Update Manager is actually embedded into the Appliance itself. So, if we were moving from 6.5 to 7, there's no work to do. vCenter Server Appliance also runs on a PostgreSQL database. So, we don't have any work. I don't have to set up that separate database and I'm not limited at all to five hosts or 50 VMs.
Now those of you who like this set up, I would imagine it's most of you, you don't want to waste a Windows Server license on an Update Manager. Why not just roll it into the vCenter Server Appliance? You can use the Migration Assistant, the one I told you to download. That's because I figured you were going to want to go this route. Now, last but not least, when, in the future, 7.0, 7.5 come out, the vCenter Server Appliance Update Manager will upgrade along with the VCSA automatically.
So those of you who are stuck on the Windows track and want to jump over to the vCenter Server Appliance track for Update Manager, this is how you do it. First, you will need to get that Migration Assistant and install it on the old Update Manager machine. That Windows machine that's running Update Manager, you need to get the Migration Assistant software installed there. Then, you need to take the vCSA installer package, copy the Migration Assistant folder to the old machine.
Then we're going to need to run the Migration Assistant exe from the Migration Assistant folder. Once you're done, keep that window open. You'll be prompted to go through a couple questions, nothing difficult, a couple confirmations, and then you will have moved or migrated from an Update Manager that relies on the Windows Operating System over to the brand new 6.5 Update Manager that's rolled into the vCenter Server Appliance.
- Manually performing ESXi host and virtual machine upgrades
- Configuring a custom download source for Update Manager
- Importing ESXi images
- Creating baselines or baseline groups
- Attaching baselines to vSphere objects
- Upgrading an ESXi host using vCenter Update Manager
- Upgrading VMware tools, VM hardware, and Update Manager
- Performing vCenter server upgrades