Friday, August 17, 2012 5:13 PM
OK Let me start by giving a bit of background.
Windows 2008 R2 servers (all patched and updated)
Hyper-V running on a cluster.
*CRASH*! not going into details but my PDC died (We buried it in an unmarked grave out back)
So I Seize the rolls on the existing (Virtual) DC, clean up the metadate, set up new DHCP - DNS (Network is happy again) At least the users are.
I, of course replace the physical DC that crashed and move on.
My issue now (two years after the crash) is that the network quit getting its time from ntp.org I check and see that the virtual DC holds the PDC emulator roll. Knowing that Hyper-V clients want to get their time from their hose, I move the PDC roll from the virtual DC to the Physical one.
At that time the network was off by 38 seconds. This is important. the entire network is off by the same time and therefore in no danger of DC's and clients getting out of sync.
No matter what I try I cannot get the network to get it's time from the PDC emulator (Physical server) Running w32tm /query shows that all clients and servers are getting their time from the Virtual DC that IS NOT THE OWNER OF THE PDC Emulator Roll.
As far as I can tell the network believes that the Virtual DC is the PDC but I don't know what to do now or where to look.
PDC is set to use SNTP
DC and all other servers are set to use NTDS5
When I run w32tm /config /manualpeerlist:si.pool.ntp.org,0×8, /syncfromflags:manual /update on the PDC I get "Command completed successfully.
Then when I run w32tm /query /status I see the PDC is still getting its time from the Virtual DC.
I have been through AD GPO's. logon scripts everything I can think of.
Has anyone ever seen this? Any ideas? At the time of this posting the network is off 52 seconds and GOD FORBID a users pc displays a 1 minute difference!
Friday, August 17, 2012 5:35 PM
A useful links for your reference to configure time source at your place.
- Configuring a time source for the forest:http://technet.microsoft.com/en-us/library/cc784800(v=ws.10)
- Time Synchronization and Domain Controller VM's:http://blogs.msdn.com/b/robertvi/archive/2011/05/11/time-synchronization-and-domain-controller-vm-s.aspx
So,check it once and cross check your time configuration settings again.Also please write here again if you need any other info?
Regards, Ravikumar P
Saturday, August 18, 2012 1:26 AM
I would at first check your registry. Check in hklm\system\currentcontrolset\w32time and check for any reference for that virtual DC.
If you find nothing, check all GPO, script (like a net time \\virtual_dc), etc.. that could set the timeserver.
Let us know if you find something.
Monday, August 20, 2012 2:34 PM
I checked and double checked my time settings - they are correct.
I checked the registry. And I think something is amis.
The Physical DC that holds the PDC Emulator role has under hklm\...\w32time\parameters: NtpServer = 0.pool.ntp.org 1.pool.ntp.org and the Type is NTP
on the virtual DC that the network is getting it's time from the settings are hklm\...\w32time\parameters: NtpServer = sl.pool.ntp.org, 0x8 and teh type is NTP
I don't ever remember changing the time settings but I could have. I'm still checking GPO's and scripts.
I will keep everyone updated.
Tuesday, August 21, 2012 8:21 AM
if you transfer FSMO roles the previous PDCEmulator must be reconfigured with:
w32tm /config /syncfromflags:domhier /reliable:no /update
After that you have to run:
net stop w32time
net start w32time
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
- Marked As Answer by Andy QiMicrosoft Contingent Staff, Moderator Monday, August 27, 2012 6:43 AM