Re: Time Server best practice
- From: "Pavlo Ignatusha" <pavlo.ignatusha@xxxxxxxxxxxxx>
- Date: Thu, 7 Sep 2006 16:29:40 -0400
Usually the domain members are syncronised automatically with PDC emulator.
All you have to do is set the PDC emulator to sync with outside time source
you like.
Check this link:
http://technet2.microsoft.com/WindowsServer/en/library/f3d6b66c-5fdc-4a77-a901-5efbcb4d4bb71033.mspx?mfr=true
Pavlo
"Gordon Price" <GordonPrice@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5894E711-3570-4F06-86DB-9E56FA838590@xxxxxxxxxxxxxxxx
I have inherited a network recently, and I am seeing some regular W32Time
errors in the event log. As far as I can tell, DHCP is not configured to
give
clients a Time Server to sync to, and I am wondering what the Best
Practice
is here.
Do I configure DHCP to provide an outside Time Server for all machines to
sync to, or do I configure DHCP to provide an in-house Server to sync to,
and
then configure just that one Server to sync to an outside Time Server? Or
is
time sync done automatically bybeing a member of a domain and the DHCP
setting can be ignored? And if so, what might be causing my regular
events. I
get a ID 14 warning, no NtpClient unable to find domain controller. Then
ID
29 error, then ID 37 and 35, indicating sync success. But the warning and
error keep happening, followed by success.
Just curious.
Thanks,
Gordon
.
- Prev by Date: Re: access offline files on the laptop (CSC)-help!
- Next by Date: Re: access offline files on the laptop (CSC)-help!
- Previous by thread: test
- Next by thread: Re: Remote Desktop
- Index(es):
Relevant Pages
|