What group policy is responsible for the transition to summer time and back?

Actually the question is which group policy is responsible for enabling this option? windows server 2016.
Joined the server and was surprised that the times are off, googled added policy, but the option is never activated. Or is there a patch that will include? I know that MS is such a practice.
March 19th 20 at 08:54
2 answers
March 19th 20 at 08:56
It's not really group policy, so "jammed" in the "list of time zones" that come with updates Windows.

Actually on the screenshot - the bottom switch is the same.

If the times are off, so no one time zone, and "in this country," every year the idiots in the Duma, the government and other so-called "power structure" then enter, then cancel the transition... :(
If you pay attention to the inability to turn off "Set time automatically", it can be assumed that the computer in the domain, which manages the synchronization. - Vernice commented on March 19th 20 at 08:59
@Vernice, (I noticed) Highly unlikely. Most likely disabled the "update time zones".
well and the fact that the computers in the local network must be synchronized time is right and normal, and then begins a terrible collision. - verona_Hau commented on March 19th 20 at 09:02
@verona_Hau, Yes you need to look w32tm /query /peers. - Vernice commented on March 19th 20 at 09:05
March 19th 20 at 08:58
what group policy is responsible for enabling this option? windows server 2016
The consequences of entering the computer to the domain. The latter, as the last thing, would want that for the computers in it was synchronized time. Documentation: accurate time, Windows Server 2016.
In theory, everything goes just when you type in the domain on the computers settings are configured automatically and all the client stations begin to synchronize its time with domain controller on which they are authenticated. In turn, the domain controllers are synchronized with the controller on which the FSMO role is the PDC. By default, the PDC is synchronized with time.windows.com and it must be manually set to the desired source. To understand the current situation, it is possible to consistently run the command w32tm /query /peers on the workstation to the domain controller from which it takes time for the PDC.

Find more questions by tags Windows ServerWork with date / time