Hi Folks: I have two sites - SITE A and SITE B. SITE B is overseas on a different time zone authenticating to our DC's at SITE A over an MPLS network. THE PROBLEM: The PCs and Phones in SITE B show the time zone settings of SITE A. (Obviously because they are getting their NTP settings from the MAIN DC in SITE A). I want users in SITE B to receive their real local time zone. How can I fix this issue?Luis

The PDCEmulator is the time source for the domain, all DCs sync with that one. The first domain controller that you deploy in a domain holds the primary domain controller (PDC) emulator operations master (also known as flexible single master operations or FSMO) role for the domain. By default, the domain controller that holds the PDC emulator master role in the forest root domain is the reliable time source at the top of the time-source domain hierarchy for the forest. As soon as you install the first domain controller in the forest, set the PDC emulator in the forest root domain to synchronize from a valid Network Time Protocol (NTP) source or from a hardware clock installed on the network. If no time source is configured on the PDC emulator or any other domain controller in the forest root domain, the PDC emulator advertises as a reliable time source and uses its internal clock as the source for forest synchronization. In this case, no manual configuration is required. To configure the pdc emulator see here http://technet.microsoft.com/en-us/library/cc786897(WS.10).aspxRegards, ~P MCSE, MCITP, MCTS, MCP, CCNA

The PDCEmulator is the time source for the domain, all DCs sync with that one. The first domain controller that you deploy in a domain holds the primary domain controller (PDC) emulator operations master (also known as flexible single master operations or FSMO) role for the domain. By default, the domain controller that holds the PDC emulator master role in the forest root domain is the reliable time source at the top of the time-source domain hierarchy for the forest. As soon as you install the first domain controller in the forest, set the PDC emulator in the forest root domain to synchronize from a valid Network Time Protocol (NTP) source or from a hardware clock installed on the network. If no time source is configured on the PDC emulator or any other domain controller in the forest root domain, the PDC emulator advertises as a reliable time source and uses its internal clock as the source for forest synchronization. In this case, no manual configuration is required. To configure the pdc emulator see here http://technet.microsoft.com/en-us/library/cc786897(WS.10).aspxRegards, ~P MCSE, MCITP, MCTS, MCP, CCNA

Gandalf thank you for your reply. However, I know what the PDC emulator does and the important role it plays in my domain. I just want to know if there is a workaround on my scenario. Thanks!Luis

Just make sure that your computers are set to a correct time zone. That’s why by default you only have one PDC per domain. I think the thread below will clarify that. http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/b83246a8-e041-4a67-be16-58da8786e85c/

Just make sure that your computers are set to a correct time zone. That’s why by default you only have one PDC per domain. I think the thread below will clarify that. http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/b83246a8-e041-4a67-be16-58da8786e85c/

Brano thanks for your reply. But in this case, there is no DC in SITE B. Remember, they all connect to the DC in SITE A.. Thanks Lu

You may need to look into DHCP options if you are having problems (004,042,156) http://www.howtonetworking.com/others/dhcp4ipphone.htm http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx

You may need to look into DHCP options if you are having problems (004,042,156) http://www.howtonetworking.com/others/dhcp4ipphone.htm http://technet.microsoft.com/en-us/library/cc773013(WS.10).aspx