A. Mikkelsen VMware ESX scripts, commands, tools and other nice to know things that will make your virtualization days easier!!!!

Wednesday, November 25, 2009

Restarting management Agent on ESX 3.x

Filed under: Troubleshooting,vSphere (ESX) — Tags: , , — A. Mikkelsen @ 21:20 pm

Restarting the Management agents on ESX Server 3.x

  1. Login to the ESX host using SSH (or from COS)
  2. Type service mgmt-vmware restart.
    Before restarting the Management Agent make sure that Automatic Startup/Shutdown is Disabled
    For more info see
    Restarting hostd (mgmt-vmware) on ESX Server Hosts Restarts Hosted Virtual Machines Where Virtual Machine Startup/Shutdown is Enabled (1003312)
  3. Type service vmware-vpxa restart.
  4. Exit the SSH session or logout of COS

Tuesday, November 24, 2009

IBM/Lenovo Bios update/Embedded Controller with dead/no battery

Filed under: Tools — Tags: , , , , , , , — A. Mikkelsen @ 15:10 pm

Below solution is on you own risk.

  1. Download the Bios/Embedded Controller from IBM/Lenovo (Diskette version)
  2. Rename the file UPDTFLSH.EXE to UPDTFLSH.EXE.OLD
  3. Create a copy of QKFLASH:EXE and rename it to UPDTFLSH.EXE
  4. Boot the labtop from the diskette
  5. Follow normal procedure for updating BIOS/Embedded Controller
  7. When the BIOS/Embedded Controller is updated the PC will trun off
  8. Poweron  and enter BIOS (F1) to verify that the new BIOS/Embedded Controller is installed.

Monday, November 23, 2009

Upgrading Windows 2008 from virtual HW 4 to 7 may cause problems

Just found this very interesting article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013109 describing a problem with Windows 2008 and ESX 4 virtual hardware version 7.

In short the article states that you might have the disks go offline in a Windows 2008 VM if you

  • Upgrade virtual hardware from version 4 to 7
  • Installing a new VM with virtual hardware 7

There is two ways to get around this (taken from the VMware KB 103109)


This can be resolved by changing the SAN Automount Policy on the system. See the Microsoft article http://support.microsoft.com/kb/973834 to change the SAN Policy to online.
The SAN policy is defined within the VDS environment of the system and is represented by the following values:
  • VDS_SP_UNKNOWN = 0x0
  • VDS_SP_ONLINE = 0x1
  • VDS_SP_OFFLINE = 0x3
For more information, see http://msdn.microsoft.com/en-us/library/bb525577(VS.85).aspx.
On Windows Server 2008 Enterprise and Windows Server 2008 Datacenter, the default SAN policy is VDS_SP_OFFLINE_SHARED. On all other Windows Server 2008 editions, the default SAN policy is VDS_SP_ONLINE.
To query current SAN policy from the command line, start DISKPART and issue a SAN command:
SAN Policy : Offline Shared


Alternatively, you can set the disk to Online after the hardware version upgrade.
To set the disk to Online:
  1. Log in to your system as an Administrator.
  2. Click Computer Management > Storage > Disk Management.
  3. Right-click the disk and choose Online.

Thursday, November 19, 2009

Free virtualization fools

Filed under: Tools — Tags: , , , , , — A. Mikkelsen @ 22:19 pm

David Davis has put together a list of what he thinks is some of the best free virtualization tools avaiable.

I still think that he is missing a few, like

See the full article at

Wednesday, November 18, 2009

Project Onyx Alpha Release

Filed under: PowerShell,Project Onyx,Scripting — Tags: , — A. Mikkelsen @ 18:05 pm

Finally everyone outside the closed beta is now able to get hands on with the cool application Project Onyx.
Thanks to Carter Shanklin

Project overviewGot it from http://www.ntpro.nl/blog/archives/1330-Project-Onyx-Alpha-Release.html

Onyx is a standalone application that serves as a proxy between the vSphere Client and the vCenter Server. It monitors the network communication between them and translates it into an executable PowerShell code. Later, this code can be modified and saved into a reusable function or script.

  1. To connect to a server, click the “Connect” icon.
  2. Enter the IP of the vCenter Server on which you want to work and click Connect.
  3. Connect with any of the following clients:For vSphere Client, in the “IP Address” field enter the following address:
    http:// [IP of the machine where Onyx is running] : [listening port]

    For vSphere PowerCLI, run the following command:
    Connect-VIServer [IP of the machine where Onyx is running] -Protocol http
    -Port [listening port] -User [username] -Pass [password]

  4. To start the generation of PowerCLI.NET scripts, click the “Start” icon.
  5. To save the generated script, click the “Save output to file” icon.

You can download Project Onyx Alpha from http://blogs.vmware.com/files/onyx_1.5.3607.25516.zip or http://bit.ly/vmwOnyx15.

To learn how it works please see this video from YouTube.com

Wednesday, November 11, 2009

Another easy guide from Techhead – iSCSI on vSphere

Filed under: ESXi,vSphere (ESX) — Tags: , , , — A. Mikkelsen @ 7:51 am

If you are looking for a easy and simple guide for setting up iSCSI on vSphere (ESX 4.x) you might want to take a look at this guide from www.techhead.co.uk

Tuesday, November 10, 2009

Running the vSphere client on Windows 7

Filed under: Microsoft,Tools,Virtual Center,vSphere (ESX) — Tags: , , , — A. Mikkelsen @ 11:21 am

Many admins have upgraded to Windows 7 and gotten into problems when trying to install the vSphere Client.

I have found a few guides to do a workaround, but the best guide is found at techhead.co.uk.

Thanks to Kiwi Si.

Powered by WordPress