VMware Cloud Community
OaktonIT
Contributor
Contributor

VirtualCenter 2.0.2 Upgrade Patch 1?

I cannot find this patch and evidently it is needed for the patch ESX-1002088. Here is a quote from its description:

"The fix for taking snapshots on virtual machines with Raw Device Mapping (RDM) disks attached will work properly only with VMware VirtualCenter 2.0.2 U1. With this patch, VMware Consolidated Backup (VCB) 1.0.2 and VCB 1.0.3 can now be used to take snapshots on virtual machines with pass-through RDM disks attached."

Anyone know where it is? Right now I'm guessing it doesn't exist yet even though the other patch references it.

Thanks!

0 Kudos
31 Replies
williamarrata
Expert
Expert

The patch does exist. It is a download and you can downlowd this from the esx 3.02 patches.

Hope that helped. 🙂
0 Kudos
esiebert7625
Immortal
Immortal

These are the 2 patches, I've never heard of 2.0.2 U1

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100208...

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100209...

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos
williamarrata
Expert
Expert

I should have posted this URL earlier. OOPS .

Hope this helps.

Hope that helped. 🙂
0 Kudos
OaktonIT
Contributor
Contributor

Thanks but I just don't see it here:

http://www.vmware.com/download/vi/vi3_patches_302.html

0 Kudos
OaktonIT
Contributor
Contributor

The patch your link is to is the patch that refers to VirtualCenter 2.0.2 U1. Am I not seeing something everyone else is?

0 Kudos
williamarrata
Expert
Expert

Its the third one down. DO you see it now...

Hope that helped. 🙂
0 Kudos
esiebert7625
Immortal
Immortal

2.0.2 U1 if it exists is not currently released. Either this is a typo in the patch documentation or it is a forthcoming release of VC that will be released soon and include the additional fixes that complement the ESX patches.

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos
OaktonIT
Contributor
Contributor

Is it within one of those patches?

0 Kudos
esiebert7625
Immortal
Immortal

William, I think you're talking about the ESX patch and the OP is talking about the VC patch that the ESX patch mentions.

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos
williamarrata
Expert
Expert

Yes your right. ESX-1002088 is the patch that i'm refering to . Now I may be wrong but, VMWare does not duplicate Patch numbers, or I have not seen this yet, If I'm wrong about this I apologise.

Hope that helped. 🙂
0 Kudos
OaktonIT
Contributor
Contributor

Thanks, I thought I was losing it there for a second. This is what I thought.

0 Kudos
hicksj
Virtuoso
Virtuoso

FYI, it now exists!

Release Notes VC 2.0.2 Update 1

0 Kudos
formulator
Enthusiast
Enthusiast

I installed this today and now webaccess is all messed. If I goto the site I see no text and the page looks odd. Tried in IE and Firefox. Anyone else encountered this?

0 Kudos
esiebert7625
Immortal
Immortal

There is a update to Tomcat bundled in the 2.0.2 U1 version. Have you tried stopping and re-starting the VC Web Service on the VC server?

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos
formulator
Enthusiast
Enthusiast

yes

0 Kudos
esiebert7625
Immortal
Immortal

On the VC Server try loading the default file for web access from Windows Explorer and see if it displays properly in IE, it should be called, C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot\index1.html

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Thanks, Eric

Visit my website:

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

0 Kudos
formulator
Enthusiast
Enthusiast

it looks the same way as it does when i try from a remote host. I think the problem is related to the tomcat or java update. I don't normally use webaccess so it's not a huge deal but it is annoying me.

0 Kudos
formulator
Enthusiast
Enthusiast

I think it might be that the file welcomeRes.js is missing, infact the html point to the directoy "en" that doesn't exist. Does this file exist on your VC server? Unfortunately I upgraded both our VC servers before I went to download the updated client through webaccess and noticed it was busted so I can't check our other server. Smiley Sad

0 Kudos
williamarrata
Expert
Expert

It states the following on the web site;

This maintenance release includes changes to VirtualCenter Management Server and VI Client software. If you upgrade a VirtualCenter Server host using this maintenance release, you must also upgrade all VI Client hosts. You can upgrade the Windows client hosts by downloading the software from an upgraded VirtualCenter Server host, or by selecting VI Client from the VirtualCenter installation startup page.

Installing VirtualCenter 2.0.2 Update 1

VirtualCenter software maintenance releases comprise a complete software installation (rather than being supplemental software or "patches"). As with a fresh install, the VirtualCenter installation program examines the local system, identifies any existing VirtualCenter installation, and guides you through the installation (or upgrade) process.

Note: If VirtualCenter components are already installed on the host machine, the installation program prompts for confirmation that you want to upgrade.

  1. Back up your VirtualCenter database (as recommended above).

  2. Download the software installation file from .

  3. Stop the VirtualCenter Server service.

  4. Use autorun.exe to start the installation. Select VirtualCenter Management Server from the VMware VirtualCenter Installer startup page.

  5. Select Yes to upgrade an existing Installation.

    Note: If you are using Microsoft SQL Server as your database server, using the "master" database for VirtualCenter Server tables is not a supported configuration. If your previous VirtualCenter Server installation was configured to use the "master" database instead of a specific database created for VirtualCenter Server, a warning message is displayed stating that your current configuration is not supported and that it has to be manually corrected. This warning message is displayed in a GUI-based installation only.

  6. Step through the VirtualCenter Install wizard, which guides you through several configuration details, including identifying your database instance. You will need to select your existing VirtualCenter database and enter the VirtualCenter database user name and password.

  7. After upgrading the VirtualCenter Server, you must also upgrade all Windows host systems to the upgraded VI Client software. Use the autorun.exe again to start the installer but select Virtual Infrastructure Client from the VMware VirtualCenter Installer startup page.

Note: If the existing installation of VirtualCenter service fails to shut down gracefully by releasing all the system resources, the upgraded installation of VirtualCenter service will be prevented from starting. In this case, you must reboot the VirtualCenter Server machine.

For complete information about installing or upgrading VirtualCenter, see Installing and Upgrading the VirtualCenter Product.

Here is some more information about the update.

Hope that helped. Smiley Happy

Hope that helped. 🙂
0 Kudos