" After all, Kerberos requires any two computers authenticating over the network to be within five minutes of each other, though it is configurable in Group Policy.
But does it really affect domain controllers if the DST is incorrect?
So, even though a client computer in Atlanta says it's and a server in the network in Seattle says it's (adjusted for time zone), the UTC on both is .
Microsoft could have made things simple and just had all computers report the UTC time and be done with it, but they decided to make it user-friendly and built a utility to convert UTC to "local time" based on the time zone selected.
UTC is a standard time that everyone agrees on, regardless of time zones.
It is generally considered synonymous with GMT (Greenwich Mean Time).
It doesn't answer all questions, but it addresses a lot of them.
Many admins have probably dealt with a time sync problem at one time or another where they have users that try to log in and get time synchronization errors.
While I don't have space to go into details about W32(I'll do that in a future article), it is important to note that this tool is available in Windows 20. To sync an XP or Windows Server 2003 machine, the command w32tm /resync will usually do the trick. Make sure you study the online help for the command when you use it.
So, here is what we know: OK, so now that we have all our clocks synchronized, along comes a daylight-saving time change (called "summer time" in some parts of the world). A utility called stores all the time zone information in the registry: is the name of the zone, such as Mountain Standard Time.
However, if you set your local time to be , conversion to UTC/GMT would put your clock at .