Server Time Zone configuration
-
Depending on the services it provides and the area, I'd say the time zone of the location it's providing services to.
-
If providing services to multiple time zones, the only option that makes sense to me is the physical location of the server.
-
@eddiejennings said in Server Time Zone configuration:
I'd like to get your opinions on what time zones you set for your servers. Do you tend to have them set on UTC, the time zone that's local to wherever you'll be managing them, or the time zone where the server is physically located (makes the least sense to me)?
I set it up to the time Zone of the location. Microsoft doesn't care if another server is in another time zone as long as the UTC is correct on both ends.
-
I'm a UTC guy. Servers aren't things with "locations" in most cases. The idea that a service exists in a physical location is normally a weird one.
-
And daylight savings time for servers is even more strange.
-
Doesn’t it depends if you are using Linux or Windows?
-
@black3dynamite said in Server Time Zone configuration:
Doesn’t it depends if you are using Linux or Windows?
yes.
-
@black3dynamite said in Server Time Zone configuration:
Doesn’t it depends if you are using Linux or Windows?
I'm not sure. I would be curious how AD and kerberos would handle a domain controller set to UTC with client machines set to a local time zone.
-
For Windows look at this:
-
@black3dynamite said in Server Time Zone configuration:
Doesn’t it depends if you are using Linux or Windows?
Why?
-
@dbeato said in Server Time Zone configuration:
For Windows look at this:
That seems to be concerned with putting the hardware to UTC, but the display to local. I do all to UTC.
-
@scottalanmiller said in Server Time Zone configuration:
@dbeato said in Server Time Zone configuration:
For Windows look at this:
That seems to be concerned with putting the hardware to UTC, but the display to local. I do all to UTC.
So what is your Time now on your computer?
-
-
@eddiejennings said in Server Time Zone configuration:
....or the time zone where the server is physically located (makes the least sense to me)?
This seems to be the most common thing that I see people using, too.
-
It doesn't matter what time zone the DC is set to, so long as the time is correct.
Each Windows client PC is responsible for it's own time zone setting.
Our DCs are on-prem, and using Pacific time, while domain clients can be anywhere in the world and use their own time zone setting.
-
@obsolesce said in Server Time Zone configuration:
It doesn't matter what time zone the DC is set to, so long as the time is correct.
Each Windows client PC is responsible for it's own time zone setting.
Our DCs are on-prem, and using Pacific time, while domain clients can be anywhere in the world and use their own time zone setting.
Assuming you have a DC. Even if you have stand alone boxes though, UTC works great.
-
The other point was that if you have, a web server for example, serving websites to the whole world, just use UTC... or the time zone of where it's physically located if that makes management easier for you. Time zones don't ever matter... only having the correct time for the time zone it is set for.
-
@obsolesce said in Server Time Zone configuration:
The other point was that if you have, a web server for example, serving websites to the whole world, just use UTC... or the time zone of where it's physically located if that makes management easier for you. Time zones don't ever matter... only having the correct time for the time zone it is set for.
And the correct time for the person that has to interpret them. That's why I like UTC, it avoids confusion by using a standard that everyone knows and understands. Use basically anything else and you have teams trying to figure out offsets, time of year, etc.
-
There's an RDS farm at work where the time zone is set to where the server is physically, so depending on which server you happen to hit, the time displayed is different. Doesn't make any sense to me.
-
What does BIOS time use local time or UTC?
