A
AndreasAu
Guest
Hi all,
we in Europe just had the summer time adjustment and suddenly many of our users opened tickets, that their windows time is still one hour behind. Of course, we checked this and the settings look absolutely fine: GMT+1 (Berlin), automatically detect summer/winter time.
Every affected computer is currently out of office (no VPN either).
Digging deeper, they all use local CMOS as time provider. Wait, what?
GPO is set to activate ntp client and use default settings. This should (in my opinion) result in
- Use domaincontroller if available
- use time.windows.com if no DC available
But it does not work.
But as soon as I set type to NTP (instead of NT5DS), windows successfully uses time.windows.com as provider
So for me, this looks like the fallback of NT5DS does not work as it should.
As I cannot connect to the machines, I don't know the exact build, but they should all be 1903/1909 at Jan-March updates.
More...
we in Europe just had the summer time adjustment and suddenly many of our users opened tickets, that their windows time is still one hour behind. Of course, we checked this and the settings look absolutely fine: GMT+1 (Berlin), automatically detect summer/winter time.
Every affected computer is currently out of office (no VPN either).
Digging deeper, they all use local CMOS as time provider. Wait, what?
GPO is set to activate ntp client and use default settings. This should (in my opinion) result in
- Use domaincontroller if available
- use time.windows.com if no DC available
But it does not work.
But as soon as I set type to NTP (instead of NT5DS), windows successfully uses time.windows.com as provider
So for me, this looks like the fallback of NT5DS does not work as it should.
As I cannot connect to the machines, I don't know the exact build, but they should all be 1903/1909 at Jan-March updates.
More...