Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » Windows Time Drift
Windows Time Drift [message #331051] Mon, 30 November 2009 06:13 Go to next message
Rajnish  is currently offline Rajnish
Messages: 17
Registered: August 2009
Junior Member
I've set up a NTP Server on Linux and want to configure all the servers
,domain controllers to fetch the time source.However i want the servers to
update the time in a slow manner maybe sync to all should be completed in a
week's time.Is this possible on windows servers to configure this option..how
can we do this as some reporting servers also exists and are lagging on time
to the extent of 20 min which will affect in the reports generation..Can
anyone help on this
Re: Windows Time Drift [message #331054 is a reply to message #331051] Mon, 30 November 2009 06:17 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
The ONLY server that should be getting its time externally is your PDCe.
All clients should be getting there time from a dc within their site and all
other dc's should be sync'ing their time with the PDCe.

Fsmo list
netdom query fsmo

Setup PDCe (Follow this exactly as described)
http://support.microsoft.com/kb/816042

Troubleshooting time on a PDCe
http://technet.microsoft.com/en-us/library/bb727060.aspx

Set debug logging
http://support.microsoft.com/kb/816043/en-us

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Rajnish" <Rajnish@discussions.microsoft.com> wrote in message
news:D0810C5F-3353-433E-BF3D-5E292F8F4BC2@microsoft.com...
> I've set up a NTP Server on Linux and want to configure all the servers
> ,domain controllers to fetch the time source.However i want the servers to
> update the time in a slow manner maybe sync to all should be completed in
> a
> week's time.Is this possible on windows servers to configure this
> option..how
> can we do this as some reporting servers also exists and are lagging on
> time
> to the extent of 20 min which will affect in the reports generation..Can
> anyone help on this
Re: Windows Time Drift [message #331055 is a reply to message #331051] Mon, 30 November 2009 06:18 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Rajnish" <Rajnish@discussions.microsoft.com> wrote in message
news:D0810C5F-3353-433E-BF3D-5E292F8F4BC2@microsoft.com...
> I've set up a NTP Server on Linux and want to configure all the servers
> ,domain controllers to fetch the time source.However i want the servers to
> update the time in a slow manner maybe sync to all should be completed in
> a
> week's time.Is this possible on windows servers to configure this
> option..how
> can we do this as some reporting servers also exists and are lagging on
> time
> to the extent of 20 min which will affect in the reports generation..Can
> anyone help on this


It's either the time is synched, or it's not. There's no provisions to
'slowly' spread out the time sync feature. It works basically out of the box
without any needs to change registry entries or other settings other than
simply setting the time service on the DC holding the PDC Emulator FSMO Role
to get time from an outside or other source (such as your Linux time
server), then all machines in the domain will automatically find the time
service. Read teh following for more specicif information and how it all
works.

Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configur ing-the-windows-time-service-for-windows-server.aspx


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Re: Windows Time Drift [message #333372 is a reply to message #331055] Wed, 02 December 2009 09:45 Go to previous messageGo to next message
Mark Parris  is currently offline Mark Parris
Messages: 2
Registered: December 2009
Junior Member
I don't believe the algorithm has changed since 2000 but:

When the local clock offset has been determined, the following algorithm is
used to adjust the time:

If the local clock time of the client is behind the current time received
from the server, W32Time will change the local clock time immediately.

If the local clock time of the client is more than three minutes ahead of
the time on the server, W32Time will change the local clock time immediately.

If the local clock time of the client is less than three minutes ahead of
the time on the server, W32Time will quarter or halve the clock frequency for
long enough to bring the clocks into sync. If the client is less that 15
seconds ahead, it will halve the frequency; otherwise, it will quarter the
frequency. The amount of time the clock spends running at an unusual
frequency depends on the size of the offset that is being corrected.

Source:
http://download.microsoft.com/download/2/0/f/20f61625-7b2a-4 531-b007-1c714f1e51b7/wintimeserv.doc



"Ace Fekay [MCT]" wrote:

> "Rajnish" <Rajnish@discussions.microsoft.com> wrote in message
> news:D0810C5F-3353-433E-BF3D-5E292F8F4BC2@microsoft.com...
> > I've set up a NTP Server on Linux and want to configure all the servers
> > ,domain controllers to fetch the time source.However i want the servers to
> > update the time in a slow manner maybe sync to all should be completed in
> > a
> > week's time.Is this possible on windows servers to configure this
> > option..how
> > can we do this as some reporting servers also exists and are lagging on
> > time
> > to the extent of 20 min which will affect in the reports generation..Can
> > anyone help on this
>
>
> It's either the time is synched, or it's not. There's no provisions to
> 'slowly' spread out the time sync feature. It works basically out of the box
> without any needs to change registry entries or other settings other than
> simply setting the time service on the DC holding the PDC Emulator FSMO Role
> to get time from an outside or other source (such as your Linux time
> server), then all machines in the domain will automatically find the time
> service. Read teh following for more specicif information and how it all
> works.
>
> Configuring the Windows Time Service for Windows Server
> http://msmvps.com/blogs/acefekay/archive/2009/09/18/configur ing-the-windows-time-service-for-windows-server.aspx
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please check
> http://support.microsoft.com for regional support phone numbers.
>
>
> .
>
Re: Windows Time Drift [message #333717 is a reply to message #333372] Wed, 02 December 2009 14:51 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Mark Parris" <mark.parris@discussions.microsoft.com.> wrote in message
news:E3CF8F73-008C-45A0-B8E7-D9EF62D3C793@microsoft.com...
>I don't believe the algorithm has changed since 2000 but:
>
> When the local clock offset has been determined, the following algorithm
> is
> used to adjust the time:
>
> If the local clock time of the client is behind the current time received
> from the server, W32Time will change the local clock time immediately.
>
> If the local clock time of the client is more than three minutes ahead of
> the time on the server, W32Time will change the local clock time
> immediately.
>
> If the local clock time of the client is less than three minutes ahead of
> the time on the server, W32Time will quarter or halve the clock frequency
> for
> long enough to bring the clocks into sync. If the client is less that 15
> seconds ahead, it will halve the frequency; otherwise, it will quarter the
> frequency. The amount of time the clock spends running at an unusual
> frequency depends on the size of the offset that is being corrected.
>
> Source:
> http://download.microsoft.com/download/2/0/f/20f61625-7b2a-4 531-b007-1c714f1e51b7/wintimeserv.doc
>

Hi Mark,

Thanks for posting that. Yes, 2000 and 2003 time skew algorithm hasn't
changed. I updated my blog with the above link.

Thanks again!

Ace
Previous Topic:netlogon using wrong DC
Next Topic:Re: Ldife Import / Export problem
Goto Forum:
  


Current Time: Fri Jan 19 00:43:12 MST 2018

Total time taken to generate the page: 0.04564 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software