I brought a new Primary Domain Controller on-line running Windows Server 2008 R2 to replace the old PDC running Windows Server 2003 and I have successfully transferred the FSMO roles to the new server however i did not demote the old PDC and it has been off for about 2 months. Would it be safe to turn back on knowing that it will replicate with the other Domain Controllers before i can demote it.

You can remove it without keeping it back. Proceed like that: Let the old DC disconnected and run dcpromo /forceremoval on the old DC to force its demotion perform a metadata cleanup Remove all remaining DNS records of the old DC That should solve your problem without any issues. Note that it is recommanded to have at least two DC/DNS/GC servers per domain and that there is no primary DC and secondary DC. I brought a new Primary Domain Controller on-line running Windows Server 2008 R2 What do you mean by that? This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

Thanks for the response. I actually have two domain controlers but replacing one. I mistakenly turned one off for a couple of months without demoting it first. I am just worried that when I bring it back online (turning it on ) that the replication process will begin again and possibly mess something up with my current domain controllers. If I can safetly turn it back on then demote it then I will be cool with that. Since it has been off for months that was my concern. Do you see any problems with this.

I don't recommend that you let back a DC that was offline for more than 60 days. Please make sure that you have an online DC that is a GC and proceed like I mentioned in my first reply. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

Hi, I also agree to remove the orphaned Domain Controller by a force removal and a metadata cleanup. For the detailed steps, please refer to the following Microsoft KB article: How to remove completely orphaned Domain Controller http://support.microsoft.com/kb/555846 If the tombstone lifetime has expired, it will cause some unexpected issues. The default tombstone lifetime is 60 days. For more information, please also refer to the following Microsoft KB articles: Phantoms, tombstones and the infrastructure master http://support.microsoft.com/kb/248047 Lingering objects may remain after you bring an out-of-date global catalog server back online http://support.microsoft.com/kb/314282 Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello, if you are over the tombstone lifetime do NOT recoonect and run metadata cleanup: http://msmvps.com/blogs/mweber/archive/2010/05/16/active-directory-metadata-cleanup.aspx This way will show you how to find it out which days are configured: http://technet.microsoft.com/en-us/library/cc784932(WS.10).aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.