VMTN

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

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.

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

We've confirmed that the download issues have been resolved. We've posted a longer statement on this new thread:

http://communities.vmware.com/thread/139468

As this thread is getting long, let's take our discussion on the download over there.

Thanks again for all the help.

GOOD NEWS! GOOD NEWS!

Since the begining of this ordeal on saturday we downloaded the zip and had all kinds of problems with our upgrade.  We had the VIC crashing with various error dialogs and the infamous:

"the process cannot access the file "c:\documents and settings\administrator\local settings\application data\vmware\xpx\viclient-0.log  because it is being used by another process" error.

Well even uninstalling the VIC and installing the good MD5 hash DID NOT  fix these issues.  We also have two other machines that we installed the VIC on and have no problems. But the only difference was that those machines do not have plugins installed. So this got me thinking about someone else here that had uninstalled the plugins.

So I just uninstalled the update manager and the converter plugin and VIC and did a reinstall (using existing db) then installed the plugins again.  WOW so far I can move around like i should and nothing crashes or popups and no more viclient.log files in use. I can click all around and select different servers and vm's without crashes....

I think the update doesnt like it when the update manger and converter plugins where installed. I am going to keep playing around to see if this holds true. Its been good for 10minutes, before I couldnt last more than a minute!

Yep, you are 100% right, We also had problem when the plugin where installed.

1) unistall everything except Virtualcenter server

2) Install update + client + plugins

Ps. what are your versions of the plugins after the upgrade?

- VMware Converter Enterprise: 4.0.0

- VMware Update Manager Extention 1.0

Same versions as you just mentioned.....

• VMware Converter Enterprise: 4.0.0

• VMware Update Manager Extention 1.0

chicagom wrote:

bq.

Yep, you are 100% right, We also had problem when the plugin where installed.
1) unistall everything except Virtualcenter server
2) Install update + client + plugins

bq. Ps. what are your versions of the plugins after the upgrade?

• VMware Converter Enterprise: 4.0.0* VMware Update Manager Extention 1.0

You'd think the installer app would catch this itself and uninstall the bits beforehand, but clearly it is very important to do a clean install this time around.

Just to let everyone know, I updated one of my ESX hosts through Update Manager to 3.5.0 - 82663, without any problems.  This is without updating the VC (its still at 2.5.0 - 64192).  I like to live on the edge ]:).

By my reckoning, if VMware thought that upgrading the ESX hosts to this level without upgrading VC was incompatible, then they wouldn't suggest it through the Update Manager.  Or am I giving them too much credit?  With the release notes and everyones comments here (thanks everyone), it doesn't sound like the update to VC is very compelling.

Its a bit of a disappointment that the VC upgrade is still a full uninstall/re-install.  Who would have thought that upgrading a whole ESX OS would be so much easier (now that we have UM), than a mere windows app upgrade??? 

Hopefully VMware have realized that a server component like this, shouldn't be written in .NET; and are in the process of rebuilding it in something more cross-platform, more stable and more maintainable   Guess I should keep that rant  for another blog post.

However, I won't be updating the rest of my host servers until the problem that jasonboche highlighted, with dead templates, gets resolved.

I love the ESX platform, however in my opinion, VC still isn't a great enterprise solution.

Forbes Guthrie

http://www.vmreference.com

Jason, few questions.

I have experienced most of the issues people complaining about.

Regarding your installation installations

1) If my VC server is the same server as my license server, should I install license server part first, then reboot and proceed with VC install?

2) I am using SQL2000 backend, still need to download this MS patch?

3) Install all the clients/converters/plug-ins last after reboot?

Thanks in advance

I want to verify something here.... Do we really need to install and update manuall for the license server?

Because we installed the VC update just running the main install and have not had any problems at all. We assumed it was automatically upgraded.