Sounds like EST with a 6 hour offset would put them in UTC time. Or, am I going backwards?
I have a domain with many clients in and many clients out of that zone since our scientific data acquisition machines need UTC time while the rest of the domain uses local time (wherever that may be). I haven't figured this out yet LeeW, but changing zones doesn't seem to effect kerberos authentication, however being out of time synch by more than the +/- 5 minute synchronization flag of the PDCe does. Maybe you can shed some light on that subjet.
Now I have a time server, so your application may be different in a way. I use Symmtime to synch to a time server. Then on the clients I need to be in a different time zone, I choose to change the zone. That does change the system clock zone and synchronizes the system clock of the client PC to my time server that I configured in Symmtime. But, for you, it will synch your client to an outside time server of your choosing and could put you out of synch with your PDCe unless your PDCe is synched up to the same outside time server.
In my personal experience, changing the time zone doesn't screw up kerberos authentication. However, changing the system clock time does.
Main Topics
Browse All Topics
by: leewPosted on 2009-05-27 at 04:38:27ID: 24481847
TIME is CRITICAL to a Windows domain - the time on the workstations MUST match the time on the servers (within a few minutes) or Kerberos authentication will FAIL and users won't be properly authenticated to the domain. The PDC emulator is in charge of time sync for the domain. Change the time there and disable it's internet time sync and that should do as you need. BUT WHY do you need the time to be six hours earlier? Time Zone issues?