VMWare: Installing VMware vSphere Client 4.x on Windows 8

Installing VMware vSphere Client 4.x on Windows 8

When installing VMWare vSphere Client 4.1 to manage VMWare ESX, you observe the following error:

Windows 8.1 Error

 

 

 

 

 

“This product can only be installed on Windows XP SP2 and above.”

Although Windows 8 is obviously above XP SP2, it would seem that Windows 8 wasn’t about when vSphere Client 4.1 or 5.0 was released. In order to work around this you simply need to do the following:

1. Extract the content from the installation file to a folder of your choice. Using 7zip, you can right click the executable file, go to 7Zip, and choose Extract to folder name.

2. Go to the extracted folder, bin sub-folder, right click VMware-viclient.exe and choose Properties. Go to Compatibility tab, and check the option “Run this program in compatibility mode for” and pick Windows 7 from the list:

Window2s 7 Compatibility Mode

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3. click OK to save the setting, and launch VMware-viclient.exe to start the installation again.

Note: If you are running vSphere 5.x you can download the newly released client which supports Windows 8 without the workaround above.

The link above also contains direct download links for all released vSphere clients.

VMWare: How to Change the ESXi System Time and HW Clock on the CLI

This article details how to change the ESXi system time and HW clock on your ESXi hypervisor machine via the CLI.

Ideally we want to use NTP to set the system time but if your clock is too far out from the actual time then this will fail and you may see something like this in the syslog file:
ntpd[263140]: synchronized to <46.249.47.127>, stratum 1
ntpd[263140]: time correction of <54423> seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
[info 'ha-eventmgr'] Event 91 : NTP daemon stopped. Time correction 1206 > 1000 seconds. Manually set the time and restart ntpd.
The situation was that my VMs were synchronising their time to the ESXi host’s on every reboot, meaning that some important secure system services (in Windows 2008 in particular) were not starting. There isn’t the facility to do this on the DCUI (Direct Console User Interface – the yellow and black screen) so here’s the gen on how to achieve this using the command line.

My first endeavours were using the “date” command, as I’m used to doing in Linux, unfortunately these were met with the error:

~ # date 100410112014
date: can't set date: Function not implemented
Sat Oct  4 10:11:00 UTC 2014

OK, it’s being pernickety so lets use the “-s” flag to SET the time:

~ # date -s 041010112014
date: Setting date not supported; use <esxcli system time set>

Now we’re getting somewhere. The command takes the following parameters:

Usage: esxcli system time set [cmd options]
Description:
set                   Set the system clock time. Any missing parameters will default to the current time

Cmd options:
-d|--day=<long>       Day
-H|--hour=<long>      Hour
-m|--min=<long>       Minute
-M|--month=<long>     Month
-s|--sec=<long>       Second
-y|--year=<long>      Year

So, to set the system time to 10th April 2014, 10:18 (am):
~ # esxcli system time set -d 10 -H 10 -m 18 -M 04 -y 2014

Also, make sure that we also set the hardware clock time as the system time will revert to this on a reboot:

~ # esxcli hardware clock set -d 10 -H 10 -m 18 -M 04 -y 2014     <- sets the hardware clock to 10th April 2014, 10:18 (am)

To check the hardware and system time we can use the following commands:

esxcli hardware clock get
esxcli system time get

Job done! Now move on to setting the time automatically using NTP.

VMWare: VMWare Workstation Download Links

This article provides direct download links for the trial versions of VMWare Workstation for convenience: