Change time server to another sever?

When I type net time at the command line I get Current time at \\DP2S is 3/29/2010 1:44:50 PM how I’m demoting DP2S/2k3 R2 soon how can make the time provided by our new 2008/R2 PDC instead?  
TITGAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

IT-Monkey-DaveCommented:
To set up the new 2008 R2 server as your timekeeper, see MS KB Article 816042:
http://support.microsoft.com/kb/816042 
Once that's done, change the old timekeeper back to its default role as obtaining time from Active Directory with this command:
w32tm /config /syncfromflags:domhier /update
Be sure to stop & restart the time service after making config changes on both servers:
net stop w32time && net start w32time
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jasoncmCommented:
Run the following on the command line for systems you want to update with the new time server:

net time /setsntp:xxx.xxx.xxx.xxx

Replace the x's with the appropriate IP address. Command requires elevated privileges.
0
TITGAuthor Commented:
Just to make sure to set the new time server i'm following the below to set it up?


 Configuring the Windows Time service to use an  internal hardware clockImportant This section, method, or task  contains steps that tell you how to modify the registry. However,  serious problems might occur if you modify the registry incorrectly.  Therefore, make sure that you follow these steps carefully. For added  protection, back up the registry before you modify it. Then, you can  restore the registry if a problem occurs. For more information about how  to back up and restore the registry, click the following article number  to view the article in the Microsoft Knowledge Base: 322756                                           (http://support.microsoft.com/kb/322756/                         )          How to back up and restore the registry in Windows

To  configure the PDC master without using an external time source, change  the announce flag on the PDC master.  The PDC master is the server that  holds the forest root PDC master role for the domain. This configuration  forces the PDC master to announce itself as a reliable time source and   uses the built-in complementary metal oxide semiconductor (CMOS) clock.   To configure the PDC master by using an internal hardware clock,  follow these steps:Click Start,  click Run, type regedit,  and then click OK.
Locate and  then click  the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
       In the right pane, right-click AnnounceFlags,  and then click Modify.
      In Edit DWORD Value, type A  in the Value data box, and then click OK.
Quit Registry Editor.
At  the command prompt, type the following command to restart the Windows  Time service, and then press ENTER:net stop w32time && net start w32time

0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

IT-Monkey-DaveCommented:
How important is it for your domain to have very accurate timekeeping?  If accuracy is important, you should use an external time source, even if it's just time.windows.com.  Using the server's built-in clock will not give you a high degree of accuracy, just consistency across your domain.
List of reliable external time references: http://tycho.usno.navy.mil/ntp.html
 
0
TITGAuthor Commented:
 
I just need this new PDC to keep the time and PCs look at him for the right time that is all  
0
IT-Monkey-DaveCommented:
Then you should be ok using the 2nd method you quoted, where the PDC timekeeper server uses the server's internal hardware clock (CMOS clock) as the timekeeping reference.
 
0
TITGAuthor Commented:
okay ran this on the old time server w32tm /config /syncfromflags:domhier /update stopped then restart time service and i get the below event
The time service is now synchronizing the system time with the time source PDCS.ourdomain.local (ntp.d|10.0.0.9:123->10.0.0.6:123). 10.0.0.9 "old server IP" and 10.0.0.6 they be switched?

New server did the reg modifications below stop then restart win time service ran net time still getting the time from the old server?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
        In the right pane, right-click AnnounceFlags,  and then click  Modify.
      In Edit DWORD Value, type A  in the Value data box, and  then click OK.
0
IT-Monkey-DaveCommented:
Try this on the new server:
w32tm /query /status
What server does it show as the "Source" of its time?
0
TITGAuthor Commented:
C:\>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0312500s
Root Dispersion: 0.0266709s
ReferenceId: 0x81060F1C (source IP:  129.6.15.28)
Last Successful Sync Time: 3/29/2010 5:42:04 PM
Source: 129.6.15.28,0x8
Poll Interval: 9 (512s)

When I do net time in my laptop I get current time at \\DP2S is 3/29/2010 5:45:53 PM. Still the old one...the old server still on and as a DC I didn't take it off yet I want to switch the time server so I can take the old one off soon.
0
IT-Monkey-DaveCommented:
"Source: 129.6.15.28,0x8"
That's an external time source, time-a.nist.gov.  Nothing wrong with that but it's not what you said you wanted which was to just do internal timekeeping.
What do you get when you do the same command "w32tm /monitor" on the old server?  Its time reference server should now be the new server's IP or name.
Is the laptop joined to the domain (presumably it is).  Have you rebooted it since making the server changes?
0
IT-Monkey-DaveCommented:
Also note that when Active Directory has multiple domain controllers, any DC can function as a time reference server, domain hierarchy thing.  AD figures that out on its own.  So the clients will not necessarily get their time from the PDC.  However the other servers will be sync'd to the PDC so all domain clients & servers will be in sync with one another and with the master timekeeper.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.