VI 3.5 Update 1 upgrade experiences

[jasonboche]

I upgraded VirtualCenter 2.5.0 to 2.5 Update 1 today (using SQL Server 2005 SP2 back end).

Observations:

1. The license server installation/upgrade is still not called as part of the autorun.exe as all other VI components are (VC server, VC client, VC Update Manager, VMware Converter for VC). The license server installation/upgrade must still be performed as a separate step at the very beginning.

2. SQL back end users are no longer allowed to use the SQL Server 2003 ODBC driver packaged with Windows Server. You must now download and use the SQL Native Client driver and rebuild your DSNs using this driver. Available at: http://www.microsoft.com/downloads/details.aspx?FamilyId=50b97994-8453-4998-8226-fa42ec403d17&Displa...

3. VMware took the feedback of all the database upgrade issues being had with the release of VC2.5.0. Helpful screens now guide us to the correct database upgrade permissions referencing the applicable VMware KB articles. Furthermore, if by chance you grant your VirtualCenter SQL account the sysadmin role to SQL server, the upgrade picks up on this and presents you with a warning message that a new parallel set of database tables will be created rather than upgrading the existing infrastructure. Failure to correct this situation will essentiall result in losing your datacenter after the upgrade is complete.

4. Database upgrade completed without any issues.

5. Once completed, Help|About reflects VIC and VirtualCenter versions 2.5.0 build 84767. Why not 2.5.1? Why is the incorrect build number of 84767 shown instead of what's listed on VMware's website build 84782

[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

[admin]

Hi Jason,

I get 6201bd703a932750ca2b4b9fe68996d8 for the download VMware-VIMSetup-2.5.0-84782.zip too. Tried it 3 times, same result each time. My download is also coming from download2.vmware.com.

Cheers,

Alex

[jasonboche]

Hi Jason,

I get 6201bd703a932750ca2b4b9fe68996d8 for the download VMware-VIMSetup-2.5.0-84782.zip too. Tried it 3 times, same result each time. My download is also coming from download2.vmware.com.

Cheers,

Alex

Thank you Alex. That is very helpful! You are getting the same incorrect MD5SUM value that I have been getting for the VirtualCenter .ZIP file.

Jas

[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

[NathalieMarshal]

I upgraded one of our test ESX hosts using update manager and although it is all up and everything I can't migrate any hosts to it, or enable HA on it... I take it I need to rebuild to 3.5? I have no idea that this was a U1 install, just saw that there were updates waiting and foolishly trusted them!

If I rebuild the host, update manager will pick up these updates again. How will we know when we can install them safely??

Nathalie

[sunchaser]

Hi everybody,

have you checked the Virtual Center ISO image, too? maybe it contains the correct build...

[wally]

nope, the one I downloaded contains the same 84767 version, although the md5sum was ok.

[RParker]

> Can someone from VMware please advise when the correct download is available for Update 1 (for ESX 3.5 and VC) - and also when the bugs have been fixed?

The builds ARE correct, they were correct the whole time actually, the descrepancy was the website showed the installation build not the actual build of the product. 84767 is the build for VC and 82663 is the correct build foe ESX update 1.

As far as bugs is concerned, I updated almost immediately for our entire enterprise, and I don't see any bugs. In fact I see many improvements. Like the VC refresh showing many VM's, it would hang while it was displaying the VM list, now it shows fine.

This is the best build to date, and now they have officially supported jumbo frames and improved the network perofrmance, we are good.

what kind of "bugs" do you see?

[RParker]

> nope, the one I downloaded contains the same 84767 version, although the md5sum was ok.

84767 IS the correct version, 84782 is the installer used to INSTALL the product.

[dmadden]

RParker is correct. The build numbers are right. The VC build number displayed on the download page is for the unified installer and not VirtualCenter.

The md5sum for the zip file is not correct.

[NathalieMarshal]

I see the bugs I explained about above - that I can't migrate any VM's to the one machine I upgraded. Hence I'm not happy applying the upgrades to any other machines until I know the problem is fixed. I'm also worried that when I rebuild the ESX server back to 3.5 update manager is going to pick up all the updates again and I don't want to install them but will want to install others. Hence I am keen that this is fixed soon!

[jasonboche]

The md5sum for the zip file is not correct.

Based on my email discussions with VMware, last night a VMware employee downloaded the .ZIP file and the MD5SUM value matched what is published on the website.

Thus far it has been confirmed that when Alex (Mittell) or myself downloads the .ZIP file, the MD5SUM value does not match what is published on the website.

My biggest concern is that 2 different .ZIP files are being downloaded from the VMware website evidenced by the 2 different MD5SUM values we are seeing. It's a version control issue. How many people have downloaded the .ZIP file since the release on 4/10/08 and which version of the .ZIP file did each person get? Which version is the correct version?

So far it has not been proven that there is any correlation between the different .ZIP files/MD5SUM values and the other issues being reported such as VIC client crashing, complaining about a vpx log file being in use, inability to vmotion, inability to view remote console, inability to deploy a template with a customization, inability to enable the Update Manager plugin, etc. For now I would treat those as separate issues.

Jason Boche

VMware Communities User Moderator

[FrancWest]

Hi,

same here. Just downloaded it 5 minutes ago and has the wrong (6201BD703A932750CA2B4B9FE68996D8) checksum. It was downloaded from download2.

Franc.

[kellino]

I'm wondering if either proxies or content delivery systems such as Akamai (not sure what VMWare uses) could be reponsible?

In other words maybe VMWare did correct the download, but some points in the distribution chain (including proxy servers) are still serving the original version.

Just pure specualtion on my part...

[NathalieMarshal]

I updated via updte manager just one ESX server and now I can't migrate

any VM's to that ESX. I'm not prepared to upgrade the others until I can

understand why I have this problem. I plan to rebuild the ESX server

tomorrow.

Nathalie Marshall - I.S. Infrastructure Support x8427

RParker <communities-emailer@vmware.com>

14/04/2008 15:15

To

Nathalie <nathalie.marshall@honda-eu.com>

cc

Subject

http://VI3 v3.5 New Features New message: "VI 3.5 Update 1 upgrade experiences"

Nathalie,

A new message was posted in the thread "VI 3.5 Update 1 upgrade

experiences":

http://communities.vmware.com/message/914254

Author : RParker

Profile : http://communities.vmware.com/people/RParker

Message:

[sbeaver]

Edit your baseline or create a new one with just the updates that you want

[kellino]

Very confused.....

We applied the VC update as a ZIP file. I can confirm that we are suddenly experiencing all the symptoms (no vMotion, VC crashes, etc.). When I do an MD5 on the zip I get:

9146AA4743C0A56E37921F62FB898A64

...which is the same MD5 listed on the download page.

If the problem has been corrected why would one be experiencing the symptoms when the MD5 matches?

[jpoling]

Jason,

I was dumb - After my initial download and install, I dowloaded the ZIP a second time because of the issues raised in this post. Well, I overwrote my initial dowloaded zip file. . .

THe download I ahve now, I ahve not extracted and installed, but the MD5SUM is:

6201bd703a932750ca2b4b9fe68996d8 VMware-VIMSetup-2.5.0-84782.zip

Jeff

[doubleH]

I upgraded from 2.0.2 u1 to 2.5.0 u1 last night (using the zip file with the wrong md5sum) and everything is working perfectly. no problems with vmotion (hosts are still at 3.0.2), able to deploy vm's from customized templates, vi client is not crashing, no issues with remote console connections, i did not install any plugins because i haven't had a chance to experiement with the added functionality yet.

If you found this or any other post helpful please consider the use of the Helpfull/Correct buttons to award points

[jasonboche]

Very confused.....

We applied the VC update as a ZIP file. I can confirm that we are suddenly experiencing all the symptoms (no vMotion, VC crashes, etc.). When I do an MD5 on the zip I get:

9146AA4743C0A56E37921F62FB898A64

...which is the same MD5 listed on the download page.

That is also the same MD5SUM that the VMware employee was getting last night which is different than what Mittell and myself are getting.

If the problem has been corrected why would one be experiencing the symptoms when the MD5 matches?

We will need to get clarification from VMware on how to proceed. Still waiting the news on what is actually happening. Hopefully today.

[i]Jason Boche[/i]

[VMware Communities User Moderator|http://communities.vmware.com/docs/DOC-2444][/i]

[kellino]

My confusion is growing...

I downloaded the VC update on Friday and again just minutes ago (around 12:30 EDT Monday).

After applying the update that was downloaded on Friday we suddently have all the symptoms (no vMotion, VI client crashes, etc.) and the VI client reports the build as being 84767.

Here is the results of running MD5 against BOTH downloads:

H:\md5&gt;md5 h:\vmware\VMware-VIMSetup-2.5.0-84782.zip
9146AA4743C0A56E37921F62FB898A64 h:\vmware\VMware-VIMSetup-2.5.0-84782.zip
H:\md5&gt;md5 h:\vmware\VMware-VIMSetup-2.5.0-84782_new.zip
9146AA4743C0A56E37921F62FB898A64 h:\vmware\VMware-VIMSetup-2.5.0-84782_new.zip

In other words the following are true:

• the MD5 for either download matches the MD5 posted on the download page.

• immedaitely after applying the update we experience the symptoms

Am I missing something? If not, how do we get obtain the "correct" zip to restore lost functionality?

Thanks!

[dconvery]

I just downloaded the zip. I used md5sums.exe to run and got the posted md5:

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+

Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/

Type c:\software\utils\md5sums.exe -h for help

/ filename MD5 sum

-

---

VMware-VIMSetup-2.5.0-84782.zip 100% 9146aa4743c0a56e37921f62fb898a64

The download link was http://download2.vmware.com/software/vi/VMware-VIMSetup-2.5.0-84782.zip?HashKey=.