Re: NTP Question
- From: DevilsPGD <spam_narf_spam@xxxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 23:19:01 -0600
In message <uXDgcuYaHHA.5044@xxxxxxxxxxxxxxxxxxxx> "Herb Martin"
<news@xxxxxxxxxxxxxx> wrote:
"DevilsPGD" <spam_narf_spam@xxxxxxxxxxxx> wrote in message
news:d4sqv2pa2872qpi5q8jlmjonj65ajhdhqh@xxxxxxxxxx
Absolutely everything resolved itself once the time was fixed, which was
only a big deal because of the DST switch (And even then not a huge
complication in the grand scheme of what can go wrong with AD)
DST had almost nothing to do with "time" -- it was about DISPLAY of the
time since AD maintains time internally in UTC (aka GMT) form.
The "real" time in my timezone was 2:00am -0600 (MDT), however the new
server read the time from the BIOS as 2:00am -0700 (MST) (based on my
"correct" setting that I'm in MST zone)
As a result, both clocks displayed the correct time, both BIOSes had the
correct time, but when calculating UTC for internal use, the machines
were one hour off.
If it hadn't been 2am, it might have occurred to me to "fix" it by
adjusting the clock an hour off, correcting the UTC rather then the
displayed time, which would have allowed the new DC to sync up, group
policies would have kicked in, updates would have been downloaded and
the time would have fixed itself, the only pain being logs would be off
by an hour for a period of time (not a big deal)
--
Insert something clever here.
.
- References:
- NTP Question
- From: Geoff
- Re: NTP Question
- From: Jorge de Almeida Pinto [MVP - DS]
- Re: NTP Question
- From: DevilsPGD
- Re: NTP Question
- From: Herb Martin
- Re: NTP Question
- From: DevilsPGD
- Re: NTP Question
- From: Herb Martin
- NTP Question
- Prev by Date: Re: LDAP Authentication for Single Sign On
- Next by Date: Re: Active directory error
- Previous by thread: Re: NTP Question
- Next by thread: Re: NTP Question
- Index(es):
Relevant Pages
|
