Skip to Main Content

My VMware setup

Main server: a Dell PowerEdge T110 II server (Intel Xeon E3-1230v2, 32 GB RAM, 512 GB SSD, 3 HDDs, 2 NICs) running 24/7 in my hallway, with VMware ESXi 5.5 installed.
Instructions for installing the (free) ESXi Embedded Host Client can be found at
I run all my Oracle development VM's on that server (most of those run CentOS, some Windows). Some Windows VM's as well; I do 90% of my daily work on one of those via Remote Desktop. And an OpenVPN Access Server Virtual Appliance takes care of VPN access (more info).
A highly recommended setup; it has been extremely reliable since I installed all that in 2013.

And to complete the server setup:
A HP ProLiant MicroServer G7 N54L with 6 GB RAM, Windows 10 and 1.5 GB HDDs (in RAID 5) acts as the (on-site, offline) backup server.
For off-site backups I use a couple of external HDDs.
Synchronization of data between the different machines on the network is handled by Resilio Sync (automatic) and SyncBack (manual).
For off-site backups I use a couple of external HDDs.
An APC UPS and Zyxel Armor Z1 AC2350 router complete the server setup.

2020 update: The ESXi server and UPS mentioned above were running 24/7, while not being used for much besides hosting my website. So when I moved my site to an OVH VPS, I switched those off. Saves some power - and noise :-)

VMware ESXi 5.1 vSphere Client - Installing on Windows 10

"Recently we have installed some dev machines using Windows 10 as the latest system by Microsoft. Since we’re using VMware ESXI 5.1, we wanted to use the vSphere client to access the VM host using this GUI. However, we ran into issues installing the vSphere setup to the brand new Windows 10 system.
The problem: You simply cannot get the client to install. At some point, the installer stops and you don’t see the window to show up anywhere on your desktop. If you check the window title in Task manager, it says something about contact your network administrator."

Unzip the installer file (using 7-zip) and manually install Microsoft .NET Framework and Microsoft Visual J# 2.0 x64 (located in the unzipped redist directory).

Source and more info:

VMware ESXi 5.5 vSphere Client- Scaling problems on Windows 10

If your mouse pointer doesn't match the cursor position in a VM console, making the VM quite uncontrollable, this probably has to do with Windows DPI settings.

For me (ESXi 5.5 on Windows 10 Pro build 1803 with a 4K monitor), this fixed it:
  • Locate the VMware vShpere Client (in my case this is at "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe").
  • Right-click and select Properties.
  • Go to tab "Compatibility" and click on "Change DPI Settings".
  • Under "High DPI scaling overrride", make sure "Override high DPI scaling behavior" is checked and set the "Scaling performed by" dropdown to "Application".
  • Click OK and Apply, and OK again.
The application doesn't look very good after this fix (all sorts of scaling issues, and things are very small on my 4K monitor) but at least it is workable.

Some more info (a bit outdated):

VMware Workstation Player - Scaling problems

Workstation Player (15.5) also has some scaling issues on my Windows 10 (2004) machine. If you resize the Player window of a CentOS 7 VM with a Gnome desktop (with VMware Tools installed) the cursor position goes haywire. And I suspect any other OS will have the same issue as well.
The fact that there are 2 external monitors attached to my laptop (and 1 internal of course), all with different resolutions and DPI's, probably doesn't help :-)

A partial solution is similar to the vSphere Client solution above, except that I needed to select "System" instead of "Application". "System (Enhanced): works as well.
It is not a 100% fix however; scaling the Player windows works fine now, but if you move the windows to another monitor the same issue occurs.

VMWare Workstation Player - Set default VM location

Open up the following file in a text editor:

Add this line, changing the path to your desired location:
prefvmx.defaultvmpath = "D:\VMs"

Save, restart VMWare Player, and your new location should work when creating a new VM.