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.

Misc: Data source name not found and no default driver specified – ODBC / MySQL

Error: Data source name not found and no default driver specified

Platform: Windows7 (64 bit), MS Office 2010 (32 bit)

After downloading and installing the ODBC driver from oracle.com for 64 bit, this is the error observed when trying to access a MySQL server via Micrsoft Word VBA using a connection string:

conn.connectionString = "Driver={MySL ODBC 5.1 Driver};Server=10.1.1.10;Database=contacts; User=admin;Password=qwerty1"

Solution: The key issue here is that you must you must install the db drivers corresponding to the architecture of the application which is to use them, i.e.:

If you have 32 bit MS Office you MUST install the 32 bit MySQL drivers, if you have a 64 bit release then you MUST install the 64 bit drivers. There is absolutely no harm in installing both!

Notes: To access the 64 bit ODBC manager, pull up “Data Sources (ODBC)” from the start menu, to access the 32 bit manager, run the following: “C:\Windows\SysWOW64\odbcad32.exe

In the ODBC managers, make sure that you have the drivers installed:

Data source name not found and no default driver specified

 

 

Misc: Resynchronise the HP 2.4 GHz Wireless Optical Mouse FHA3510

Totally off topic but if you’ve had the misfortune to have one of these stop working on you then never fear as the solution is below.

Symptoms:

The USB receiver is inserted and installs fine but one day the mouse appears to give up the ghost and no longer connect.

Cause:

The mouse has become disassociated with the receiver, there are no obvious “sync” buttons on the mouse. As th mouse functions on 2.4 GHz, it may become disrupted by anything else using this frequency band e.g. microwaves, bluetooth, cordless phones etc.

Fix:

Set the mouse close to the inserted USB receiver and hold down the button just behind the wheel – it has a little paper icon on it, as shown in the image below. The blue wheel LED will start to flash – keep holding the button until it has stopped blinking – your mouse is now functional again!

HP FHA3510 Mouse