ESX Build Differnet after update?...

[thesixuk]

Can anyone help me with a strange problem?

I have two ESX 3.5 Servers in a cluster, ESX1 & ESX2

Today I updated the version of ESX on both servers using the latest installation CD (VMware ESX 3.5 Update 2, build: 110268)

After the installation I used Update Manager in Virtual Center to rescan for updates.

ESX1 reported itself as compliant and requiring no updates

ESX2 reported itself needing 14 updates.

I remediated ESX2 and now it's build number has changed to 120512

No mater how many times I re-scan ESX1 it tells me that it doesn't require any updates yet it's build seems to be earlier than the updated ESX2

Soooo:

Is this right?

Is there any way for me to get the builds to match?

Is it important to have your builds matching in a Cluster?

Cheers

Niels

[chill]

It seems like it's not being read properly by Virtual Centre. Try removing it from inventory and then readd it, then scan it again.

If that doesn't work, double check the update levels in the service console by typing in:

esxupdate -l query

This will tell you exactly what level you are at.

Do your builds have to be the same in a cluster? No, but it's always a best practice to have all ESX servers at the same consistent level for troubleshooting purposes.

If you find this information helpful or correct, please consider awarding points.