General discussion

Locked

Splitting FSMO Roles and Resolving Time-Service Issues

By Zpunky ·
Just thought I'd post this for others who may be trying to resolve this problem. When moving the PDC role to a second DC, you need to re-establish the domain's time source:

We have a relatively small domain, single forest, two domain controllers. Per best practice, after migrating to W2K8 R2 Standard from SBS 2008 (ugh), I split the FSMO roles between the two DCs, moving the RID, PDC and Infrastructure roles to the second DC.

Time synchronization should be done on the DC with the PDC role, so I had to move time sync onto that DC: (http://technet.microsoft.com/en-us/library/cc794937%28WS.10%29.aspx), or simply execute: w32tm /config /manualpeerlist:?time.nist.gov time.microsoft.com? /syncfromflags:manual /reliable:yes /update from an elevate command prompt.

But this leaves the time server confused as the info is unchanged on the original PDC role holder. So, to have the original DC sync it's time with the new PDC role holder, simply execute, from an elevated command prompt, "w32tm /resync".

Although this appears fairly simple, before trying this I could not verify from documentation that this would actually cause this original DC to reset it's time to sync from the new PDC role holder. It did.

Hope this helps.

This conversation is currently closed to new comments.

0 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Back to Networks Forum
0 total posts (Page 1 of 1)  

Related Discussions

Related Forums