The command sync completed successfully.
Check the Event Viewer sync for any errors.
Configure the external time sources, type: C: w32tm /config server /syncfromflags:manual /manualpeerlist:st.Log in to your PDC Server and open the command prompt.46:48.8738609s - server NtpServer started.46:33.8630024s - DomainHierarchy: we are now the domain root. .46:48.8728609s - Logging warning: NtpClient: This machine is the PDC of sync the domain at the root of the forest, sync so there is no machine above it in the domain hierarchy to use as a time source. So far so good.
46:48.8728609s - Query 1: no DC found.
46:48.8748610s - NtpProvider: Network Topology Change :46:48.8748610s - Peer never sync sync'd, resync now!
Should be advertised as reliable :46:33.8640024s - ClockDisciplineThread: Starting: SetUnsync: LI:0 S:1 RDl:0 RDs: TSF:0x :46:33.8700028s server - ClockDispln: we're a reliable time service with no time source: LS: 0, TN:, wait: :46:33.8700028s - Starting Providers.46:48.8728609s - Retrying resolution for domain windows hierarchy.Type: C: w32tm /config /reliable:yes.46:33.8710028s - Query 1 (background site: Default-First-Site-Name, DOM: virage.You can check the external NTP servers in the time configuration by typing: C: w32tm /query /configuration. Make your PDC a reliable time source for the clients.
Please be sure to answer the question.
Post as a guest, email, required, but never shown.
46:33.8710028s - PeerPollingThread: waiting forever time sync windows server 2008 :46:33.8710028s - Starting 'NtpServer :46:33.8710028s - LoadLibrary :46:33.8710028s - NtpTimeProvOpen NtpServer called.