jasonboche
Immortal
Immortal

VI 3.5 Update 1 upgrade experiences

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]

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
0 Kudos
157 Replies
wally
Enthusiast
Enthusiast

Besides the 3 extra files the file "vpx\VMware VirtualCenter Server.msi" also seems to be different. After extracting the msi and running a diff I get the following output:

Binary files vpx\new\!Property and vpx\old\!Property differ

Binary files vpx\new\!_StringPool and vpx\old\!_StringPool differ

The first shows some additional info and seems to only concern some install dialog text, the 2nd one doesn't show additional info.

Since we currently don't have any problems (running VC2.5U1 (84767) with both esx 3.0.2 (63195) and 3.5u1 (82663) hosts I'm not planning any additional repair actions unless vmware support tells me to (opened an incident monday morning to clear up the buildnumbers puzzle).

typo edited by: wally

0 Kudos
olczak
Enthusiast
Enthusiast

Hi Guys,

Since I upgraded my VC 2.5 to 2.5 Update1 (with the correct MD5), I have a pb not described previously on this topic:

if the VitrualCenter service is restarted, all informations about processors are lost for all ESX (3.5 or 3.02) in the summary or in configuration/processor tabs and memory informations are lost in configuration/memory tab. So the cluster composed by these servers have 0 processor and 0 Ghz. To solve the pb, I have to disconnect and reconnect each ESX servers from the VirtualCenter...And informations are back. If the VirtualCenter service is restarted, information disappear again.....Everyone else got this problem?

0 Kudos
cryptonym
Enthusiast
Enthusiast

As of 10AM today, download2.vmware.com at 64.132.49.153 is still pumping out the wrong file, with the 6201... md5 sum. Come on vmware, get it fixed!

And while we wait... why does this keep popping into my head?

"Don't you love farce?

My fault I fear,

I thought that you'd want what I want,

Sorry my dear

But where are the clowns

Send in the clowns

Don't bother, they're here.

Isn't it rich, isn't it queer

Losing my timing this late in my career

But where are the clowns

there ought to be clowns

Well, maybe next year" - Stephen Sondheim

0 Kudos
kellino
Enthusiast
Enthusiast

I think VMWare may be at the mercy of Akamai to correct the caches that exist in the cloud.

0 Kudos
tlyczko
Enthusiast
Enthusiast

We need a comprehensive explanation from VMware:

1) What are the correct build numbers??

2) How to verify we have the correct files??

VMware messed this up, they need to continue working on making this right, and to announce loudly and clearly when it is made right.

Very shocking to read this kind of news, makes one wonder...

Thank you, Tom

0 Kudos
cryptonym
Enthusiast
Enthusiast

I believe the better approach is for them to take down the link until they resolve the distribution problem with Akamai. They are compounding the problem every minute they leave it up. As to the best "fix". Rename the file, and redistribute it through Akamai. No need to worry about "bad" cached files if the name changes and they point everyone to the new file.

They could post a "Sorry we messed up" message on the web page.

0 Kudos
BenConrad
Expert
Expert

I just opened a SR referencing this thread, I know some internal vmware employees know about this issue but wanted to get some clarity from support.

Here is what I have from them so far:

Hello Ben Conrad,

CORRECTION!!!

There are some areas that haven't been updated yet....Please download the ISO files as they don't have this issue.

Best regards,

.....

0 Kudos
beckhamk
Enthusiast
Enthusiast

Support seems to be taking a down turn with vmware on this one.... My company is starting to second guess their decision...

I sat on the phone saturday for 4-5 hours with this issue, only to have vmware tech support say lets take this up on monday at a specific time that we all agreed upon. Well yesterday, we sat around waiting for vmware tech to call us or email us and nothing. What kind of support is that?

0 Kudos
tlyczko
Enthusiast
Enthusiast

Appears to be a definite black eye here for VMware. Hope they understand this and start fixing things, etc.

0 Kudos
cryptonym
Enthusiast
Enthusiast

Official response from vm support:

"Please download the ISO file as that one +seems +to be correct...we are working on correcting this issue.

Let me know if that answers your question.

Looking forward to your response :smileygrin: "

I bolded the interesting wording on this, and will try it next.

I asked them to be proactive and pull the bad link, notify all users that have downloaded it so far, re-release it with a modified name for clarity, and post info on the web page. Of course, I expect nothing to happen.

Updated at 1PM EST. Just spoke with a manager in vm support. He assured me that this has been elevated internally at VMware, to his manager, and at least the level beyond that. Teams are working to resolve, but no real info was given. He seemed frustrated as well, and probably rightfully so, since they get to hear about it first hand. I was able to download the ISO version, and it's MD5 matched, so I uninstalled all of the "bad" versions, then reinstalled from the ISO. So far, so good.

0 Kudos
admin
Immortal
Immortal

We believe everyone should be able to access the correct bits now.

We have an ongoing ticket with Akamai to check at several edge IPs, but the best way to test a worldwide, distributed system is -- to test it in worldwide, distributed fashion.

Can a few folks try to download the zip file and confirm they are getting the right md5sum, and what IP you got it from? We appreciate the extra help before giving everybody the "all clear" signal at support and here on the community.

We'll start a new thread with an official statement once we confirm this, and I'm sure you may have some feedback for us in that thread. Many people internally are both aware of the situation and are reading these threads, so your comments and suggestions are not going by unnoticed.

John Troyer

VMware Communities

0 Kudos
tlyczko
Enthusiast
Enthusiast

Please provide a clear description of what the correct bits are -- what

build, contents, whatever people can use to verify for themselves --

otherwise this snafu will linger on...

Thank you, Tom

0 Kudos
shurik
Contributor
Contributor

I installed incorrect version of VC (upgrade from v3.5) but apart from some troubles with converter and updater plugins not being installed properly everything seems ok. About box shows version 767 for VI and VC. I have to say I do not have HA and VMotion so do not know if it is ok and I did not try creating/deleting/moving VMs but basic day to day finctions seems to be ok.

Now given that should I reinstall? I assume reinstall will require complete uninstall of VC server, client, updater and converter?

Thanks,

Alex

0 Kudos
jpoling
Enthusiast
Enthusiast

Just dowloaded it. Here is the info:

9146aa4743c0a56e37921f62fb898a64

Name: a1534.d.akamai.net

Addresses: 62.41.4.19, 62.41.4.65

Aliases: download2.vmware.com, download2.vmware.com.edgesuite.net

0 Kudos
admin
Immortal
Immortal

Sorry, Tom -- if you'd just studied the 131 messages in this thread over the last 4 days, you'd know exactly what I was talking about. Smiley Happy

This will all get detailed in the new thread, but as Jason says above, this is the correct zip file:

VMware-VIMSetup-2.5.0-84782.zip

456,277KB

Extracts to 55 files, 13 folders 552,462,397 bytes

MD5SUM: 9146aa4743c0a56e37921f62fb898a64

Note that the 84872 in the filename is the build of the installer, and the VC installed will have a build number of 84767. This is by design.

The incorrect file had an MD5SUM starting with 6. We identified the root cause and this is the only file that was affected.

0 Kudos
jasonboche
Immortal
Immortal

Thank you for the update John. I'll test the download from my home network where, in the past, I was always getting the incorrect version.

Jas






[i]Jason Boche[/i]

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

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
0 Kudos
tlyczko
Enthusiast
Enthusiast

That's why I commented -- perhaps there could be a sticky at the top --

saying GO HERE FOR THE CORRECT FILES AND MORE INFORMATION.

Thank you, Tom

0 Kudos
jasonboche
Immortal
Immortal

Download finished. I got the correct file.

C:\>nslookup download2.vmware.com

Non-authoritative answer:

Name: a1534.d.akamai.net

Addresses: 72.247.238.154, 72.247.238.144

Aliases: download2.vmware.com, download2.vmware.com.edgesuite.net

VMware-VIMSetup-2.5.0-84782.zip download streamed from IP address 72.247.238.144 at 2:44pm Central time

MD5SUM value: 9146aa4743c0a56e37921f62fb898a64

For comparison purposes, yesterday when I was getting the wrong file, it was coming from IP address 72.247.238.154






[i]Jason Boche[/i]

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

VCDX3 #34, VCDX4, VCDX5, VCAP4-DCA #14, VCAP4-DCD #35, VCAP5-DCD, VCPx4, vEXPERTx4, MCSEx3, MCSAx2, MCP, CCAx2, A+
0 Kudos
cryptonym
Enthusiast
Enthusiast

File is named: VMware-VIMSetup-2.5.0-84782.zip

Sucessfully downloaded with MD5 of 9146aa4743c0a56e37921f62fb898a64 from 64.132.49.146 a1534.d.akamai.net.

0 Kudos
chicagom
Contributor
Contributor

Is it now save to install the software from the ISO image?

If the MD5 key is the same as on the website!

Best Regards,

Geert

0 Kudos