Home » Active Directory » Synchronize the domain controller with an external time source

Translate:

Archives

Synchronize the domain controller with an external time source

If there is time synchronize issues we might see lot of issues like Connectivity issues in between DC and Client Machines. So let’s see how to resolve this out:

Note : If you’r client machines are like Exchange Server and connected to DC if there is Time Sync Issues then we might see scenario’s like

a: Exchange Services not starting.

b: EMC & EMS not opening

c: In Event ID’s we might see 2080, 2070 etc….

 

Solution :

 1 : First, locate your PDC Server. Click Start, and then click Command Prompt

2: In the Command Prompt window, type the following line, where peers is a comma-separated list of IP addresses of the appropriate time sources, and press ENTER:

w32tm /config /manualpeerlist: peers /syncfromflags:MANUAL

 

The time sources you choose depend on your time zone. For example, if your domain controller is located in the Pacific Time zone, this line might read:

w32tm /config /manualpeerlist:10.X.X.X /syncfromflags:MANUAL

 

In this example, the IP address of the timeserver is used instead of the fully qualified domain name for security purposes.

Press ENTER. You should get a message that the command completed successfully.

Type w32tm /config /update

Press ENTER. You should get a message that the command completed successfully.

 

W32time uses a variable poll interval based on the quality of timesync with the server. On DCs, this interval defaults to between 64 and 1024 seconds.

 

To immediately synchronize with the external time server, type w32tm /resync and press ENTER. You should get a message that the command completed successfully.

 

Type Exit and press ENTER.

OR

 

If you want to use an external source for both Domain Controllers you can configure it to do so using the commands. Generally speaking, the Domain Controller holding the PDC Emulator role should sync from the external source and your other Domain Controllers should sync from it.

 

net stop w32time & net start w32time

w32tm /resync /force

Restart the time service and force a resynchronization.

w32tm /query /source

 

Finally you should confirm that your Domain Controllers have the correct time source.

 

For More Info : http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/11/19/time-synchronization-in-hyper-v.aspx

 

Praveen Kumar

MCSA, MCSE | Windows Server


2 Comments

Leave a comment

Translate »