VMTN

I am told that the problem with the build has been corrected.  Based on what I see on the download page for VI3, it appears the build # for VC 2.5 Update1 is indeed correct on the website, however, the actual bits were not.  If you download now, you should see build 84782 in Help|About.  Try it and let me know if it works.

Thanks.

Badsah

---

Badsah Mukherji

Senior Community Manager, VMware Communities

So, for this build discrepancy. . .I have 84767. . .I need to do a reinstall after downloading the bits again?

If that's true, do I ahve to completely uninstall VC and do a fresh install? That will be painful as I don't have the luxury of a lab. . . (kind of knew I should wait before jumping on the upgrade. . .but I've been waiting to go to 3.5 until update1 came out. . .ugh)

Jeff

Jason,

Thanks for the update. . .I was actually going to try a reinstall tonight. . .based on your experience I guess I will start enjoying my weekend instead

Hopefully VMware will have an answer for this soon. . .

Jeff

I downloaded VMware-VIMSetup-2.5.0-84782.zip at 6.45pm EST today 4/11/08 and after install about box still shows 84767 build

Also I had to uninstall and reinstall update manager before it appeared in installed tab of plugin screen. Uninstalling and installing Converter  did not help - it is still listed on available tab but not on installed tab. When I installed standalone client on my workstation plugin screen offered to download both plugins and installed them after downloading

I think this is all a joke. Howcome simple things like the incidents reported on this thread cannot be identified before being released? These simple problems are happening too regularly.... and everyone seems to just put up with it.

My opinion of VMware is that it is a fantastic product.... but the simplest of issues that shouldn't be a problem at all just keep happening.

I really feel sorry for the keen enthusiasts who jump straight in and apply these major changes to their environment before waiting for the "correct download" to be released.

These updates are tested internally within VMware right??? Beta testers etc??? Where is the QA? Download site QA??

I realise these forums are for constructive comments - that's why I'd be keen in finding out if there is anyway for other users of this forum can also test the updates before the release? I'd be keen. Are there update Beta's?  For some of us with testing environments it's always an option....

OK - that's enough of my 2 cents worth

Message was edited by: java_cat33

I have downloaded the "updated version" and installed Iam also seeing 83767 build

Could we still be downloading a cached version?

I downloaded the zip and cdrom copies, it was a fresh install on a test pc

mkh

> My opinion of VMware is that it is a fantastic product.... but the simplest of issues that shouldn't be a problem at all just keep happening

I agree, VM Ware needs SME (Subject Matter Experts).

> These updates are tested internally within VMware right??? Beta testers etc??? Where is the QA? Download site QA??

Would  be nice to know who THEY are, they need to the forum experts (like moderators and other chosen people) to be the Forum Integrators, so they can test the products and CONFIRM the product release.  The builds are just one problem, but they seem to ignore our requests for enhancements (a la 64-bit) and other features they could do better (such as VIC not retaining settings -- windows size, sorting, etc -- between runs).  There are MANY things that can be done, but they seem to ignore this group.  If we have the knowledge and can help, why not let some of the people on here be involved in the process.

> The install ran with no problems however the build version for the license server is still 10.8. I've restarted the services etc which made no difference.

Again with the build descrepancy... this is rediculous.  How can a build be one thing, yet INSTALL be another?  That makes no sense whatsoever.  I noticed the same thing, despite the program notifying me that "an upgrade of the license server would be performed"

> After the upgrade, I'm unable to deploy any Windows templates with a customization. "The virtualcenter server is unable to decrypt passwords stored in the customization specification." This one hurts.

Well this one isn't new, This happened with VC 2.0 -> 2.5 also.  I forgot about it until you posted it.. I just deployed a VM last night too, and I forgot to check... I get comfortable with everything working, every upgrade is like a do over.... -sigh-

We need to talk to someone at VM Ware... at least for a few faithful, they could entrust with some QA testing before the product is released to the public.

I have been told the following:

84767 is the right build for VC. 84782 is the VIM Installer build. If you look at the release notes:

http://www.vmware.com/support/vi3/doc/vi3_esx35u1_vc25u1_rel_notes.html

you'll see that the build numbers are:

VMware Infrastructure Management Installer | 10 APR 2008 | Build 84782

VirtualCenter 2.5 Update 1 | 10 APR 2008 | Build 84767

Program management looked into this yesterday when we forwarded them this thread, but their answer didn't get back out all the way here to the community. That was a process issue -- sorry. We'll also attempt in the future to overdocument and overexplain when build numbers don't all match like this.

If I've missed something or if there are still issues, please let us know.