vSphere Client in Windows 7
Win-Get
I think this is great. At least if you're like me and have like 3 CMD.exe windows open at all times just because you're addicted to the command line.
win-get is an automated install system and software repository for Microsoft Windows written in pascal (for the command line client) and php for the online repository. The ideas for its creation come from apt-get and other related tools for the *nix platforms.Lifehacker
The system works by connecting to a link repository. Finding an application and downloading it from the stored link using wget.exe . Then performing the installation routine (silent or standard). And finally deleting the install file.
(0) |
Get 5 GB of free Storage with Windows SkyDrive
MakeUseOf - Get 5 GB of free Storage with Windows SkyDrive
(0) | MakeUseOf, online, SkyDrive, storage
While I mostly use a PC at work and a Mac at home, occasionally I use my “other” laptop. That special one who only gets powered on a couple of times a month to do random and various tasks and as the title would suggest, it’s running Windows 7.
So, I have an ESXi 4.0 server here at home that runs a Linux server, a windows 2003 server and other various guest OS flavors. As of ESX 4.0, the client was renamed and updated to vSphere Client instead of vMWare Infrastructure Client. That client piece is the piece that lets you modify your ESX host and all of its virtual machines, datastores, network, etc…
As luck would have it…the client doesn’t work under Windows 7. Blast! You get this error:
Error parsing the server “SERVER IP” “clients.xml” file.
With Google and a little patience, I got it working again – for the first time.
Here’s a little rundown of how to get VMWare’s latest client product to work under Windows 7:
For starters, your system needs a file from Microsoft’s .NET Framework on an earlier system of Windows. I got mine from an XP machine.
- Obtain a copy of
%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dllfrom a Windows Vista or below that has .NET 3.5 SP1 installed. - Create a folder on your Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory
(%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib+). - Now we need to tell the vSphere client that we’re going to run the product in Development mode. So, in the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a <runtime> element and a <developmentMode> element as shown below. Save the file.
<configuration>
...
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>
- Create a batch/cmd file (e.g. *VpxClient.cmd*) in the same location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client.
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" - Replace the shortcuts in the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked.
Big up to Fernando from the VMWare Communities forum for writing this up. I changed a few things form his original post but follow these steps and you’ll vSphering in Windows 7.


I’ve found that this works great, with one exception. When I close the vSphere client, especially if I’ve done work with consoles, the vpxclient process stays active in task manager, and starts eating memory. I just watched it go from 180MB while running, with two VM consoles open, to a little over 300MB before I ended the process 5 minutes after I thought that I had closed the client. Seems like a pretty serious memory leak to me, no telling how much RAM it would have eaten if I hadn’t been watching it.
This is on Windows 7 Enterprise RTM btw.
Weird.
I tested it a few times tonight and I cant reproduce the problem you’re having. My process closes almost immediately and doesn’t suck up a lot of memory at all.
I’m using Win 7 Ultimate – Build 7100