<div>
do the foloowing<br />
<br />
dcdiag from the command prompt and dcdiag/fix and restart the server.
</div>


do the foloowing

dcdiag from the command prompt and dcdiag/fix and restart the server.

<div>
<div class="content wysiwyg-content">
I have a Windows Server 2003 network that has two domain controllers. I just added the second one a few days ago. As part of the dcpromo process, it uses FRS to copy the contents of my domain's sysvol directory from one DC to the other. <br />
<br />
Since the dcpromo, I've been getting errors on the second DC, inculding Event ID 13549 Source Ntfrs (<a href="http://www.eventid.net/display.asp?eventid=13549&eventno=3073&source=Ntfrs&phase=1" rel="ugc">http://www.eventid.net/display.asp?eventid=13549&eventno=3073&source=Ntfrs&phase=1</a>). When I look at my first domain controller's sysvol directory, the mydomain.local directory has a timestamp of 01/17/2010. The date and time on the server is correct, 10/2/2009. Both servers' times are in sync. That mydomain.local timestamp is keeping me from using FRS to my second domain controller. Any idea on how I can resolve the issue?
</div>
</div>


I have a Windows Server 2003 network that has two domain controllers. I just added the second one a few days ago. As part of the dcpromo process, it uses FRS to copy the contents of my domain's sysvol directory from one DC to the other. 

Since the dcpromo, I've been getting errors on the second DC, inculding Event ID 13549 Source Ntfrs (http://www.eventid.net/display.asp?eventid=13549&eventno=3073&source=Ntfrs&phase=1). When I look at my first domain controller's sysvol directory, the mydomain.local directory has a timestamp of 01/17/2010. The date and time on the server is correct, 10/2/2009. Both servers' times are in sync. That mydomain.local timestamp is keeping me from using FRS to my second domain controller. Any idea on how I can resolve the issue?

How can i resolve an incorrect timestamp in my sysvol folder?

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.

Active Directory

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).