Windows AD 2012 - Changing Time Zone on member servers

I have a 2012 domain on which I have been seeing large numbers of 4625 errors.

In looking for a resolution I have found a likely cause, which is that though time is sync'd across all servers the Domain Controllers are set to UTC whereas all member servers are set to UTC London, Dublin with DST. On all member servers the time is therefore currently one hour ahead of the DCs.

I can go onto each member server and change the timezone but what will the impact be on, for example, the SQL DB servers as they are obviously storing events against the date/time. I assume that I am going to just get events being logged during an hour for which events have already been logged and there is nothing I can do about that. Is that correct ?

TIA
rob prestonAsked:
Who is Participating?
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
The time is stored as Microsoft Time which is seconds past the epoch date in UTC  the timezone only converts this when it displays the time according to the TimeZone.

TimeZone EST5EDT
EDTTimeZone UTC
UTC
0
 
rob prestonAuthor Commented:
David,

Thanks for the reply. Would I be correct , then, in assuming that the same process applies not only to timestamps within the file system but also to records within the SQL DB ?
0
 
David Johnson, CD, MVPOwnerCommented:
DateTime is always stored internally as seconds past an epoch date.
0
 
David Johnson, CD, MVPOwnerCommented:
answered
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.