VMWare: Update Standalone ESXi 5.0 to 5.1 Using a Depot Zip File

1) Download the depot file; at the time of writing the latest update is as follows and can be found here.

File size:298M
File type: zip
Release Date:2012-09-10
Build Number:799733

2) Upload the file to your datastore, in this example the file was uploaded to  “myDatastore”

3) Enable SSH on your ESXi host and on the command line, enter the following, using an absolute path to your depot file:

~ # esxcli software profile install -d /vmfs/volumes/myDatastore/VMware-ESXi-5.1.0-799733-depot.zip -p ESXi-5.1.0-799733-standard

4) Reboot, done!

VMWare: Enable SSH Daemon on ESXi 3.5

Taken from the vm-help.com website:

ESXi 3.5 does ship with the ability to run SSH, but this is disabled by default (and is not supported). If you just need to access the console of ESXi, then you only need to perform steps 1 – 3.

1) At the console of the ESXi host, press ALT-F1 to access the console window.
2) Enter unsupported in the console and then press Enter. You will not see the text you type in.
3) If you typed in unsupported correctly, you will see the Tech Support Mode warning and a password prompt. Enter the password for the root login.
4) You should then see the prompt of ~ #. Edit the file inetd.conf (enter the command vi /etc/inetd.conf).
5) Find the line that begins with #ssh and remove the #. Then save the file. If you’re new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #. Then press ESC and type in :wq to save the file and exit vi. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.
6) Once you’ve closed the vi editor, run the command /sbin/services.sh restart to restart the management services. You’ll now be able to connect to the ESXi host with a SSH client.

Tip – with some applications like WinSCP, the default encryption cipher used is AES. If you change that to Blowfish you will likely see significantly faster transfers.

Update for ESXi 3.5 Update 2 – With Update 2 the service.sh command no longer restarts the inetd process which enables SSH access. You can either restart your host or run ps | grep inetd to determine the process ID for the inetd process. The output of the command will be something like 1299 1299 busybox      inetd, and the process ID is 1299. Then run kill -HUP <process_id> (kill -HUP 1299 in this example) and you’ll then be able to access the host via SSH.

You can also download an oem.tgz file which will enable SSH (and FTP). Copy the file to a datastore with the VI client and then to bootbank with the command cp /vmfs/volumes/<datastore>/oem.tgz /bootbank/oem.tgz and then reboot.

VMWare: ESX Microsoft Visual C++ Runtime Library Error When Using Converter Plugin

This error message is displayed during import or export of a machine under vCenter Converter plugin and sometimes with the standalone converter.

If a user environment has versions of VI Client 2.5 Update 1, Update 2, Update 3, or Update 4 that coexist with vSphere Client 4.0, and you install the vCenter Converter 4.1.0 client plug-in, when you start the vCenter Converter Import or Export wizard, the vSphere Client session is terminated abruptly. An OpenSSL DLL conflict between the VI Client versions and the vCenter Converter 4.1.0 client plug-in causes this problem.
Workaround: Go to the Launcher folder in the VI Client install directory, for example, C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher, and delete the following DLL files from that location:

  • libeay32.dll
  • ssleay32.dll

For this workaround to function correctly, you also need to ensure that no additional copies of OpenSSL DLL files with different versions exist in the system path.

Also, make sure that the %TEMP% path does not have any non-english characters in it e.g. if you are using French / German / Spanish Windows OS. If you are, create the C:\TEMP directory and update your environment variables to point here.

Note for ESX users: if the fixes above do not work for you, try uninstalling all your VMWare clients, reboot and install the vCenter client from your vCenter’s https page. Now try and access your host using the vCenter client – you will connect and be prompted to download and install the Infrastructure client – if you do it this way then you shouldn’t have any issues.