Wouldn't it make more sense to have the PDCe use the workstation as your
reliable time source and let the rest of AD do it's thing? It has that
built into the product because of how important time sync is to AD
functionality.
Just curious.
Al
-Original Message-
From: [EMAIL
Personally...I don't use NET TIME at all. I wish they'd either do away
with it or make some kind of statement about its uselessness (my opinion
-sorry!). Use W32TM to test your 2000 (and up) machines.
You should sync your forest root PDCe to whatever device you have as
your reliable time
Net Time uses the old NetRemoteTOD API, for computers not running the
time service, when they issue a NET TIME command without any parameters
the clients issue a NetServerEnum to enumerate the servers from the
browse list (yuk) with the TS (timesource )flag. Archaic and inaccurate
as compared to
I know that on a Win2k3 server you are supposed to use the w32tm
utility to verify your time settings (as Joh Policelli has already
mentioned this week) so perhaps it would be better to use that utility
on your workstation as well since in Win2k3 net time will not always
show you accurate
by:cc:
[EMAIL PROTECTED] Subject: RE: [ActiveDir] Using
net time
tivedir.org
] On Behalf Of Mike Baudino
Sent: Wednesday, April 13, 2005 11:49 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] Using net time
Strongly agree on the use of W32TM over NET TIME. Questions though:
So you don't need W32Time running on the XP box to be a time source to
the
root PDCe
