Your experience agrees with what was mentioned is some of the discussions I read before I posted the initial question. In cases where removing the VMWare Tools was mentioned, if I remember correctly, there was always a response identifying a command that was missing and advising against removing VMWare Tools (I can understand that - VMWare Tools are quite valuable), and then a subsequent response that all was ok after the missing command was implemented, with VMWare Tools still installed. I think I am using the full set of commands, but I was and still am hoping that something somewhere is missing.
The thing I don't understand is why VMWare tools has the Time Synchronization check box that doesn't seem to work, at least if it's supposed to do what I think. The other thing is the "rtc.startTime = " command; it's useless if the time that is set is quickly reset after a few seconds. I'm a new user, and a bug or badly implemented command seems a little incongruous with what I've seen so far with this nice application - I still think I'm the problem.
you maybe able to keep the vmware-tools if you use
monitor_control.restrict_backdoor = "true"
but I don't know for sure.
Other then that your vmx looks it has the relevant entries like I described them
I have never tested VMs that have the tools installed when setting a fixed start-time.
Thanks Continuum,I tried adding the "monitor_control.restrict_backdoor = "true" " to my .vmx file. Here's what I found:When I powered on the virtual machine, which is running an activated version of Windows XP, I got a message that Windows XP activation was required, and was returned to the Windows logon screen.I shut down VMWare Workstation, removed the "monitor_control.restrict_backdoor = "true" " command from the .vmx file, restarted Workstation, and started the virtual machine; it started normally - no Windows XP activation message.I shut down VMWare Workstation, and again added the command to the .vmx file; same activation problem, but this time I activated Windows XP. The activation was successful, but I noticed that the VMWare Tools icon is missing from the taskbar. BUT, it appears that the time Time Synchronization was disabled successfully. It appears that there is SOME VMWare Tools functionality. I can move the cursor from the host to the guest with the mouse, but I can't fit the the guest to the virtual machine window, even though I can resize the virtual machine window (if I remember correctly, I don't think it's possible to resize the virtual machine window without VMWare Tools installed). I tried to reinstall VMWare Tools, but the installation failed.So it appears there is partial success, but still some annoying glitches.By the way, before adding "monitor_control.restrict_backdoor = "true" " to my .vmx file, I had tried setting the time in the VMWare BIOS. This was not a success. Although the virtual machine starts with the modified BIOS time, it is quickly reset in the virtual machine to the host time, and when I subsequently check the BIOS, the time there is reset to the host time too.Thanks again and Best Regards
It appears that VMware Tools may be working as it's supposed to.
When I start the virtual machine, which is running Windows XP, during the startup process, the time is intially set as specified on the
rtc.startTime = 1074859200
command in my .vmx file.
During the startup process, the VMware Tools is initially disabled (it's over layed by a circle with a slash). As the startup process continues, VMware Tools starts, and the virtual machine time is reset to the host system time. This is in accordance with:
"These options do not disable one-time synchronizations done by VMware Tools for events such as tools startup, taking a snapshot, resuming from a snapshot, resuming from suspend, or VMotion. These events synchronize time in the guest operating system with time in the host operating system even if VMware Tools periodic time sync is disabled, so it is important to make sure that the host operating system's time is correct."
This does seem like a glitch in VMware Tools - it seems like it might be appropriate to not perform the initial synchronization if "rtc.startTime" is set. It DOES seem like the time synchronization is disabled apart from this initial synchronization. If I reset the time in Windows XP, the time does seem to remain set to the new value.
Evidently, there may be other ways to modify the synchronization (see the link); I haven't yet figured this out.
Just curious why do you need or want a Virtual Machine to always start at, Fri, 23 Jan 2004 12:00:00 GMT?
I did some testing on a Windows 7 Guest with VMware Tools installed and in conjunction with the following settings in the .vmx configuration file and disabling Guest OS Level Time Synchronization I found it to maintain the correct time as referenced by the value of rtc.startTime and not sync with the Host. Of course as usual YMMV.
rtc.startTime = "VALID_VALUE" tools.syncTime = "FALSE" time.synchronize.continue ="FALSE" time.synchronize.restore = "FALSE" time.synchronize.resume.disk = "FALSE" time.synchronize.resume.memory = "FALSE" time.synchronize.shrink = "FALSE" monitor_control.restrict_backdoor = "TRUE"