<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Configure a time server for Active Directory domain controllers ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-340718/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-20T00:00:36-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Easy Solution]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3492904]]></link>
        <description><![CDATA[Time sync uses UTC, so time zones remain intact.You really should sync with the PDC emulator which, in turn, syncronises from an NTP server (preferably not time.microsoft.com which is out of sync half the time).In addition, computers sync with their authenticating DC, not with the PDC emulator. The PDC emulator is the authoratative time source for the domain and is the server that other DC's will sync with, but member servers and client computers will sync with their authenticating DC.PiyushLepide.com]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3492904]]></guid>
        <dc:creator><![CDATA[Piyush.Agrawal]]></dc:creator>
        <pubDate>Wed, 07 Sep 2011 05:09:50 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[PDC Emulator]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3474840]]></link>
        <description><![CDATA[according to Microsoft, time sincronization is the job of the PDC emulator http://technet.microsoft.com/en-us/library/cc756161(WS.10).aspx. The PDC emulator role is one per domain. Other DCs go after it as a source of time. It should be set to use the NTP protocol and all other PC's in the domain (including member servers) should be set to use the NT5DS protocol to sync from domain hierarchy. This is what should be pushed by a GPO - client targeting of a time source and not the AD's.As for the question, I would go for an in house fabric if one exists, if not I would go for an external reliable time source. Here in Brasil we use the ntp.br servers.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3474840]]></guid>
        <dc:creator><![CDATA[NassimJD]]></dc:creator>
        <pubDate>Thu, 21 Jul 2011 10:49:42 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[thank you for ur info]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3423176]]></link>
        <description><![CDATA[hi, very good article, its high valuable.. thank you very much...........http://serveradministrators.blogspot.com/]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3423176]]></guid>
        <dc:creator><![CDATA[ganesank123]]></dc:creator>
        <pubDate>Mon, 28 Feb 2011 07:19:19 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I will update my records and recommendations!]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3417374]]></link>
        <description><![CDATA[Thanks for the heads up. I have been using the ntp2.usno.navy.mil address since the late nineties and it has always worked well. Apparently about 7 years ago they changed their access policies and I never had a reason the check it. I like the pool.ntp.org address you provided much better, too. It has a pool of over 2000 time servers and picks the one closest to your geographic location that is available for your time request. So much technology and so many changes .. love it .. it keeps your interest and provides job security!It reminds me of the IPv4 to IPv6 migration but without the advertisements! That was a geeky joke, maybe no the best.Try this one - &quot;data is just a bunch of ones and zeros .... and an ocassional two&quot;Thanks again for sharing more current information with me/us.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3417374]]></guid>
        <dc:creator><![CDATA[davidsont@...]]></dc:creator>
        <pubDate>Wed, 09 Feb 2011 07:45:31 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Microsoft view through a window!]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3417197]]></link>
        <description><![CDATA[http://technet.microsoft.com/en-us/library/cc773013%28WS.10%29.aspx&quot;Although the Windows Time service is not an exact implementation of the Network Time Protocol &quot;&quot;The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs and is not supported by Microsoft as such. For more information, see Microsoft Knowledge Base article 939322,&quot;]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3417197]]></guid>
        <dc:creator><![CDATA[DGermantr@...]]></dc:creator>
        <pubDate>Tue, 08 Feb 2011 18:06:37 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I disagree on other DCs syncing externally]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3416632]]></link>
        <description><![CDATA[Nope every DC that is not the PDC emulator should be set to NT5DS as well as every Member Serverhttp://technet.microsoft.com/en-us/library/cc786897(WS.10).aspxhttp://technet.microsoft.com/en-us/library/cc758905(WS.10).aspx]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3416632]]></guid>
        <dc:creator><![CDATA[Vern Anderson]]></dc:creator>
        <pubDate>Mon, 07 Feb 2011 07:36:39 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[limit size of time adjustment]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413705]]></link>
        <description><![CDATA[You also need a policy on all machines to limit how far your time will jump on an update. If you get a bad time value that jumps your time 300+ years in to the future then corrects by jumping back your domain will be bricked. Please give a full  researched story - we are still finding oddites over a year later after recovering from this. see http://support.microsoft.com/kb/884776]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413705]]></guid>
        <dc:creator><![CDATA[Maurice Butler]]></dc:creator>
        <pubDate>Thu, 27 Jan 2011 12:20:44 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Dont contact StratumOneTimeServers]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413427]]></link>
        <description><![CDATA[ntp2.usno.navy.mil  is a StratumOneTimeServers, restricted time server and should NOT be contacted.use pool.ntp.orgPlease see NTP.org for more details.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413427]]></guid>
        <dc:creator><![CDATA[DGermantr@...]]></dc:creator>
        <pubDate>Wed, 26 Jan 2011 17:36:36 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Determining the time source being used with &amp;quot;w32tm /monitor&amp;quot;]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413336]]></link>
        <description><![CDATA[Using &quot;w32tm /monitor&quot; displays how time sources in a domain are configured.  I have been using  time-B and time-C.timefreq.bldrdoc.gov for so many years, and have become so complacent in their reliability that I've neglected them completely.  I have two time servers using the two different locations, and everything else pointing to them, so that I could, in theory, compare, isolate and recover from any external server failure.  The command along with &quot;w32tm /tz&quot; is especially useful on workstations purportedly in a domain, when users claim their clock is wrong.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413336]]></guid>
        <dc:creator><![CDATA[ToR24]]></dc:creator>
        <pubDate>Wed, 26 Jan 2011 12:31:22 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[All Domain Controllers? or those with PDC role only?]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413312]]></link>
        <description><![CDATA[Hey Rick, I noticed two snippets:&quot;From there, you can configure Active Directory domain controllers with the PDC emulator role in a domain to use this list of servers explicitly for their time&quot;&quot;I recommend applying this configuration to all domain controllers and possibly even making it a Group Policy object as a startup script for the \Domain Controllers organization unit within Active Directory.&quot;Unless I am losing my memory, Isn't there only one DC in any child (or root) domain that carries the PDC FSMO role for that domain?So If one has two or more DCs for any given domain in a forest, shouldn't this be specific to the PDC role holder only?http://www.petri.co.il/understanding_fsmo_roles_in_ad.htmAlso, if you set the PDC Role holder DC in the forest root to be reliable and pointing at an external pool of NTP servers or a hardware clock solution for the enterprise, isn't that the only one you need to worry about?All DCs whether Peer in the forest root, or in child domains will reference the Authoritative and Reliable DC in the root, and AD will make sure that behavior is replicated to themAll workstations in the child domains will choose a domain-local DC to synchronize their time tohttp://support.microsoft.com/kb/816042a discussion on the subject:http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/1a83420e-7a43-46b8-8df4-e0354480a4b0]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413312]]></guid>
        <dc:creator><![CDATA[cbutler@...]]></dc:creator>
        <pubDate>Wed, 26 Jan 2011 12:11:25 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Time - One Source needed]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413185]]></link>
        <description><![CDATA[I have always found it best to use the Domain Controller as the only network source for time synchronization in a Windows AD environment. Using Group Policy you can tell all computers/servers on the network to use one source for time which should be the Domain Controller. On that box I have always used the source ntp2.usno.navy.mil and rarely get an exception in the Event Viewer for NET Time. Usually means some type of network connectivity issue with the internet if I see any exceptions.It has always worked well for me for more than the past decade. Share some new technology with me if you have something.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-340718-3413185]]></guid>
        <dc:creator><![CDATA[davidsont@...]]></dc:creator>
        <pubDate>Wed, 26 Jan 2011 06:59:49 -0800</pubDate>
    </item>
    </channel>
</rss>

