<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx</link><description>Windows Time Service on a domain (referred to as 'Domain Synchronization' or 'Domain Sync' for short) is a huge topic. I will do my best to cover all of its aspects in this article, but some concepts won't be covered until a later date, and others still</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#4748967</link><pubDate>Wed, 05 Sep 2007 00:02:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4748967</guid><dc:creator>MSDN Blog Postings  » Keeping the Domain On Time</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/09/04/keeping-the-domain-on-time/"&gt;http://msdnrss.thecoderblogs.com/2007/09/04/keeping-the-domain-on-time/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9029764</link><pubDate>Mon, 03 Nov 2008 01:22:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9029764</guid><dc:creator>Alexis</dc:creator><description>&lt;p&gt;What happens if the root PDC gets the wrong time? will all computers in the domain get the wrong time?&lt;/p&gt;</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9030679</link><pubDate>Mon, 03 Nov 2008 06:10:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9030679</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Correct. If the PDC gets the wrong time, so will the rest of the comptuers in the forest. This is why in Server 2008 we started making a recommendation to set phase correction limits. The limits won't prevent the PDC from getting the wrong time, but they will prevent that bad time from filtering down to all of the other computers in the forest. Check this post for more information on the problem:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/w32time/archive/2008/02/28/configuring-the-time-service-max-pos-neg-phasecorrection.aspx"&gt;http://blogs.msdn.com/w32time/archive/2008/02/28/configuring-the-time-service-max-pos-neg-phasecorrection.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9835220</link><pubDate>Thu, 16 Jul 2009 09:56:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9835220</guid><dc:creator>Mark</dc:creator><description>&lt;P&gt;This all tries to be so clever it has no hope of working reliably and then when the time is wrong, you've got little hope of working out why.&lt;/P&gt;
&lt;P&gt;For my example right now, RODC server straight out of the box is 8 minutes different to the writeable DC on the network. It's so clever it has found some unreliable time source and being so clever I can't make it use the reliable time source that one would expect was the OBVIOUS choice.&lt;/P&gt;</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9835660</link><pubDate>Thu, 16 Jul 2009 17:03:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9835660</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Mark,&lt;/p&gt;
&lt;p&gt;There is nothing &amp;quot;clever&amp;quot; about w32time. I would agree that some of what w32time does can be difficult to understand, which is why I started this blog.&lt;/p&gt;
&lt;p&gt;Since your problem is unrelated to this post itself, I will need you to ask it in a different forum. If you are willing to post your problem on the Directory Services forum (&lt;a rel="nofollow" target="_new" href="http://social.technet.microsoft.com/Forums/en-US/winserverDS/threads"&gt;http://social.technet.microsoft.com/Forums/en-US/winserverDS/threads&lt;/a&gt;), I will be more than happy to help you out.&lt;/p&gt;
&lt;p&gt;I will be looking for your post.&lt;/p&gt;
</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9852383</link><pubDate>Wed, 29 Jul 2009 21:09:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9852383</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;The graphic in your article appears to be broken. It looks like it might be useful - can you take a look?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;</description></item><item><title>re: Keeping the Domain On Time</title><link>http://blogs.msdn.com/w32time/archive/2007/09/04/keeping-the-domain-on-time.aspx#9852395</link><pubDate>Wed, 29 Jul 2009 21:21:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9852395</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Matt,&lt;/p&gt;
&lt;p&gt;I've updates the graphic. Hopefully it won't move again.&lt;/p&gt;
&lt;p&gt;Thanks for letting me know!&lt;/p&gt;
</description></item></channel></rss>