Announcement

Collapse
No announcement yet.

Windows Time Service

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows Time Service

    Hi,

    I am reading an article about the Windows time service and how it can cause client authentication issues if it is not working correctly.

    I have read a Technet article about how to configure the client although it states some clients can be set to use their own source or cmos settings.

    The questions I have are:

    How can you check that the PDC is being used to inform the clients and from what source. What is stopping the clients from changing their time if the user is not locked out.

    Thanks

  • #2
    Re: Windows Time Service

    In an AD domain all clients automatically sync their time with the DC that holds the PDC Emulator role. No manual configuration of the clients is needed. If a user changes the time, it will automatically resynch to the DC after a few minutes. You can sync your DC with an external time source if you choose, although it's not required. If you only care about time accuracy relative to your internal domain then you don't need to do anything. If you want to make your internal time accurate relative to the outside world then sync your DC to an external time source.

    Comment


    • #3
      Re: Windows Time Service

      Hi Simonsays,

      The following table summarizes how the W32Time hierarchy works, starting from the external source.


      1
      Locally connected hardware clock (optional)

      Internet time server (optional)

      2
      PDC Emulator in forest root domain

      3
      Other domain controllers in forest root domain

      PDC Emulators in child domains

      4
      Workstations and member servers in forest root domain

      Other domain controllers in child domains

      5
      Workstations and member servers in child domains


      The polling process is initiated when W32Time starts on the client and is repeated every 45 minutes by default. If clocks are determined to be synchronized for three consecutive polls, the polling interval is increased to every 8 hours.

      Ref: http://www.windowsnetworking.com/art...e-Service.html
      Caesar's cipher - 3

      ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

      SFX JNRS FC U6 MNGR

      Comment


      • #4
        Re: Windows Time Service

        Guys,

        That has answered my questions - thanks for the clear explanations!

        Comment


        • #5
          Re: Windows Time Service

          Originally posted by joeqwerty View Post
          In an AD domain all clients automatically sync their time with the DC that holds the PDC Emulator role. No manual configuration of the clients is needed. If a user changes the time, it will automatically resynch to the DC after a few minutes. You can sync your DC with an external time source if you choose, although it's not required. If you only care about time accuracy relative to your internal domain then you don't need to do anything. If you want to make your internal time accurate relative to the outside world then sync your DC to an external time source.
          UNLESS you live in a part of the world that has changed Daylight Times and the Daylight patch hasn't been installed yet. Then the Server time could be correct but the client time will keep going out of sync no matter how many times you change the client time. (Having NET TIME in a logon script also doesn't help )

          Hope this hasn't caused any confusion.
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment

          Working...
          X