airport utility on Windows 7

11 03 2011

Following on from my last post about the vSphere client, it turns out that the Apple Airport utility also has issues running under Windows 7.

This is a problem for me, as I run 3 of them ……

As you can see, when I try to manage one of them I get a dreaded 10057 error. The Airport utility finds all 3 of my airports, but I cannot manage them.

Suggestions seem to range from disabling IPv6 to turning off the windows firewall – to power cycling the whole environment … it seemed about as endless as it was fruitless …. until

The simple solution appears to be simple clicking on the File menu, selecting Configure Other (Ctrl+Shift+O) and entering the IP address & password of the Airport – that is displayed in the App.

Viola, I can now manage my Apple Airports again …. under Windows 7.


vsphere client on Windows 7

9 03 2011

So as it always seems to happen, the few apps you really want to work …. dont.

I loaded up the vSphere client under Windows 7 & it failed to connect to my ESXi host, nor would it connect to my Virtual Centre server.

It just fell in a heap with the following errors ……

“Error parsing the server “server name” clients.xml” file.”


“The type initializer for ‘VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.”

After much Google trawling later, I came across the solution.

  • Create lib folder under the Launcher folder

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib

  • Copy system.dll into the lib folder, or if you prefer to grab your own dll from the %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\ directory of a Windows XP machine with .NET v3.5 SP1 installed.

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher

The only change in the config file is the addition of the following lines:

<developmentMode developerInstallation=”true”/>

before the last </configuration> close tag.

  • Create a new system variable

DEVPATH=C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\lib

  • Change the VpxClient.exe app to run as an administrator:

If all things went well – you should now just be able to launch the vSphere client & admin your machines as you did before.

History of Operating Systems

9 03 2011