How to run vSphere Host Update Utility on Windows 7 x64

Follow these instructions to fix vSphere client on Windows 7: http://communities.vmware.com/thread/211440

xcopy “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe.config”    “C:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\VIUApp.exe.config”

Create bat file for VIUApp.exe:

 

SET DEVPATH=c:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
“c:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\VIUApp.exe”  

SET DEVPATH=c:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

“c:\Program Files (x86)\VMware\Infrastructure\VIUpdate 4.0\VIUApp.exe”

Without these changes, VIUApp.exe fails adding hosts with error “The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an  exception.”

Advertisements

7 thoughts on “How to run vSphere Host Update Utility on Windows 7 x64

  1. Great tip. Worked a treat. Had to do similar for vSphere Client as well. Hopefully this will all be resolved when Windows 7 is available ‘off the shelf’

  2. I still can’t get to to work. Something else has got screwed up now. I can get the vSphere Client to work, but not the Update Utility. Very frustrating as I’ve been “working around” different companies non-Windows 7 readiness all day now.

    EARTH TO SOFTWARE COMPANIES: WINDOW 7 HAS BEEN OUT FOR OVER A MONTH. FULL VERSION. FINAL RELEASE. GET YOUR ACT TOGETHER! IT’S 2009. NEARLY 2010. THERE’LL BE ANOTHER RELEASE OF WINDOWS BY THE TIME VMWARE GET IT TOGETHER.

    End of rant. sorry.

  3. Okay, finally got it to work, but it involved adding:

    to the “settings.config” file inside the “VI Update 4.0” folder.

    Making a copy of the “VpxClient.exe.config” file from the VpxClient.exe.config file and XCOPYing it over didn’t seem to work for me.

    Perhaps I’m running a later version of vSphere? I don’t think so though, seeing as how I haven’t been able to update it.

  4. Should read:

    Okay, finally got it to work, but it involved adding:

    to the “settings.config” file inside the “VI Update 4.0″ folder.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s