Windows Server 2. Server 2. 01. 2 R2. Windows Server includes W3. Time, the Time Service tool that is required by the Kerberos authentication protocol. The Windows Time service makes sure that all computers in an organization that are running the Microsoft Windows 2. Server operating system or later versions use a common time. To guarantee appropriate common time usage, the Windows Time service uses a hierarchical relationship that controls authority, and the Windows Time service does not allow for loops. By default, Windows based computers use the following hierarchy All client desktop computers nominate the authenticating domain controller as their in bound time partner. All member servers follow the same process that client desktop computers follow. All domain controllers in a domain nominate the primary domain controller PDC operations master as their in bound time partner. All PDC operations masters follow the hierarchy of domains in the selection of their in bound time partner. In this hierarchy, the PDC operations master at the root of the forest becomes authoritative for the organization. We highly recommend that you configure the authoritative time server to obtain the time from a hardware source. When you configure the authoritative time server to sync with an Internet time source, there is no authentication. Figure-85.png' alt='Citrix Presentation Server Client For 64-Bit Windows 7' title='Citrix Presentation Server Client For 64-Bit Windows 7' />We also recommend that you reduce your time correction settings for your servers and stand alone clients. These recommendations provide more accuracy and security to your domain. Configuring the Windows Time service to use an internal hardware clock. Important 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 3. 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. Client and server operating systems supported for the most current release of the UPD Client operating systems supported Microsoft Windows 8, Pro, Enterprise 32. Cisco UCS C240M3 Rack Server with NVIDIA GRID GPU cards on Citrix XenServer 6. XenDesktop 7. 5. Windows Server includes W32Time, the Time Service tool that is required by the Kerberos authentication protocol. The Windows Time service makes sure that all. To configure the PDC master by using an internal hardware clock, follow these steps 1. Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeConfigAnnounce. Flags. 3. In the right pane, right click Announce. Flags, and then click Modify. In Edit DWORD Value, type A in the Value data box, and then click OK. Close Registry Editor. At the command prompt, type the following command to restart the Windows Time service, and then press Enter net stop w. Note The PDC master must not be configured to synchronize with itself. For more information about why the PDC master must not be configured to synchronize with itself, see Request For Comment RFC 1. If the PDC master is configured to synchronize with itself, the following events are logged in the System log Event Type Information Event Source W3. Time Event Category None Event ID 3. Computer Computer. Name. Description The time provider Ntp. Client cannot reach or is currently receiving invalid time data from NTPserverIPAddress. For more information, see Help and Support Center at http support. Free Templates For Sale there. Event Type Warning Event Source W3. Time Event Category None Event ID 4. Computer Computer. Name. Description Time Provider Ntp. Client No valid response has been received from manually configured peer NTPserverIPAddress after 8 attempts to contact it. This peer will be discarded as a time source and Ntp. Client will attempt to discover a new peer with this DNS name. Red Alert 2 Royal Mod. For more information, see Help and Support Center at http support. Event Type Error Event Source W3. Time Event Category None Event ID 2. Computer Computer. Name. Description The time provider Ntp. Client is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 1. Ntp. Client has no source of accurate time. For more information, see Help and Support Center at http support. When the PDC master runs without using an external time source, the following event is logged in the Application log Event Type Error Event Source W3. Time Event Category None Event ID 1. Description Time Provider Ntp. Client This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the Ntp. Client. This text is a reminder to use an external time source, and it can be ignored. Configuring the Windows Time service to use an external time source. To configure an internal time server to synchronize with an external time source, follow these steps 1. Change the server type to NTP. To do this, follow these steps a. Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeParametersTypec. In the pane on the right, right click Type, and then click Modify. In Edit Value, type NTP in the Value data box, and then click OK. Set. Announce. Flagsto 5. To do this, follow these steps a. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeConfigAnnounce. Flagsb. In the pane on the right, right click Announce. Flags, and then click Modify. In Edit DWORD Value, type 5 in the Value data box, and then click OK. Enable NTPServer. To do this, follow these steps a. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeTime. ProvidersNtp. Serverb. In the pane on the right, right click Enabled, and then click Modify. In Edit DWORD Value, type 1 in the Value data box, and then click OK. Specify the time sources. To do this, follow these steps a. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeParametersb. In the pane on the right, right click Ntp. Server, and then click Modify. In Edit Value, type Peers in the Value data box, and then click OK. Note. Peers is a placeholder for a space delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique. You must append ,0x. DNS name. If you do not append ,0x. DNS name, the changes that you make in step 5 will not take effect. Select the poll interval. To do this, follow these steps a. Locate and then click the following registry subkey HKEYLOCALMACHINESYSTEMCurrent. Control. SetServicesW3. TimeTime. ProvidersNtp.