Disable VM Time Synchronization with ESXi Host Completely

By admin, April 16, 2021 18:40

Simply add the following lines to VM options

tools.syncTime 0
time.synchronize.continue 0
time.synchronize.restore 0
time.synchronize.resume.disk 0
time.synchronize.shrink 0
time.synchronize.tools.startup 0
time.synchronize.tools.enable 0
time.synchronize.resume.host 0


By admin, April 11, 2021 21:01


線條還是老車好看 911 RS 3.0 1974

By admin, April 9, 2021 14:44


點睇都係咁靚 1962 Le Mans Ferrari 250 GTO #3769GT

By admin, April 8, 2021 11:49


夢回賽車的黃金時代: 1964 Targa Florio Ferrari 250 GTO #3705GT

By admin, April 7, 2021 18:39



By admin, April 7, 2021 17:17



By admin, April 5, 2021 12:46


Winner of 1973 Targa Florio: Porsche 911 RSR 2.8

By admin, April 3, 2021 16:40


Symantec Endpoint Protection (SEP) failed to load new virus definition

By admin, April 3, 2021 11:41

Seems the old Windows Server 2003 is having trouble with recent SEP v12.1 virus definition updates.

Solution is simple by restarting the SEP service.

smc -stop
smc -start

Then manually update the definition will solve all the question marks.

Interesting! Windows Server 2019 working on ESX 4.1!

By admin, April 2, 2021 21:51


As expected, the installation process is almost identical to Windows Server 2012 and 2016. The key is to use BIOS version SLIC 2.5.

Except I’ve encountered a tricky problem that the valid license key won’t activate, it returns with “windows server 2019 error -xc004f069″.

It turns out the the source ISO is an evaluation copy, so all you have to do is to convert the Eval copy to Retail version by:

DISM /Online /Set-Edition:ServerStandard /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /AcceptEula

To determine upgrade path and other available edition:
DISM /online /Get-TargetEditions

For the evaluation/retail version of Windows Server 2016 Standard, you can also convert to the retail version of Windows Server 2016 Data Center using the same command and the appropriate product key.

DISM /Online /Set-Edition:ServerDatacenter /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /AcceptEula

Update: Apr 11, 2021

It turns out VM will lost its customized CPUID parameter after Veeam backup restoration, BIOS SLIC 2.5 parameter holds though.

So you have to add it back again, or the VM will keep crashing every now and then.

However, if the VM is deployed via template, then there is no problem at all.