Hello Oliver,
I would first investigate potential conflicts between domain time synchronization and hypervisor time integration, especially on virtualized or VDI endpoints.
Check whether Hyper-V or VMware Time Synchronization is continuously adjusting the guest clock while Windows Time Service uses the domain hierarchy (NT5DS). Next, review the Microsoft-Windows-Time-Service/Operational event log, particularly Events 35, 37, and 50, and compare the time source before and after logon using w32tm /query /source and w32tm /query /status.
You can also run w32tm /monitor to compare time across domain controllers and inspect the W32Time configuration for unexpected GPO overrides. Avoid changing polling intervals until the actual time source conflict is identified.
If the issue also occurs on physical workstations, investigate BIOS/UEFI firmware, hardware timers, and possible CMOS battery issues.
Best regards,
Harry P.