Right Time Zone, wrong time

Mohamed jihad bayali 1,136 Reputation points
2023-04-27T16:39:57.1933333+00:00

Hello Team,

I hope you're doing fine,

I just set an ntp server for my client, and sync it sucessfully with the PDC emulator of the domain.

The sync is ok, the tests are good, i configure the correct timezone on the PDC, but it gives the incorrect date (1 hour less than the correct date), i tried to disable/enable the daylight saving time, but nothing change.

the time that i choose is Casablanca UTC +1, and i can't understand why i have this incorrect date.

As per my understanding, the NTP is delivering Time to the servers in UTC, and then based on the timezone configured on the clients machine, the time is calculated.

For my machine the timezone is correct (UTC+1) but the time on the machines is incorrect

Any ideas please?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-04-27T16:58:33.3233333+00:00

    You could check the results;

    Get-TimeZone
    
    

  2. Anonymous
    2023-04-27T17:53:12.0033333+00:00

    You could try;

    w32tm /unregister
    net stop w32time
    w32tm /register
    net start w32time
    w32tm /config /syncfromflags:domhier /update
    net stop w32time
    net start w32time
    

    Then check again.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Limitless Technology 44,766 Reputation points
    2023-04-28T14:13:02.42+00:00

    Hello there,

    To work around this issue so that the NTP client is enabled to sync with the NTP server after a SPIKE state, configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval.

    An NTP client computer that is running Windows Server editions or Windows Client editions may not correct the time if the following conditions are true:

    The NTP client syncs its time with the manually specified NTP server.

    The NTP client uses SpecialPollInterval as a polling interval.

    The time offset between the NTP client and the NTP server is greater than the LargePhaseOffset as configured in the NTP client.

    In this situation, the NTP client cannot correct its time even after waiting for SpikeWatchPeriod to pass.

    https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/specialpollinterval-polling-interval-time-service-not-correct

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.