VMware Cloud Community
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+
Reply
0 Kudos
157 Replies
RParker
Immortal
Immortal

> 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.

Reply
0 Kudos
RParker
Immortal
Immortal

> 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"

Reply
0 Kudos
RParker
Immortal
Immortal

> 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.

Reply
0 Kudos
jasonboche
Immortal
Immortal

As of this morning, the MD5SUM value for the VirtualCenter .ZIP download does not match the download website. The .ZIP download installs build 84767 which is the wrong build.

As of this morning, the VirtualCenter .ISO MD5SUM does match the download website but it still installs build 84767 which is the wrong build.

The MD5SUMs do match for all the other components I downloaded: Converter Enterprise ZIP file for Windows, Converter Enterprise tarball for Linux, ESX Update 1 CD image .ISO however, I have not verified if they are the correct builds or not. As seen above with the VirtualCenter .ISO file, matching MD5SUM values do not guarantee the correct build number.

I wonder if anyone from VMware on call this weekend that can fix this before the wrong version gets spread about. There were quite a few people at my VMUG last month who weren't aware of the ESX 3.5.0 .ISO incident.






[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+
Reply
0 Kudos
admin
Immortal
Immortal

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:

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.

Reply
0 Kudos
FrancWest
Contributor
Contributor

Hi,

just installed the VI update 1, but the client (shows version 84767 for both server and client) keeps crashing. During use it suddenly complains about the vpx logfile is in use by another process and few seconds after that it just shuts down. This happens on both clients we installed the VI client on.

Franc.

Reply
0 Kudos
jasonboche
Immortal
Immortal

Hi,

just installed the VI update 1, but the client (shows version 84767 for both server and client) keeps crashing. During use it suddenly complains about the vpx logfile is in use by another process and few seconds after that it just shuts down. This happens on both clients we installed the VI client on.

Franc.

I'm having these issues as well on both clients I installed the VIC on. I've uninstalled all VC components waiting to decide on what to do. To roll back to the previous version of VC, the database will have to be restored from backup. I had tried rolling back to the previous 2.5.0 version of VC but the VC service won't start. Assuming something in the database changed as a result of the Update 1 upgrade.






[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+
Reply
0 Kudos
FrancWest
Contributor
Contributor

I think I revert back to the previous version then, because this isn't workable.

Great way of quality control by VMWare. Smiley Sad

Franc.

Reply
0 Kudos
FrancWest
Contributor
Contributor

looks like the 64192 version of the VIC is much more stable. I installed it on my machine and didn't crash so far. The VI server is still the 84767 version and looks like the old client is able to talk to that one.

Franc.

Reply
0 Kudos
java_cat33
Virtuoso
Virtuoso

Hi,

just installed the VI update 1, but the client (shows version 84767 for both server and client) keeps crashing. During use it suddenly complains about the vpx logfile is in use by another process and few seconds after that it just shuts down. This happens on both clients we installed the VI client on.

Franc.

I'm having these issues as well on both clients I installed the VIC on. I've uninstalled all VC components waiting to decide on what to do. To roll back to the previous version of VC, the database will have to be restored from backup. I had tried rolling back to the previous 2.5.0 version of VC but the VC service won't start. Assuming something in the database changed as a result of the Update 1 upgrade.


[i]Jason Boche[/i]

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

Once again - surely this must have been tested before being released?

Reply
0 Kudos
jasonboche
Immortal
Immortal

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:

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.

In the past, the build numbers of VirtualCenter matched what was on the website. Communication explaining the discrepancy would be very helpful.

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

The active discussion on why the download MD5SUMs don't match the website has been overlooked.

I've downloaded the VirtualCenter .ZIP file 4 times (twice today, once yesterday, and once on 4/10).

Each time I download, I get an MD5SUM of 6201bd703a932750ca2b4b9fe68996d8

The posted MD5SUM on the website for the VirtualCenter .ZIP file is 9146aa4743c0a56e37921f62fb898a64

The .ZIP file on the VMware downloads website doesn't match the posted MD5SUM.






[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+
Reply
0 Kudos
FrancWest
Contributor
Contributor

Another question: is the update 1 for ESX server itself the same as the updates that arrived yesterday via the auto update manager ?

The version number on the summary tab for the ESX server shows the latest build, but I'm unsure that all updates that were downloaded using update manager are the same as update 1 or is update 1 more comprehensive?

Regards,

Franc.

Reply
0 Kudos
jasonboche
Immortal
Immortal

looks like the 64192 version of the VIC is much more stable. I installed it on my machine and didn't crash so far. The VI server is still the 84767 version and looks like the old client is able to talk to that one.

Franc.

When I can get the VIC client to open without crashing, I have found the remote console isn't working most of the time. Opening a remote console just displays a black screen for the console. No video/GUI of the actual console. I'm not sure if this is an agent issue or not as my ESX hosts are also being managed by Lab Manager Server as well which installs its own agent onto the ESX hosts. It wasn't an issue until VC2.5 Update 1. The previous version of VC2.5 didn't have this issue. I'd be interested to hear if anyone else is having this particular problem.

At this point, I'm rolling back. Got to dig out the SQL restore tapes 😐






[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+
Reply
0 Kudos
FrancWest
Contributor
Contributor

Jason,

do you mean that you get that blank console using the old version of VIC ? I can't reproduce that I'm running the old VIC for some time now without crashing and also can open the consoles of my VM's.

Franc.

Reply
0 Kudos
beckhamk
Enthusiast
Enthusiast

just installed the VI update 1, but the client (shows version 84767 for both server and client) keeps crashing. During use it suddenly complains about the vpx logfile is in use by another process and few seconds after that it just shuts down. This >happens on both clients we installed the VI client on.

This morning I updated VC and VIC only, which are both installed on the same server. We have the exact same issues. It either complains about the vpxlogfile or it just crashes. I spent 5 hours on the phone with vmware tech support and an escaltation engineer and no luck. They wanted to pick back up on monday. Which was ok with us, as we had also installed a VIC on a local desktop and that works no problems.

Here is what I am thinking - our server that has both VC and the VIC installed, we also have the update manager and converter plugin installed. My local desktop and another server (seperate from the vc server) has the VIC working fine. The only difference is that they both do not have any of the plugins installed.

I really have to laugh at myself on this one. I always wait a week or two before updating any new softwares (outside of vmware and including vmware). But today I completely over looked when exactly these had been released. But I can say that VC seems to run just fine using VIC from the other two machines. Anyone seeing this same work around as I?

Reply
0 Kudos
RParker
Immortal
Immortal

Well our experience is the exact opposite. I found this new build to be more stable. Of course I have been running it for a day or less, but it sure seemed like it was a bit faster and more stable.

We have ALL the plugins enabled, and even the svmotion plugin, and not even the slightest quirk in the client. I installed the VIC on the VC server and my machine (running vista) and a few others, but so far the new build seems to be better than before.

Reply
0 Kudos
RParker
Immortal
Immortal

ESX update 1 includes ALL patches up to date, so if you install ESX update 1 or update your existing servers the build should be the same.

So yes this should be a comprehensive update.

Reply
0 Kudos
beckhamk
Enthusiast
Enthusiast

I just noticed that none of our templates which are stored on a lun show up when switching to the Virtual machines and templates like they used to. They are still located on the lun though.

Reply
0 Kudos
jpoling
Enthusiast
Enthusiast

I am not seeing the instability of the VIC as some are. It seems to work just fine - though I do have that different build number. I will probably continue with upgrading our hosts next week unless there are other red flags that show up here.

Jeff

Reply
0 Kudos
jasonboche
Immortal
Immortal

I just noticed that none of our templates which are stored on a lun show up when switching to the Virtual machines and templates like they used to. They are still located on the lun though.

That's usually not too much of a a big deal. Simply use VC to browse your datastore and right click each template and import. viola!

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+
Reply
0 Kudos