Enable SSH on VMware ESXi 5.5 via vSphere Client

VMware
To enable SSH on your VMware ESXi 5.5 host you can do this directly on the host or alternatively you can do this using the VMware vSphere Client. Using the vSphere client click on the "Configuration Tab" Now click on the "Security Profile" option in the Software pain (on the left hand side) Now click on the "Properties" tab which will open up Remote Access Select the SSH Service (which is currently stopped) and click on the options button.  Now select the startup policy you require and then click on the Start button. You should now be able to access your VMware ESXi host via SSH.
Read More

VMware Tools for Nested ESXi

VMware
This VIB package provides a VMware Tools service (vmtoolsd) for running inside a nested ESXi virtual machine. The following capabilities are exposed through VMware Tools: Provides guest OS information of the nested ESXi Hypervisor (eg. IP address, configured hostname, etc.). Allows the nested ESXi VM to be cleanly shut down or restarted when performing power operations with the vSphere Web/C# Client or vSphere APIs. Executes scripts that help automate ESXi guest OS operations when the guest’s power state changes. Supports the Guest Operations API (formally known as the VIX API). New in version 1.1: – Now reports IPv6 addresses as well as IPv4 addresses for nested ESXi guests. For more information: What’s in a VIB? woot! VMware Tools for Nested ESXi  
Read More

HP Customised VMware ESXi Images

VMware
The new Proliant Gen8 servers require you to use a customised image for the installation of ESXi to be a success.  The network and storage drivers are combined in the HP customised image and therefore you are unable to install ESXi with a standard download ISO from VMware. There are a number of download options available to you which is summarised below:  1 - HP Customised ESXi Image ESXiandvSphere: vSphere 5.5 U1 June 2014 - Download here vSphere 5.5 June 2014 - Download here vSphere 5.1 U2 June 2014 - Download here vSphere 5.1 U1 Sept 2013 - Download here vSphere 5.1 Feb 2013 - Download here ESXi 5.0 U3 June - Download here ESXi 5.0 U2 Sept 2013 - Download here ESXi 5.0 U1 Oct 2012 - Download here ESXi…
Read More

Adding the ESX/ESXi host to an Active Directory domain fails with the error “Errors in Active Directory operations”

VMware
When adding a 4.1 ESX/ESXi host to an Active Directory domain it fails or whilst adding you receive an error "Errors in Active Directory operations". If you have netlogond enabled on the host, you can check to see if you have similar entries in the netlogond.log: 20100820075107:0xf7c74b90:DEBUG:[LWNetSrvGetCurrentDomain () /build/mts/release/bora-234910/likewise/esxi- esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83] Error  at /build/mts/release/bora-234910/likewise/esxi- esxi/src/linux/netlogon/server/api/lwnet-pstore.c:83 [code: 136] The issue is more than likely down to TCP/UDP ports not open between the ESX/ESXi host and Active Directory server. Make sure you have the following TCP and UDP ports open:- Required (TCP and UDP) ports are Port 88  - Kerberos authentication Port 123 – NTP Port 135 - RPC Port 137 - NetBIOS Name Service Port 139 - NetBIOS Session Service (SMB) Port 389 - LDAP Port 445 - Microsoft-DS Active Directory, Windows shares (SMB over TCP) Port 464 - Kerberos - change/password changes Port 3268-…
Read More

Installing vSphere Client 5.1 fails

VMware
When installing the vSphere 5.1 client you may encounter the following error message "Failed to install hcmon", if you look at the vminst.log file (which is normally located in the %TEMP% area) you will notice the following:- After troubleshooting this issue I found that I required Microsoft .NET Framework 3.5.1 Service Pack 1 installed (or the feature wasn't turned on) before installing the client. Install Microsoft .NET Framework 3.5.1 Service Pack 1 Install the vSphere 5.1 client  
Read More

Change root password on all (or some) vSphere hosts

VMware
As part of a security audit I needed a quick way to change the ESXi root passwords without having to go on to each server. I was looking for a script that would automate at least some of the work for me and I came across a script called Change-ESXiPassword.ps1 that was created by Jesse Gardner which I thought I would give a try. After running the script and knowing it works fine I will be personally be running this every quarter. This script: prompts you for the old password prompts you for the new password prompts you for the vCenter server name prompts you for vCenter credentials Queries vCenter for all hosts that you wish. See "Host selection section" in the middle of the script to tweak what hosts it…
Read More

VMware Release & Build Info

VMware
Whilst doing some research today based around release/build numbers for several VMware products I discovered a site with all the necessary information in one place.  Great news so I thought I would share it with you all click HERE to direct to the information.
Read More

Creating snapshots in a different location than default virtual machine directory

VMware
In ESX/ESXi 3.x and 4.x, all files comprising snapshots are created in the virtual machine's working directory. By default, the working directory is the same directory as the virtual machine's (.vmx) configuration file. Thus, if the virtual disk (.vmdk) file is located on different datastore than the virtual machine itself, virtual disk redolog (-delta.vmdk) files are created alongside the virtual machine's (.vmx) configuration file instead of beside the virtual disk (.vmdk) file. You may want to change the location (new directory on the same or alternative datastore) where virtual disk redolog (-delta.vmdk) files are created, in order to: Create snapshots but do not have enough space on the VMFS volume. Power on a virtual machine when there is not enough space to create a swap file on the VMFS volume. (more…)
Read More

Creating a persistent scratch location for ESXi

VMware
You can configure persistent scratch space for ESXi using the vSphere Client: Connect to vCenter Server or the ESXi host using the vSphere Client. Select the ESXi host in the inventory. Click the Configuration tab. Click Storage. Right-click a datastore and select Browse. Create a directory for this ESX host (eg, locker-servername) Close the Datastore Browser. Click Advanced Settings under Software. Select the ScratchConfig section. Change the ScratchConfig.ConfiguredScratchLocation configuration option, specifying the full path to the directory. eg. /vmfs/volumes/DatastoreName/locker-servername Click OK. Put the ESXi host in maintenance mode and reboot for the configuration change to take effect. You could also use vCLI or PowerCLI to make the change but I found the above procedure easier to use.
Read More