Updating esxupdate database

So I decided to take the risk to see if it would still work after the upgrade had completed.This View Composer incompatibility again seems to be a 32/64-bit issue.The upgrade of v Center itself went relatively smoothly.

The first concerns how you want to handle the update of the v Center Agent on your ESX hosts.

I chose to select the automatic upgrade, as I didn’t much like the idea of them being “disconnected” during any upgrade.

But I noticed when I upgraded VUM, that Database Information page showed a path to the Sys WOW64 directory.

This is the location where you can run the DSN Administrator for 32-bit on a 64-bit copy of Windows 2008 R2.

Just out of blue started receiving the following error after trying to scan my ESXi hosts with baseline group: "The host returns esxup error code:99.

In terms of the order – you MUST get started with the upgrade of v Center – it’s impossible to upgrade ESX 4.0-U2 to ESX 4.1 without doing this before hand.I’ve never really liked this method of upgrading – after once accidentally canceling an upgrade – which then broke the older Vi client.My advice is once you have embarked on the upgrade, don’t cancel it!After the upgrade it appears that VMware migrates your 32-bit DSN into a 64-bit one. So if you want to modify your DSN for v Center and VUM you will need to run to separate utilities.I was surprised to see that the v Sphere Client didn’t offer me the chance to install or update the “Host Update Utility”.I am trying to upgrade an ESXi 4.1 host to version 5.1 or 5.5. Errno - 5 Description - The format of the metadata is invalid.

Tags: , ,