dleskovecI have a client on Windows 7 Professional machine that is on a domain (connected to a DC) and does not show the Internet Time tab, when looking at the Date and Time Settings.
The time on the machine is slightly off but not by much and the user always receives the error message that the date and time settings are not correct and hence does not get by the authentication. I have gotten their installation to work by manually changing their time by a minute or so.
Is there a more permanent solution to this given the Internet Time window does allow to sync to network time? Or will I continue to have this problem if the DC time is not synced to the network time?
dleskovec
TurboActivate and LimeLM aren't sensitive to a minute or 2 of drift. In fact, we count on it to happen. What's more likely the case is that the timezone is incorrect.
So the time needs to be accurate (date / timezone / and time need to be correct), but they don't have to be perfect.
dleskovecTime zone was correct on the machine. The only change I made to the machine to get it to work was change the time to match the time from my machine (Windows 10, using internet time). The time changed by roughly 1 minute and 30 seconds to a 2 minute change but nothing more.
Is there a limit that the time could be off? Which internet time server do you check against? time-a.nist.gov?
>> "The time changed by roughly 1 minute and 30 seconds to a 2 minute change but nothing more."
Then the problem is the machine booted with a wildly inaccurate time (because TA / LimeLM account for drift in computer clocks). Just reboot the machine.
>> "Is there a limit that the time could be off?"
Yes, and it depends on the function and different conditions. But even 30 minutes off and you should be fine.
>> "Which internet time server do you check against? time-a.nist.gov?"
Our own servers.
