We recently installed Ex2007 so we had to install two W2003 DC's. HOwever,
we can't demote the two W2K dc's at this time. One of two W2003 DC's has
the FSMO and PDC Emulator roles. However, we've found some of our pc's are
synchronizing their clocks to a W2K DC instead of the W2k3 DC.
Upon investigation, I found the W2k3 DC time was set to NT5DS instead of
NTP. The W2K dc was set to NTP. I changed that on both DC's;one to NTP and
the other to NT5DS. But, we're still having a conflict. Did I miss a reg
setting?

Hello paulc,

The domain time syc works as follows, the PDCEmulator is the time master,
all DCs sync with it and all other domain machines choose one available DC
for the time sync.

Normally you don't have to set the registry keys manual in Windows server
2003. It is more easy with the command line.

On the PDCEmulator run:

w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update

With "PEERS" you can set the time source, either DNS name (time.windows.com)
or an ip address from a reliable time source.

Here you can find some of them:
http://www.pool.ntp.org/

-------------------------------------------------------------------
Client configuration:
To configure a client computer for automatic domain time synchronization

w32tm /config /syncfromflags:domhier /update

After that run:
net stop w32time
net start w32time

-------------------------------------------------------------------
Reconfigure the previous PDCEmulator in Windows server 2003:

w32tm /config /syncfromflags:domhier /reliable:no /update

After that run:
net stop w32time
net start w32time

Windows server 2000 previous PDCEmulator:
Modify the "Type" value to "Nt5Ds" without the quotes under this registry
key:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters\


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> We recently installed Ex2007 so we had to install two W2003 DC's.
> HOwever,
> we can't demote the two W2K dc's at this time. One of two W2003 DC's
> has
> the FSMO and PDC Emulator roles. However, we've found some of our
> pc's are
> synchronizing their clocks to a W2K DC instead of the W2k3 DC.
> Upon investigation, I found the W2k3 DC time was set to NT5DS instead
> of
> NTP. The W2K dc was set to NTP. I changed that on both DC's;one to
> NTP and
> the other to NT5DS. But, we're still having a conflict. Did I miss a
> reg
> setting?

Hello paulc,

Do not forget to make the new DCs also Global catalog server and install
DNS server, if not already done. Also reconfigure the domain machines to
use the new DNS servers on the NIC instead of the Windows server 2000.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> We recently installed Ex2007 so we had to install two W2003 DC's.
> HOwever,
> we can't demote the two W2K dc's at this time. One of two W2003 DC's
> has
> the FSMO and PDC Emulator roles. However, we've found some of our
> pc's are
> synchronizing their clocks to a W2K DC instead of the W2k3 DC.
> Upon investigation, I found the W2k3 DC time was set to NT5DS instead
> of
> NTP. The W2K dc was set to NTP. I changed that on both DC's;one to
> NTP and
> the other to NT5DS. But, we're still having a conflict. Did I miss a
> reg
> setting?