The Windows Time service is the basis for the normal functioning of Active Directory Domain. Kerberos, the AD primary authentication protocol, uses the W32Time (Windows Time) time service to work properly. In AD environment, the time synchronization is performed according a strict hierarchy: domain joined computers and servers get the time from the nearest domain controller which they are logged on, all domain controllers synchronize their time with a single DC that owns the PDC Emulator FSMO role.

PDC Emulator (Primary Domain Controller) synchronize time with an external time source. The external time source is usually one or more public NTP (Network Time Protocol) servers, like time.windows.com or NTP-server of your provider. Please note that by the default time is provided to clients using the Windows Time service (instead of native NTP).

How the Windows Time Service Works in Domain?

All versions of Windows have a W32Time service. This service is used to synchronize the time in the AD organization. A computer can be both a client and an Ntp Server. By default, clients in the domain synchronize time using the Windows Time service rather than using NTP.

By default, the Windows Time Service is configured as follows:

• After performing a clean Windows installation, an NTP client is launched on the computer, which is synchronized with an external time source;
• If you joined a computer to a domain, the sync type changes. All client computers and member servers in the domain use a domain controller for time synchronization;
• When a member server is promoted to a domain controller, an NTP server is launched on it, which uses a DC with the PDC emulator role as a time source;
• The PDC emulator is the main time server for the entire organization. At the same time, it also synchronizes itself with an external time source or with the server’s hardware clock in CMOS (this method of time synchronization is not recommended);
• This scheme works in most cases and does not require admin intervention. However, the structure of the time service in Windows may not follow the domain hierarchy.

If you are facing a problem when time on clients and domain controllers is different, most likely your domain has a problem with time synchronization and then this article can be very useful for you.

First of all, it is necessary to select an NTP server that you want to use. The list of public NTP atomic clock servers is available at http://ntp.org. In our example, we will use: 0.us.pool.ntp.org, 1.us.pool.ntp.org, 2.us.pool.ntp.org and 3.us.pool.ntp.org.

Configuring domain time synchronization using Group Policy consists of 2 steps:

1. Create a GPO for the domain controller with PDC role;
2. Create a GPO for Windows client computers in the AD Domain.

Configuring NTP Server on PDC

First of all, you need to configure the PDC and enable the NTP service on it. Open a command prompt and run:

w32tm /query /source

If you see in the output:

• Local CMOS Clock — the time source on this server is its own local hardware clock.
• VM IC Time Synchronization Provider — then your domain controller with the PDC role is a virtual machine that synchronizes the time with the host.

Disable time synchronization with the host via the registry:

• Set the Enabled parameter to 0 in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\VMICTimeProvider

or in the settings of the virtual machine (the screenshot below shows how to disable the time synchronization of the VM with the Hyper-V host using the Time Synchronization option in the Integration Services section).

Note. The virtual PDC emulator must always synchronize the time with an external source, and the time synchronization with the host must be disabled. This also applies to any other VMs joined to the domain.

Make sure NTP service is enabled on the domain controller. To do this, open the registry editor, go to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer and check that the value of the Enabled parameter is 1.

Configure NTP Setting on PDC DC Using GPO

At this step, you need to configure your domain controller with the PDC Emulator role to synchronize time with an external source. PDC Emulator role can be transferred between domain controllers, so we need to make sure that GPO applied only to the current holder of the Primary Domain Controller role. To do this, run the Group Policy Management Console (GPMC.msc). Select the WMI Filters section and create a new WMI filter with name Filter PDC Emulator and the following WMI query in the root\CIMv2 namespace Select * from Win32_ComputerSystem where DomainRole = 5.

Create a new GPO and link it to the OU named Domain Controllers.

Select this GPO and switch to the Edit mode. Go to the following section of Group Policy Editor Console:  Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers.

Enable the following policy settings:

• Configure Windows NTP Client: Enabled (policy settings are described below);
• Enable Windows NTP Client: Enabled;
• Enable Windows NTP Server: Enabled.

Specify following settings in Configure Windows NTP Client policy:

• NtpServer: us.pool.ntp.org,0x1 1.us.pool.ntp.org,0x1 2.us.pool.ntp.org,0x1 3.us.pool.ntp.org,0x1;
• Type: NTP;
• CrossSiteSyncFlags: 2;
• ResolvePeerBackoffMinutes: 15;
• Resolve Peer BAckoffMaxTimes: 7;
• SpecilalPoolInterval: 3600;
• EventLogFlags: 0.

Note. Do not forget to configure your firewall properly and allow your PDC access the external NTP servers over NTP protocol (UDP port 123).

Assign a WMI filter Filter PDC Emulator that you created earlier to the GPO.

Tip. You can locate the current PDC server using the command: netdom query fsmo

It remains to update the Group Policy settings on PDC:

gpupdate /force

Perform a manual time synchronization with your NTP source:

w32tm /resync

And check the current NTP settings:

w32tm /query /status

Tip. If something does not work, try to restart the Windows Time service and reset its configuration:

net stop w32time

w32tm.exe /unregister

w32tm.exe /register

net stop w32tim

Configure Client Time Sync Settings Using GPO

By default in Active Directory, domain clients synchronize their time with domain controllers (option Nt5DS — synchronize time to domain hierarchy). Typically, this behavior does not need to be reconfigured. However, if there are problems with time sync on your domain clients, you can try to specify the time server directly on clients using GPO.

To do this, create a new GPO and assign it to the OU with computers. In the GPO Editor go to the following section Computer Configuration > Administrative Templates > System > Windows Time Service > Time Providers and enable the policy Configure Windows NTP Client.

As an NTP server specify the name or IP address of the PDC:  lon-dc1.adatum.com,0x9

Set Type: NT5DS

Note. Possible values for the Type parameter:

• NoSync — the NTP server is not synchronized with any external time source. The system clock built into the server’s CMOS chip is used;
• NTP — the NTP server is synchronized with external time servers, which are specified in the NtpServer registry parameter (this is default behavior on a stand-alone computer);
• NT5DS — the NTP server performs synchronization according to the domain hierarchy (used by default on domain-joined computers;
• AllSync — the NTP server uses all available sources for time synchronization.

Update Group Policy settings on the clients and check received time sync settings as described above.

The post Configure NTP Time Sync Using Group Policy appeared first on TheITBros.