Link to home
Start Free TrialLog in
Avatar of ArchitectChuck
ArchitectChuck

asked on

Old 2003 PDC interfering with new 2008 R2

How do I tell my old 2003 PDC that it is no longer the authoritative time source in a domain with a 2008 R2 DC?
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

ASKER CERTIFIED SOLUTION
Avatar of footech
footech
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ArchitectChuck
ArchitectChuck

ASKER

Thanks KCTS.  The 2008 Server already has accepted those roles, although I have received a message that is does not believe it is authoritative.

My first step was to make sure that both DC's understand the the 2008 R2 is the authoritative time source for the domain.

I will attack the remaining issues separately.

Thank you footech.  I have used your command previously, but have not used pools.  I named three time servers.  Have you found pools to be more dependable??

By the way, I did get a message from the 2003 server that it was using the 2008 server as its time source.

Thanks
I haven't really done a comparison.  I've never encountered any problem with using the pools so haven't investigated other alternatives.
I just ran

net stop w32time
w32tm /unregister
w32tm /register
net start w32time

on my desktop.  then ran Net Time

It says it is using the old 2003 server as its time source?  Does that sounds right?
You shouldn't need to run that on your desktop unless you had previously modified its config.  I never run net time so I'm not familiar with its output, but I do know the command has been deprecated, so it's better to use w32tm.