Looks like there is an issue with VMware and their update 2 for ESX 3.5 where when the date gets to 12th August, ESX stops working: http://communities.vmware.com/thread/162377?tstart=0 The workaround is to manually reset the time back a day or two...