Windows 11 pro 22H2 does not sync time via NTP from UCS 5.2-0 Samba/AD DC after domain join. Cause currently unknown. In contrast: A Windows 10 pro 22H2 does correctly recognize the UCS 5.2-0 Samba//AD (S)NTP servers and configures the client to sync from it. Interesting commands: w32tm /query /source ## should output the FQDN of one of the UCS Samba/AD DCs. Under Windows 11 this (run as DOM\Administrator) showed "Local CMOS Clock". w32tm /monitor ## should show all detected NTP servers Windows 11: "GetGcList failed with error code: 0x8007054B" Note: ^^ This command shows this warning (in Windows 10), but that seems to be harmless: > Warning: > Reverse name resolution is best effort. It may not be > correct since RefID field in time packets differs across > NTP implementations and may not be using IP addresses. w32tm /resync /rediscover ## should doe just that without error. See also Bug #24953 / Bug #29527 as well as the recent fix in UCS 5.2-0: Bug #57147 Proposed next steps with this bug: 1. Check how Windows 11 22H2 behaves with UCS 5.0-9 (and the old ntp server) 2. Research/check if newer releases of Windows 11 don't exhibit this problem 3. Research/debug the origin of this behavior
Ok the client was configured for DHCP, maybe that interfered (using from dynamic IP range plus two DNS servers, primary and replica). After switching back to static IPv4 and rebooting the time sync works again.