27 Jul 2010

vSphere client on Windows 7

http://www.techhead.co.uk/running-vmware-vsphere-client-on-windows-7

Many of you, like myself, have started running Windows 7 as their primary desktop OS and find it to be a massive improvement over Windows Vista on so many levels.
One of the very few inconveniences I have found with it, and this is not an bug or problem with Windows 7 itself, is the inability to run the VMware vSphere Client.
UPDATE: Good News – This issue has now been resolved in VMware ESX/ESXi 4.0 Update 1 (U1).
When attempting to run the client the following errors are received and you are unable to proceed any further:
“Error parsing the server “

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

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

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

Luckily there have been a few good VMware forum posts such as this one by ftubio which outlines how to successfully run the vSphere Client under Windows 7.  I thought I’d put together this brief post with a few screenshots to outline the required steps.
I am running the x64 version of Windows 7 so you will notice that any reference to the ‘Program Files’ will have an ‘(x86)’ at the end of it.  If you are running the x86 version of Windows 7 then ignore the ‘(x86)’ portion of the directory path (ie: C:\Program Files (x86) –> C:\Program Files).
Follow these 4 basic steps and you’ll be up and running in no time!

Step 1.

imageDownload this DLL called system.dll
*Note:  This DLL is usually found in the  %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\  directory of a non Windows 7 PC with  .NET v3.5 SP1 installed.

Step 2.

Once downloaded install it in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib” directory.  If the ‘lib’ directory doesn’t exist then create it and drop the dll file into it.
VMware vSphere Client Windows 7

Step 3.

Next edit the “VpxClient.exe.config” file which can be found in the “C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher” directory and add the following three lines to it in the location specified in the screenshot below.  Then save the changes.


VMware vSphere Client Windows 7

Step 4. 

From the Windows 7 ‘System Properties’ click the ‘Advanced’ tab and then the ‘Environment Variables’ button as we want to add a new ‘System’ variable.
VMware vSphere Client Windows 7

Create a new ‘System’ variable called ‘DEVPATH’ and assign the following variable value:
C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

VMware vSphere Client Windows 7

You are now ready to start using the VMware vSphere Client on your Windows 7 machine!  Some people have reported having to run the client as an ‘Administrator’ so if you are having difficulties it may pay to try this – I luckily didn’t experience this problem. Also you will likely have to reboot your machine (or restart the explorer.exe process) for your new path information to come into effect.

VMware vSphere Client Windows 7

26 Jul 2010

ifone settings for IP Phone AT320 - 530

AT320 settings panel

Enable SSH in ESXi 4.0



By default SSH is disabled in ESXi however you can enable it by follow these steps:


  1. At the Administration Windows press Alt+F1. You will get a black screen
  2. Type the word unsupported and press Enter
  3. Enter your root password and press Enter, you will get a prompt
  4. Change directory into /etc
    #cd /etc
  5. Open inetd.conf in vi
    #vi inetd.conf
  6. arrow down until you see #ssh stream tcp…
  7. With the cursor on the # type x to delete the #
  8. Type :wq! to exit vi and save your changes
  9. Restart host or restart inetd process

Restart inetd process

    • Now we need to find the process running inetd. To do that run the following command
      #ps -a grep inetd
    • Find the process number, lets pretend it is 1234. Run the following command to kill the inetd process
      #kill 1234
    • Now we need to start inetd again
    • #inetd
    • You then will be able to access host via SSH

    Total Pageviews