Move Time Service from 2K to 2K3

  • Thread starter Thread starter mren2005
  • Start date Start date
M

mren2005

Hi Guys,

I've got an issue where the previous Windows 2000 PDC Emulator is
holding onto its Time Server role. The PDC Emulator FSMO Role has since
been moved to a 2003 Domain controller.

I would like to move the Time Service role to the Windows 2003 Domain
Controller as well.

replmon.exe shows that the Windows 2000 DC is retaining this role
despite any articles I've followed to move it.

What I would like is a simple guide on how to disable the Time Service
on the Windows 2000 DC, then enable the service on the Windows 2003
PDC, have it use it's internal clock for time sync and have all network
clients use it as the time server.

I've searched high and low for a comprehensive solution to this dilemma
but can't find one. I know there's a million guides on how to do this
out there however they seem to report different methods and I can't
find one suitable for my situation. Thanks in advance for your help.
 
Yeah because the old PDC is Windows 2000 the command "w32tm /config
/syncfromflags:domhier /reliable:no /update" doesn't work. I basically
need the Windows 2000 version of that command.
 
Check the command line options again....

you could run this from a w2k3 computer and specify the W2k box as a target!
;-)


w32tm /config [/computer:<target>] [/update]
[/manualpeerlist:<peers>] [/syncfromflags:<source>]
[/LocalClockDispersion:<seconds>]
computer:<target> - adjusts the configuration of <target>. If not
specified, the default is the local computer.
update - notifies the time service that the configuration has
changed, causing the changes to take effect.
manualpeerlist:<peers> - sets the manual peer list to <peers>,
which is a space-delimited list of DNS and/or IP addresses.
When specifying multiple peers, this switch must be enclosed in
quotes.
syncfromflags:<source> - sets what sources the NTP client should
sync from. <source> should be a comma separated list of
these keywords (not case sensitive):
MANUAL - include peers from the manual peer list
DOMHIER - sync from a DC in the domain hierarchy
 
mren2005 said:
Hi Guys,

I've got an issue where the previous Windows 2000 PDC Emulator is
holding onto its Time Server role. The PDC Emulator FSMO Role has
since been moved to a 2003 Domain controller.

I would like to move the Time Service role to the Windows 2003 Domain
Controller as well.

replmon.exe shows that the Windows 2000 DC is retaining this role
despite any articles I've followed to move it.

What I would like is a simple guide on how to disable the Time Service
on the Windows 2000 DC, then enable the service on the Windows 2003
PDC, have it use it's internal clock for time sync and have all
network clients use it as the time server.
Click to expand...


All DCs must be time servers, but the PDC must be configured as the
Authoritative Time server.

A List of the Simple Network Time Protocol Time Servers That Are Available
on the Internet:
http://support.microsoft.com/default.aspx?scid=kb;en-us;262680
How to configure an authoritative time server in Windows 2000:
http://support.microsoft.com/default.aspx?scid=kb;en-us;216734
How to configure an authoritative time server in Windows Server 2003:
http://support.microsoft.com/kb/816042
 
Back
Top