Subscribe to my RSS Feed
Join 2,575 other subscribers
My ramblings on the stuff that holds it all together
From time to time you may have a requirement to set the time and date of a virtual machine to a date in the past, to replicate a time-sensitive production issue or to work around expiry of a temporary license key.
WARNING: DO NOT DO THIS WITH A MACHINE WITH ANY SORT OF CONNECTIVITY TO THE OUTSIDE NETWORK – you could get into a world of pain, and some applications don’t work well if you move the time around if they do some sort of internal comparison – so use at your own risk!!
In my case – I had some configuration information stored in an eval build of a product that had since expired installed inside a VM and I wanted to be able to extract it, I was unable to do this without running the application as it was in a proprietary format so I needed temporary access to that application.
The steps that worked for me are:
rtc.startTime = "YourValue"
tools.syncTime = "FALSE"
time.synchronize.restore = "FALSE"
time.synchronize.resume.disk = "FALSE"
time.synchronize.resume.memory = "FALSE"
time.synchronize.shrink = "FALSE"
(note: if you have more than one tools.syncTime=”FALSE” entry in your .VMX file remove one of them)
Credit to this post for the original .vmx entries
You mean “YourValue” what format I need to put it in M/D/Y, or M.D.Y or D.M.Y or D/M/Y
Very helpful. A couple comments:
1: in windows 2008 there was a task called Time Sync, it was setup to run once a week so I deleted it just in case.
2: In order to re-enable the VMware tools I had to add the following:
time.synchronize.tools.startup = “FALSE”
time.synchronize.tools.enable = “FALSE”
time.synchronize.resume.host = “FALSE”