Time Service Spike State Issue RRS feed

  • Question

    we deployed PDC Emulator on a hardware Domain Controller. DCs are based on Windows Server 2016.
    We have exactly the problem which is described in a Microsoft KB article:
    Unfortunately Fix-Tool from Microsoft did not solve the issue.
    Microsoft describes also the following workaround in the same article:
    If you want to use "SpecialPollinterval", you should change the following registry: 
    Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config 
    Value: MinPollInterval 
    Type: DWORD 
    To avoid this issue, the registry key should apply conditional expression as follows: Conditional expression: SpecialPollInterval<(2^MinPollInterval)*(HoldPeriod+1) 
    Domain member computer has default values:
    But which value for "MinPolInterval" and "HoldPeriod" should be set?
    I am confused.
    Best regards

    Wednesday, July 17, 2019 6:36 AM

All replies

  • Hiya,

    So... You have configured your PDC to synchronize with an internal time source and your clients are experiencing SPIKE state on your clients or what exactly is the issue?

    Standard configuration in a domain should be:

    1: All domain members(Including other domain controllers) mest use PDC(Primary Domain Controller) as NTP source, that is done using the NT5DS Type registry key, which is default.

    2: Your PDC should then synchronize with an reliable external time source.

    If you experience time scews on your client systems, which leads to the above time state, your should investigate why that is the case. (Virtual environments might suffer from additional time source syncs in various ways)

    Wednesday, July 17, 2019 8:57 AM
  • Hi Jesper,

    we use NTP server in our infrastructure a s time server. PDC gets the time from these servers.

    Actually we have no issue, and are wondering that Microsoft Active Directory Assessment check tells that "we have a problem". It reports:

    "Windows Time service does not correct the time if the service gets into a spike state, where the authoritative time server is more than a set number of seconds out from the server’s current time. Windows Time Service therefore considers the configured NTP time source to be unreliable and the clock on the server can drift."

    We checked all and could not find any problem. We applied also Fix for that as Microsoft decribed in KB article. Nothing is changed.

    It can be a bug in AD Assessment perhaps?!

    I don't know.

    Best regards


    • Edited by _Birdal Wednesday, July 17, 2019 10:19 AM
    Wednesday, July 17, 2019 10:18 AM
  • Hi,

    Does indeed sound like it. I mean quite some settings changed with Windows time Service in Windows Server 2016, so it could be the assessment report is wicked in that direction.

    Wednesday, July 17, 2019 11:18 AM
  • Hi Jesper,

    I know this MS article.

    But it does not help us, because we don't know why AD Assessment claims.

    Best regards


    Wednesday, July 17, 2019 12:32 PM
  • Hi,

    Here are some advice :

    Check the configuration in your environment  by running:

    w32tm /query /status

    w32tm /query /configuration

    Also the pdc setting:


    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config

    Key Name: AnnounceFlags

    Type: REG_DWORD (DWORD Value )

    Data: 0x5


    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type

    Key Name: Type

    Type: REG_SZ(String Value)

    Data: NTP


    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

    Key Name: NtpServer

    Type: REG_SZ(String Value)

    Data: Peers,0x9

    Then we would talk about the solution later

    Best Regards,


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact

    Thursday, July 18, 2019 6:59 AM
  • Hi Fan,

    all is correct on PDC.

    Best regards


    Thursday, July 18, 2019 2:16 PM
  • Hi,

    If all the client and pdc time and authentication are  in a normal state, then i would suggest you observe for a while.

    Best Regards,


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact

    Friday, July 19, 2019 3:21 AM