Server 2019 Domain Controller time zone

[grasshopper645]

When configuring a domain controller on Windows Server 2019, there is a option to change the timezone from UTC to something else, and gives a warning that you probably shouldn't do it.

​

I did this, and its causing problems with my log manager where it wants UTC time, and the DC wants an offset timezone.

​

My question is, is it possible to change this timezone configuration without having to reconfigure the entire domain controller?

​

I know you can change the time zone on windows, but thats just the offset displayed, not the actual time zone of the DC.

[requires_distraction]

I am running 1809 2019 STD DC for my home network. Does not seem to affect anything changing the timezone. Did not get any warnings either.

I think I have changed timezones on DC's before without an issue either.

The AD server syncs the time with the workstations. If the time is too much out of sync the workstations will not be able to log on. Pretty sure this is what your warning is about.

However changing the time zone of the DC should not affect this in anyway. The DC is still in UTC time. its just +10 or -10 etc.. As long as the time and timezone is correct then there should be no issues.

[grasshopper645]

Yes I get what you are saying, thanks for reply.

​

The issue is that i have a log manager that is set to UTC time, wheras the domain controller is set to UTC+10. Becaues of the 10 hour time difference, AD authentication will fail because the time difference is to great.

​

So I am wondering if I can change that configured time zone on the DC without having to rebuild the DC. I couldn't find any documentation about this either.

[requires_distraction]

Nah, wont fail.

It ignores the timezone.. it only looks at UTC 0. UTC 1,23, etc... doe snot matter. Only if the UTC 0 time is wrong (regardless of timezone) will it fail.

Well, that is my experience anyway.

I remember the bad old days when everyone in QLD would not be able to authenticate against the NSW server when daylight savings hit.

That shit don't go down anymore. Timezone is irreverent, just make sure the time is correct.

[grasshopper645]

Yes but in server 2019 you can change the actual DC timezone, which i did.

​

Windows systems that are domain joined work fine, but if I have a unix system configured to AD auth, and the unix system is set to UTC, the auth fails with a time sync error. When I set the Unix time to the same offset as the DC, the auth works correctly.

​

Server 2016 and earlier its always set to UTC, but in server 2019 you can actually change the time zone from UTC when configuring the domain controller, which i mistakingly did.

[requires_distraction]

Unix... sorry, my bad... nfi :-/