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]

[RParker]

Thanks. My boss thinks I have vmware blood... since I spend so much time on the servers. I got up early this AM to download the files (hoping that an earlier post proved they would be available today) and I was right. I kept hitting 'refresh' until they were online, then I downloaded. As soon as I came into work, first thing I did was VC, and then remediate my hosts...

The only depressing part, I have to wait 2 more months for another upgrade! ;(

[Jasemccarty]

We've got a little thing called Change Control that prohibits us from doing that.

Jase McCarty

http://www.jasemccarty.com

[RParker]

> VMware VirtualCenter Version Upgrade Support to VirtualCenter 2.5

VC 2.5 implies ALL updates and patches for 2.5, including update 1.

[RParker]

Yeah, we may get there, but for now there are only 2 VI admins... and since the other guy is on vacation, I thought I would leave him a little present.

I figure if I have to support them, and they break, I can fix them... I don't panic since the main cluster can vmotion the VM's.. the host is offline, so what's the worst that can happen a rebuild? That takes all of 10 minutes including configuration, but so far so good.

[java_cat33]

What's being released in 2 more months? Update 2??

[RParker]

> What's being released in 2 more months? Update 2??

well nothing official, just basing my guess on past history, they seem to release updates every 60 days or so.

[Jasemccarty]

Well, I'm the only VI guy here (for the most part).

We've got another guy that knows a little about it, and the Director is the one that set it up before I got here - he hasn't touched it in 3 years.

But our policies require Change Control approval before we can touch anything in production, or that could effect production.

After doing this for 15+ years on the civilian side, sometimes it is better to wait a few days.

Jase McCarty

http://www.jasemccarty.com

[RParker]

> After doing this for 15+ years on the civilian side, sometimes it is better to wait a few days.

Yeah I know -sigh- I just like to be up to date with the versions. Besides, someone has to be the first to test it... I know VM Ware has beta testers and QA testers, and I am sure they tested it before making it official.... but 2 weeks ago, they let the cat out of the bag early and tipped us all off, and the build numbers were the same, so these builds have been ready for 3 weeks...

I am confident they can fix issues by then....

[java_cat33]

Well I just went to install the latest license server (current version was 10.8), and the new version is 11.0. 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.

Looks like you need to remove the license server and install the new one?

[Badsah]

Hello, everyone, thank you for (once again) pointing out this sort of problem on the Downloads site. I have logged a Critical ticket with the team that manages that area, and I also requested an investigation into possible process breakdowns. I referenced seven discussion threads in Communities, supporting my request for the broader investigation.

I apologize on behalf of VMware.

Thank you.

Badsah

---

Badsah Mukherji

Senior Community Manager, VMware Communities

[jasonboche]

Awesome Badsah, thanks!

[i]Jason Boche[/i]

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

[jasonboche]

Bug:

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.

See http://communities.vmware.com/message/913092

[i]Jason Boche[/i]

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

[Badsah]

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

[jasonboche]

Ok, we need to re-download all components and re-install as of tonight.

Thank you for the update.

Jas

[i]Jason Boche[/i]

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

[jpoling]

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

[jasonboche]

I just got the new bits downloaded about 30 minutes ago and am going through the upgrade again.

If you previously had 84767 installed, you now cannot upgrade to 84782. Running the 84782 installation seems to think 84782 is already installed when in actuality 84767 was installed. Thus you need to uninstall all 84767 VMware components, then re-install the new 84782 bits. Also, when you uninstall 84767, it will remove any custom SSL certificates you have imported to get rid of the nagging SSL message each time you log into the VIC.

What a mess.

BTW, while waiting for the new 84782, I was trying to perform some VC management using the 84767 build. The VIC kept crashing on me on various screens. Seemed pretty unstable.

Update: I have now re-installed the new bits and Help|About is still showing build 84767 for both the VC Server and VIC. That's still the wrong version. I'm giving up for the night - spent a lot more time than I planned on this. Other things need attention.

[i]Jason Boche[/i]

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

[jpoling]

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

[shurik]

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

[java_cat33]

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 :smileygrin:

Message was edited by: java_cat33

[mhutchesson1]

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