stefanschuller.com ___Virtual reality


vmware vSphere Client 4.0 on Windows 7
Monday August 24th 2009, 8:34 pm
Filed under: vmware
Solgar Calcium Carbonate The Effects Of Prozac Extractions And Coumadin Tramadol Sobs Online How Long To Withdrawl From Lexapro Soma And Cimetidine Interactions Silicone Breast Enhancements Minnesota Can Cipro Cause Gum Infections Zoloft And Wieght Loss Drinking And Prozac Roaccutane Accutane Side Effects Generic For Indocin Prevacid Acid Diovan Vs Candesartan Cytotec Cervical Ripening Procedure Lozol Cost Celebrex Brain Damage Risperdal And Dopamine Remeron Provigil Sexual Side Effects Pregnancy After Breast Augmentation Atacand Liver Initiating Coumadin Therapy Effexor Tablets Prozacs Effect On The Brain No Prescription Effexor Colchicine And Blurred Vision Effexor Works Great Cures Depression Info On Prometrium 200mg Viagra Us Lipitor Side Effects Diabetics Celexa Heidi Do Trace Minerals React With Lipitor Effects Effexor Alcohol Plendil Drug Interactions Motrin Ib Shake Your Booty 2005 Brain Trauma And Prozac Cymbalta With Buspar Sparkle Brite Pools Sarasota Zoloft 50 Mg Chitosan Hd Fosamax Elderly Kidneys Christina Ricci Nude In Prozac Claritin Homepage Ultram Narcotic Detox Protocal Dark Melatonin Cipro Infection Yeast Serevent Long Term Use Clomid Cycle Days 3 Or 5 Zyvox Assistance Program Propecia And Prostate Cancer

UPDATE: This issue has been resolved in vSphere Update 1 link: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1011329

If you are reading this you probably found out that vSphere Client 4.0 is not (yet) running on Windows 7 RC or RTM

Luckily there is a way to make it work.

The error looks like this:
vsphere-error.jpg
Error parsing the server “name” “clients.xml” file.

First the credits. Big Thanks to FTUBIO from the VMware Communities (link) For supplying this solution.

1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed. You can find it in the vclient_on_w2k7_hack.zip file on the bottom of this post.

2. Create a Lib folder in the Windows 7 machine where the vSphere client is installed and copy the system.dll file from step 1 into this folder. Create the folder lib under the vSphere client launcher installation directory (%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\).

3. Copy (and overwrite) the VpxClient.exe.config from the zip file in the bottom of this post to the %ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\ folder

note: You might have an issue with the UAC settings and are not allowed to replace files in the Program Files folders. In this case make sure that you run the explorer as administrator (Start -> All programs -> Accessories -> Windows Explorer. Right Click “Run as administrator”).

4. Create a system variable devpath with a value of C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
assuming your default install path is C:\Program Files

5. Reboot your machine and start vSphere client (For some people a reboot was not nescesary)

Note1 that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care

Note2 If you use Windows 7 64-bit replace “Program Files” with “Program Files(x64)” in all cases

vclient_on_w2k7_hack.zip

1 Star2 Stars3 Stars4 Stars5 Stars (4 votes, average: 4.75 out of 5)
Loading ... Loading ...
4 Comments