<div>
<div class="content wysiwyg-content">
I have a small domain where one PDC emulator and 1 DC. <br />
<br />
When I run 'w32tm /monitor', it shows times of DCs, but the PDC shows 'RefID: 'LOCL' [76.79.xx.xx]'<br />
and the other DC shows RefID: PDC_Server_Name. <br />
<br />
So, I assume the PDC is syncing to Local bios time. <br />
<br />
My questions are;<br />
<br />
1. How to check if any machine is syncing to what time source? The domain controllers shows the time source as 'RefID', but rest of PCs in the domain doesn't show any, so do I just assume, any PC is syncing to PDC or is there any way to find what source is being used? <br />
<br />
2. If all clients and DCs are syncing to PDC, then I just change PDC's time source to time.windows.com by running 'w32tm /config /manualpeerlist: peers /syncfromflags:manual /reliable:yes /update'?<br />
<br />
<br />
DCs are Windows Server 2003, clients are windows xp
</div>
</div>


I have a small domain where one PDC emulator and 1 DC. 

When I run 'w32tm /monitor', it shows times of DCs, but the PDC shows 'RefID: 'LOCL' [76.79.xx.xx]'
and the other DC shows RefID: PDC_Server_Name. 

So, I assume the PDC is syncing to Local bios time. 

My questions are;

1. How to check if any machine is syncing to what time source? The domain controllers shows the time source as 'RefID', but rest of PCs in the domain doesn't show any, so do I just assume, any PC is syncing to PDC or is there any way to find what source is being used? 

2. If all clients and DCs are syncing to PDC, then I just change PDC's time source to time.windows.com by running 'w32tm /config /manualpeerlist: peers /syncfromflags:manual /reliable:yes /update'?


DCs are Windows Server 2003, clients are windows xp

Windows time server on PDC

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.

IT Administration

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.