___Virtual reality

vmware vSphere Client 4.0 on Windows 7
Monday August 24th 2009, 8:34 pm
Filed under: vmware

UPDATE: This issue has been resolved in vSphere Update 1 link:

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:
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 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

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

Microsoft Hyper-V architecture explained
Thursday July 10th 2008, 7:49 am
Filed under: Microsoft

Hello there,

I have been trying to find a good explanation about the underlying architecture of the newly released Microsoft Hyper-V virtualization role for Windows 2008
I found this great explanation on by Matt McSpirit

Wanted to share this….

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

Guide: how to setup APC Powerchute Network Shutdown in VMware ESX 3
Saturday October 06th 2007, 9:04 pm
Filed under: vmware

At customers I often need to setup ESX servers together with APC UPS devices. this guide describes how to do that.

APC has a guide on how to do this but it doesn’t totally cover the installation for VMware ESX 3.0.x For example it forgets to tell you about the firewall in ESX 3 that blocks some ports that need to be open to make the Powerchute Network Shutdown agent communicate with your APC ups (with network management card option installed)

you have an ESX 3 server running.
You have an APC UPS with a management card that is configured.
The IP address of the ESX server is registered to allow it to communicate with the management card.
You know the login, password and authentication phrase of the UPS management card.

This is a 3 step process

1. Configure the VMware ESX 3 firewall
2. Install the APC Network Shutdown agent
3. Configure the APC Network Shutdown agent

Step 1 – Configure the VMware ESX 3 firewall

Logon to your service console with your favorite ssh client (putty)

open up the firewall with the following commands

esxcfg-firewall -o 80,tcp,out,"APC tcp Port 80"
esxcfg-firewall -o 3052,tcp,in,"APC tcp Port 3052"
esxcfg-firewall -o 3052,udp,out,"APC udp Port 3052"
esxcfg-firewall -o 3052,udp,in,"APC udp Port 3052"

Move to the next step.

Step 2 – Install the APC Network Shutdown agent

Download the “PowerChute Network Shutdown v2.2.1 for VMWare” from the APC website called pcns-2.2.1-100.i386.rpm link(need an account to get it)

copy the file to the ESX service console and run the following command

rpm -ihv pcns-2.2.1-100.i386.rpm

Step 3 – Configure the APC Network Shutdown agent

Run the configuration script command:


Now a “wizard” will guide you to configure the agent follow the instructions.

after this you can configure the rest of the setup through a webinterface http://youresxserver:3052

In the event log link you can check if the esx server is communicating with the UPS. It should show a message that it established a connection.

Resource Links
APC install guide link
VMTN forum link (thanks box293)

1 Star2 Stars3 Stars4 Stars5 Stars (11 votes, average: 4.73 out of 5)

Citrix buys xensource
Wednesday August 15th 2007, 5:38 pm
Filed under: citrix,vmware

While VMware is busy with is IPO this week has Citrix been busy and bought Xensource. This is pretty big news and shakes the virutalization world !!

Read here for the press release and look here for some more insight.

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Cool Tool Alert ! ESX console manager
Thursday June 28th 2007, 8:07 pm
Filed under: vmware

Just came across this interesting tool to view and control different stuff in the VMware ESX service console using a windows based GUI app.
Pretty smart for ESX managers with not so much linux skills.

from the source:


List Virtual Machines and Virtual Disk information with the location and size of the files
(also for unregistered Virtual Machines)

Rename Virtual Disks of a registered Virtual Machine

Kill Virtual Machine Process
If the Virtual Machine can’t be powered off with the VMware tools

List All Virtual Disk Flatfiles on a Datastore with size and modificationdate.

View Logfiles on the ESX Host

Register on the website, download and install it on your windows box (worked on my windows vista)

The tool is version, so I can imagine that it will expand with more features in the future.

1 Star2 Stars3 Stars4 Stars5 Stars (4 votes, average: 3.50 out of 5)

Remotely upgrading VMware ESX 3.0.0 to 3.0.1
Tuesday June 26th 2007, 10:59 pm
Filed under: vmware

Where possible when I do an upgrade from 3.0.0 to 3.0.1 I will try do a re-installation. The installation of ESX doesn’t take that much time especially if you have all configuration settings and licenses available and it’s always nice to have a “clean” install.

But I wanted to give an upgrade a try. Sitting at home using vpn to my corporate network I only have my ssh client(putty) available, no physical access to the server and the server in question does not have any remote management (ilo, rmgt) available. Searching trough the vi3_installation_guide.pdf I came across the pretty simple procedure.

Upgrading Using esxupdate
To upgrade using esxupdate

1 Download the esxupdate tar archive bundle.
2 Extract the compressed tar archive and change to the newly created directory.
3 Type esxupdate -n update.
4 When the update command completes, reboot the ESX Server host.

I started with migrating my vm’s to another esx server just to be sure.

I downloaded the “ESX Server 3.0.1 Upgrade Package from earlier releases of ESX Server 3” from the download section on and copied it to my esx server using winSCP and extracted the tar and followed the guide:

tar -xvzf 3.0.1-32039-full.tgz

cd 32039

esxupdate –n update (took about 12 min)

last 2 lines from the update sequence
INFO: — TOTALS: 221 packages installed, 0 pending or failed, 0 excluded —
INFO: Install succeeded – please come again.


Now I just need to install the 30+ patches that are available for 3.0.1, much more then there are for 3.0.0
Maybe it’s time for a new version Vmware ESX 3.0.2 :-)

1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

vmware esx lite
Friday June 15th 2007, 10:25 pm
Filed under: vmware

Normally I do not post news on this blog but this “rumor” could in my opinion start a new era in x86 virtualization.

I found this article on

VMware Inc. is working on a reduced footprint version of its ESX hypervisor, called ESX Lite, that would run directly within a server’s firmware, has learned.


(if true) VMware ESX lite will make the virtualization layer thinner and closer to the hardware then ESX does and will provide an out-of-the-box pre-installed virtualization solution appliance.

I am sure this article will feed the buzz around virtualization and shows where the technology might be going.

I will be following this story closely….

UPDATE july 4th 2007 on the ESX lite story.Dell will come with a product called VESO that will have a ESX lite version pre-installed read here

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

License your virtual Microsoft Windows servers but no support
Monday June 11th 2007, 11:03 pm
Filed under: vmware

As virtualization technology is coming out of its infant years (x86 virtualization that is, as IBM mainframes have done it since before I was born) and the technology has proven to be a stable solution for years, it seems weird that MS is not giving in and is willing to support virtual servers running windows (besides of their own virtual server products)

Especially now that Microsoft has just released an official document that explains the rules for licensing MS Windows on virtualization products like vmware ESX and SWsoft virtuozzo

Microsoft licensing document source
Microsoft Virtualization Support policy source

Maybe Microsoft should re-think it’s support policy !

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

Best practices tips for virtualizing your infrastructure
Thursday June 07th 2007, 1:03 pm
Filed under: vmware

Paul Rooney from has written a post with some interesting tips and insights about deploying virtualization technology in your organisation.

It are notes taken from the Microsoft TechEd 2007 event held in Orlando.LINK

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

Server cloning in VMware ESX without virtual center
Tuesday May 29th 2007, 12:29 pm
Filed under: vmware

As a consultant I sometimes run into smaller customers that really like the bare bone virtualization technology that VMware ESX provides and buy the starter edition (which comes pretty cheap)
The problem with the starter edition is that you do not get a lot of the cool features that comes with the ESX enterprise edition and virtual center, but the costs from the starter edition to a full blown enterprise edition with virtual center is pretty big for some of my smaller customers.

One of the features missing is the ability to clone your virtual machines or creating virtual machines from templates in an easy way. A cheap and pretty simple way to get this functionality is to use the (free) VMware Converter 3.0 product.

Here it the procedure for cloning a windows 2003 VM for example

1. Create a VM (a “master” image) of a Windows 2003 installation in ESX and make sure it’s shutdown

2. Download VMware converter and install it on a windows computer (vista is not supported yet !) Link to download

3. Download the MS sysprep tools from MS and unpack them (in this case windows 2003 Link)

4. Open the VMware converter and click on “Import machine” this will start the “VMware converter Import Wizard”

5. Choose As the source machine your ESX server and select your master image

6. Choose as the destination server your ESX server

7. Customize the machine’s computer name (sid), ip address, etc (here you are asked for the location of the sysprep files from step 2)

and your done !

Please be aware that the windows vm image is copied over the network from the ESX to the computer running the converter and back to the ESX server, so it can take some time (depending on your network speed, disk read speed etc.)

I will post a more detailed guide with some screenshots pretty soon.

Stefan Schuller

1 Star2 Stars3 Stars4 Stars5 Stars (5 votes, average: 5.00 out of 5)