Secondary DC failing hardware
Hello experts,
I have a domain with 2 DC's. The primary DC is a 2008 server is running the following:
Schema Master
Domain naming Master
PDC
RID pool Manager
Infrastructure Master
The secondary DC is a 2003 Server , and its failing. I noticed I could connect to it last week; so I traveled to its location and noticed it wasn't booting properly. I got it backup using the last know good configuration, and I thought it was fine, but again I cant connect. Anyway probable to much info.
I'm thinking that its going to probably die soon. So seeing that its an old P3 server; I'm thinking its best to replace it.
The Secondary DC is in another city connected via routers.
My question is; what would be the best procedure for removing it from the domain?
Also if I get it turned on now after being down for 4 days; will it cause issue?
Thanks
I have a domain with 2 DC's. The primary DC is a 2008 server is running the following:
Schema Master
Domain naming Master
PDC
RID pool Manager
Infrastructure Master
The secondary DC is a 2003 Server , and its failing. I noticed I could connect to it last week; so I traveled to its location and noticed it wasn't booting properly. I got it backup using the last know good configuration, and I thought it was fine, but again I cant connect. Anyway probable to much info.
I'm thinking that its going to probably die soon. So seeing that its an old P3 server; I'm thinking its best to replace it.
The Secondary DC is in another city connected via routers.
My question is; what would be the best procedure for removing it from the domain?
Also if I get it turned on now after being down for 4 days; will it cause issue?
Thanks
ASKER
Thanks
One other question. Seeing that my Primary DC is a 2008 server; do I use the 2008 procedure for removing the old 2003 DC?
One other question. Seeing that my Primary DC is a 2008 server; do I use the 2008 procedure for removing the old 2003 DC?
It is a different procedure if you are going to remove the backup domain controller. As stated by takecoffe you want to clean the metadata from AD.
This is an article to follow which will help you through it.
http://community.spiceworks.com/how_to/show/616-remove-a-failed-domain-controller-from-a-windows-2003-domain
This is an article to follow which will help you through it.
http://community.spiceworks.com/how_to/show/616-remove-a-failed-domain-controller-from-a-windows-2003-domain
First try normal demotion if normal demotion is not possible then forcefully remove DC by running dcpromo /forceremoval followed by metadata cleanup.
Complete Step by Step Guideline to Remove an Orphaned Domain controller (including seizing FSMOs, running a metadata cleanup, and more)
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
Complete Step by Step Guideline to Remove an Orphaned Domain controller (including seizing FSMOs, running a metadata cleanup, and more)
http://msmvps.com/blogs/acefekay/archive/2010/10/05/complete-step-by-step-to-remove-an-orphaned-domain-controller.aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.itgeared.com/articles/1088-metadata-cleanup-for-active-directory_14/
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/77e8cfc4-e347-44c1-bc93-7b13f5f4671a