Monday, April 24, 2017
 Now reading ...
Oct
7
Tue
Posted By Subodh on Tuesday, October 07, 2008
44900 Views 8 Comments


Image courtesy www.time.com 1000s of documents out there that describe how to seize FSMO role, RID Master, Infrastructure Master etc from one domain controller to the other but not that easy to find a document that describes how to move the NTP time server role to new domain controller. Here goes how to do it but before we go any further, its time for the usual "Disclaimer1"

On the old domain controller, run the following at command prompt

w32tm /config /syncfromflags:domhier /reliable:no /update
net stop w32time && net start w32time

On the new domain controller, run the following at command prompt

w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update
net stop w32time && net start w32time

That's it. All the computers in your domain should automatically synchronize.

Credit where its due:


    The little things
    Richard at Article Alley
    Dealing with Windows Vista Time Sync Problems
 

1

DISCLAIMER This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.

Categories

  
 You may also be interested in
  
 Comments & Discussions

  • Gravatar
    foobar Wednesday, October 22, 2008 at 1:56 AM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    Lame lame lame. doesn't work

  • Gravatar
    subodh Sunday, October 26, 2008 at 7:44 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    A little more info on why it didn't work for you would be more helpful. Maybe there's something you're missing. Maybe I can help? happy

  • Gravatar
    Greshoe Friday, November 07, 2008 at 5:17 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    I used your procedure. It worked just fine. Thank you.

  • Gravatar
    Subodh Friday, November 07, 2008 at 6:22 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    You're welcome. Thanks for taking the time as well!

  • Gravatar
    Clive Tuesday, November 18, 2008 at 10:47 AM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    The same process will work for Windows 2003 DCs?

  • Gravatar
    Subodh Tuesday, November 18, 2008 at 4:16 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    Yes it will.

  • Gravatar
    Paul Page Monday, December 29, 2008 at 4:22 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    What is the old DC is no longer in the domain or setting up a new domain? How do I synch all the DC's to an external time source?

  • Gravatar
    Pepper Friday, August 28, 2009 at 6:59 PM
    Re: Moving NTP Time Server Role to new Windows 2008 domain controller
    So, should I do this on all DC's in my domain or just one, and let the rest of them sort themselves out? Or does it really matter?

    By the way, a somewhat related tip, if you run your DC's as virtual machines, make sure to turn off any integration "clock synchronization" feature, as what you would end up with is a DC clock that is synchronized to an inaccurate host clock, that is synchronizing itself to the DC's which are now inaccurate.

  
Locations of visitors to this page Clicky Web Analytics 

Subodh's Blog Rating

 

DISCLAIMER

The opinion expressed
on this page 
is strictly that
of the page author
who has a
habit of animating
day-dreaming
and
fictionalizing
out of thin air.
 

The contents of this page
have not been
reviewed 
nor
approved
by 
Yahoo!

 Follow this blog
  
 Tag Cloud
  
Archives
 

Top 5 Posts of Last year
Copyright © 1995-2009 Subodh Shakya. All rights reserved.{Powered by SpeedBlog}