Converge network time with Internet time

Our network time is currently 4 minutes fast and we want to converge it to an
Internet Time Source. We are running AD in a Windows 2000 environment,
although our DCs are 2003. We are about to upgrade AD to 2003. I understand
there may be problems associated with adjusting the time - can you point me
in the right direction, please?

point your dc's to a time server and the clients will adjust to the dc's
what problems with adjusting the time are you referring to?

"sluice" <(E-Mail Removed)> wrote in message
news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> Our network time is currently 4 minutes fast and we want to converge it to
> an
> Internet Time Source. We are running AD in a Windows 2000 environment,
> although our DCs are 2003. We are about to upgrade AD to 2003. I
> understand
> there may be problems associated with adjusting the time - can you point
> me
> in the right direction, please?
>

I understand that AD is not happy with reversing tthe time by more than a
second or so - it can cause records to have future dates/times

"seth" wrote:

> point your dc's to a time server and the clients will adjust to the dc's
> what problems with adjusting the time are you referring to?
>
> "sluice" <(E-Mail Removed)> wrote in message
> news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> > Our network time is currently 4 minutes fast and we want to converge it to
> > an
> > Internet Time Source. We are running AD in a Windows 2000 environment,
> > although our DCs are 2003. We are about to upgrade AD to 2003. I
> > understand
> > there may be problems associated with adjusting the time - can you point
> > me
> > in the right direction, please?
> >
>
>
>

can you show me an article that discusses that?
i'd be interested in reading it

"sluice" <(E-Mail Removed)> wrote in message
news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
>I understand that AD is not happy with reversing tthe time by more than a
> second or so - it can cause records to have future dates/times
>
> "seth" wrote:
>
>> point your dc's to a time server and the clients will adjust to the dc's
>> what problems with adjusting the time are you referring to?
>>
>> "sluice" <(E-Mail Removed)> wrote in message
>> news:76B76720-2103-4437-9E95-(E-Mail Removed)...
>> > Our network time is currently 4 minutes fast and we want to converge it
>> > to
>> > an
>> > Internet Time Source. We are running AD in a Windows 2000 environment,
>> > although our DCs are 2003. We are about to upgrade AD to 2003. I
>> > understand
>> > there may be problems associated with adjusting the time - can you
>> > point
>> > me
>> > in the right direction, please?
>> >
>>
>>
>>

It is not "seconds" but it does have to be within several minutes.

It also isn't all DCs,...it is the DC with the "pdc role". You set that
machine to what you want (manually, time source, whatever) and all others,
including the other DCs will sync to it. So you only have to deal with one
machine.

I don't have any articles to quote, but they should be easy to hunt down by
searching MS's site using key words like sync, time, "external source".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------




"sluice" <(E-Mail Removed)> wrote in message
news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
> I understand that AD is not happy with reversing tthe time by more than a
> second or so - it can cause records to have future dates/times
>
> "seth" wrote:
>
> > point your dc's to a time server and the clients will adjust to the dc's
> > what problems with adjusting the time are you referring to?
> >
> > "sluice" <(E-Mail Removed)> wrote in message
> > news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> > > Our network time is currently 4 minutes fast and we want to converge
it to
> > > an
> > > Internet Time Source. We are running AD in a Windows 2000 environment,
> > > although our DCs are 2003. We are about to upgrade AD to 2003. I
> > > understand
> > > there may be problems associated with adjusting the time - can you
point
> > > me
> > > in the right direction, please?
> > >
> >
> >
> >

Thanks for your reply, Phillip. So, am I to understand that there should be
no problem in putting the clock back on the "PDC" by 4 minutes? By that I
mean that when it all goes tits up, I can blame you?

"Phillip Windell" wrote:

> It is not "seconds" but it does have to be within several minutes.
>
> It also isn't all DCs,...it is the DC with the "pdc role". You set that
> machine to what you want (manually, time source, whatever) and all others,
> including the other DCs will sync to it. So you only have to deal with one
> machine.
>
> I don't have any articles to quote, but they should be easy to hunt down by
> searching MS's site using key words like sync, time, "external source".
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
>
> "sluice" <(E-Mail Removed)> wrote in message
> news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
> > I understand that AD is not happy with reversing tthe time by more than a
> > second or so - it can cause records to have future dates/times
> >
> > "seth" wrote:
> >
> > > point your dc's to a time server and the clients will adjust to the dc's
> > > what problems with adjusting the time are you referring to?
> > >
> > > "sluice" <(E-Mail Removed)> wrote in message
> > > news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> > > > Our network time is currently 4 minutes fast and we want to converge
> it to
> > > > an
> > > > Internet Time Source. We are running AD in a Windows 2000 environment,
> > > > although our DCs are 2003. We are about to upgrade AD to 2003. I
> > > > understand
> > > > there may be problems associated with adjusting the time - can you
> point
> > > > me
> > > > in the right direction, please?
> > > >
> > >
> > >
> > >
>
>
>

fyi
article 816042
"the PDC operations master at the root of the forest becomes authoritative
for the organization"


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> It is not "seconds" but it does have to be within several minutes.
>
> It also isn't all DCs,...it is the DC with the "pdc role". You set that
> machine to what you want (manually, time source, whatever) and all others,
> including the other DCs will sync to it. So you only have to deal with one
> machine.
>
> I don't have any articles to quote, but they should be easy to hunt down
> by
> searching MS's site using key words like sync, time, "external source".
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
>
> "sluice" <(E-Mail Removed)> wrote in message
> news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
>> I understand that AD is not happy with reversing tthe time by more than a
>> second or so - it can cause records to have future dates/times
>>
>> "seth" wrote:
>>
>> > point your dc's to a time server and the clients will adjust to the
>> > dc's
>> > what problems with adjusting the time are you referring to?
>> >
>> > "sluice" <(E-Mail Removed)> wrote in message
>> > news:76B76720-2103-4437-9E95-(E-Mail Removed)...
>> > > Our network time is currently 4 minutes fast and we want to converge
> it to
>> > > an
>> > > Internet Time Source. We are running AD in a Windows 2000
>> > > environment,
>> > > although our DCs are 2003. We are about to upgrade AD to 2003. I
>> > > understand
>> > > there may be problems associated with adjusting the time - can you
> point
>> > > me
>> > > in the right direction, please?
>> > >
>> >
>> >
>> >
>
>

What happens to the global catalogues in our UK, France & Germany domains if
I put the time back by 4 minutes?
What happens to France & Germany domains if I put the root PDC (in the UK)
back by 4 minutes?
What happens to our AD data if France & Germany suddenly move ahead by 4
minutes relative to us?
I don't think it is quite as simple as puting the root PDC time back into
sync with Internet time, sitting back and watching everything carry on as
normal but with the right time. I believe there is a command somewhere that
gradually corrects the clock by seconds every hour, allowing harmless AD
syncs between each correction.

"seth" wrote:

> fyi
> article 816042
> "the PDC operations master at the root of the forest becomes authoritative
> for the organization"
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > It is not "seconds" but it does have to be within several minutes.
> >
> > It also isn't all DCs,...it is the DC with the "pdc role". You set that
> > machine to what you want (manually, time source, whatever) and all others,
> > including the other DCs will sync to it. So you only have to deal with one
> > machine.
> >
> > I don't have any articles to quote, but they should be easy to hunt down
> > by
> > searching MS's site using key words like sync, time, "external source".
> >
> > --
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> > -----------------------------------------------------
> > Understanding the ISA 2004 Access Rule Processing
> > http://www.isaserver.org/articles/IS...cessRules.html
> >
> > Microsoft Internet Security & Acceleration Server: Guidance
> > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > http://www.microsoft.com/isaserver/t...dance/2000.asp
> >
> > Microsoft Internet Security & Acceleration Server: Partners
> > http://www.microsoft.com/isaserver/partners/default.asp
> > -----------------------------------------------------
> >
> >
> >
> >
> > "sluice" <(E-Mail Removed)> wrote in message
> > news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
> >> I understand that AD is not happy with reversing tthe time by more than a
> >> second or so - it can cause records to have future dates/times
> >>
> >> "seth" wrote:
> >>
> >> > point your dc's to a time server and the clients will adjust to the
> >> > dc's
> >> > what problems with adjusting the time are you referring to?
> >> >
> >> > "sluice" <(E-Mail Removed)> wrote in message
> >> > news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> >> > > Our network time is currently 4 minutes fast and we want to converge
> > it to
> >> > > an
> >> > > Internet Time Source. We are running AD in a Windows 2000
> >> > > environment,
> >> > > although our DCs are 2003. We are about to upgrade AD to 2003. I
> >> > > understand
> >> > > there may be problems associated with adjusting the time - can you
> > point
> >> > > me
> >> > > in the right direction, please?
> >> > >
> >> >
> >> >
> >> >
> >
> >
>
>
>

I don't know,...for all the "?"s

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"sluice" <(E-Mail Removed)> wrote in message
news:B0A8229E-DA06-42BD-8C88-(E-Mail Removed)...
> What happens to the global catalogues in our UK, France & Germany domains
if
> I put the time back by 4 minutes?
> What happens to France & Germany domains if I put the root PDC (in the UK)
> back by 4 minutes?
> What happens to our AD data if France & Germany suddenly move ahead by 4
> minutes relative to us?
> I don't think it is quite as simple as puting the root PDC time back into
> sync with Internet time, sitting back and watching everything carry on as
> normal but with the right time. I believe there is a command somewhere
that
> gradually corrects the clock by seconds every hour, allowing harmless AD
> syncs between each correction.
>
> "seth" wrote:
>
> > fyi
> > article 816042
> > "the PDC operations master at the root of the forest becomes
authoritative
> > for the organization"
> >
> >
> > "Phillip Windell" <@.> wrote in message
> > news:(E-Mail Removed)...
> > > It is not "seconds" but it does have to be within several minutes.
> > >
> > > It also isn't all DCs,...it is the DC with the "pdc role". You set
that
> > > machine to what you want (manually, time source, whatever) and all
others,
> > > including the other DCs will sync to it. So you only have to deal with
one
> > > machine.
> > >
> > > I don't have any articles to quote, but they should be easy to hunt
down
> > > by
> > > searching MS's site using key words like sync, time, "external
source".
> > >
> > > --
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > > -----------------------------------------------------
> > > Understanding the ISA 2004 Access Rule Processing
> > > http://www.isaserver.org/articles/IS...cessRules.html
> > >
> > > Microsoft Internet Security & Acceleration Server: Guidance
> > > http://www.microsoft.com/isaserver/t...dance/2004.asp
> > > http://www.microsoft.com/isaserver/t...dance/2000.asp
> > >
> > > Microsoft Internet Security & Acceleration Server: Partners
> > > http://www.microsoft.com/isaserver/partners/default.asp
> > > -----------------------------------------------------
> > >
> > >
> > >
> > >
> > > "sluice" <(E-Mail Removed)> wrote in message
> > > news:B067BE74-DC69-41FA-A3B2-(E-Mail Removed)...
> > >> I understand that AD is not happy with reversing tthe time by more
than a
> > >> second or so - it can cause records to have future dates/times
> > >>
> > >> "seth" wrote:
> > >>
> > >> > point your dc's to a time server and the clients will adjust to the
> > >> > dc's
> > >> > what problems with adjusting the time are you referring to?
> > >> >
> > >> > "sluice" <(E-Mail Removed)> wrote in message
> > >> > news:76B76720-2103-4437-9E95-(E-Mail Removed)...
> > >> > > Our network time is currently 4 minutes fast and we want to
converge
> > > it to
> > >> > > an
> > >> > > Internet Time Source. We are running AD in a Windows 2000
> > >> > > environment,
> > >> > > although our DCs are 2003. We are about to upgrade AD to 2003. I
> > >> > > understand
> > >> > > there may be problems associated with adjusting the time - can
you
> > > point
> > >> > > me
> > >> > > in the right direction, please?
> > >> > >
> > >> >
> > >> >
> > >> >
> > >
> > >
> >
> >
> >