Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 419
  • Last Modified:

Removing AD server that is no longer available 2003 R2 Schema

I have a 2003 R2 AD Domain.

One of the two DC's failed recently.  It was not the one holding all the roles thankfully.

What is the simplest way to remove this.  Should I first add another DC?

Additionally I do have some 2008 R2 MEMBER servers as well as Win7 member PCs.  What is the best method to upgrade the Schema.

I realize that you cannot detail every step for every post but I have seen the recommendations by Microsoft and I do not find their explanation clear.  

If you could lay out the steps in Dummy language first I appreciate it as I do not like taking action on such critical systems without being sure what I am doing is safe.

Thanks

Doug
0
mikromikro
Asked:
mikromikro
  • 4
  • 3
  • 2
  • +1
1 Solution
 
BlackBoxTechCommented:
Does the failed DC still boot, if so here's a good step-by-step for forceful removal: http://blogs.technet.com/b/asiasupp/archive/2006/09/06/454327.aspx

If the DC will not boot, then you'll need to use ntdsutil from the existing DC, here's a good how-to: http://www.petri.co.il/delete_failed_dcs_from_ad.htm

Lastly, if you run a dcpromo on one of the 2008 boxes it will update AD, however, you still need to address the issue of the failed AD.
0
 
mikromikroAuthor Commented:
Should I first add another DC before doing the cleanup?

Is it common for this task to create any problems?  If so what are they.

If not is there anything I need to look out for while doing this.

If I do not need to use that server name again what harm is there in leaving the DEAD server in AD.  It is surely ugly and seems like poor management BUT it may be safer to not do anything  (Hence why I am asking).

Is there any issue do this during the day.  Very small domain with 3 member servers and only 10 member user computers.

Thank you very much for the quick response.  It seems like just what I need.

I do not understand the SCHEMA UPDATE info.  Are you saying just joining the 2008 R2 server to the DOMAIN will update the schema to 2008 R2 OR that is only true if I make a 2008 R2 server a DC  (not a member server).

That said since my 2008 R2 server is a MEMBER server and NOT a DC how do I update the SCHEMA to 2008 R2 from 2003 R2.  I had updated the schema to 2003 R2 several years ago using instructions from one of you (Microsoft) back then.

Thanks

Doug
0
 
BlackBoxTechCommented:
No, you do not need to add another DC. If you're existing DC has all 5 FSMO roles there should be no issues.

Leaving the failed DC in AD will cause havoc in time (not recommended to leave it). Yes, you can do it during business hours, but I'd recommend after hours just in case there is a problem, you will have time to address it w/o business interruption. A lot of AD issues stem from DNS related problems. If you run a dcdiag on your DC before the upgrade at least you'll know if the schema's are healthy before you start.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
mikromikroAuthor Commented:
Well I am planning to add another DC anyway  (2003 R2 as we have the server) so what I am asking is should I add it before I do this removal or after?

Can you give me any advice of the Schema portion of my question.

I had said

>>>>
I do not understand the SCHEMA UPDATE info.  Are you saying just joining the 2008 R2 server to the DOMAIN will update the schema to 2008 R2 OR is that only true if I DCPROMO the 2008 R2 server a DC  (not a member server).

That said since my 2008 R2 server is a MEMBER server already and NOT a DC how do I update the SCHEMA to 2008 R2 from 2003 R2.  I had updated the schema to 2003 R2 several years ago using instructions from one of you (Microsoft) back then.
0
 
Sarang TinguriaSr EngineerCommented:
To upgrate the schema you would need to run adprep /forestprep adprep /domainprep /gpprep on the 2003 R2 DC

Adprep utility can be found on your 2008R2 Media

See below link for step by step
http://www.petri.co.il/windows-server-2008-adprep.htm
0
 
BlackBoxTechCommented:
I'd add the second 2003 before, but it really doesn't matter.

As for the schema question, hopefully the below excerpt will shed some light:

"When you change the schema on the schema master, the changes are automatically propagated to all other domain controllers in the forest. Therefore, it is not necessary to perform this operation on other domain controllers. Also, there is no need to run adprep /domainprep in any child domain where you have already installed a domain controller running Windows Server 2003 with Service Pack 1 (SP1). The necessary domain partition updates were performed when the domain controller running Windows Server 2003 SP1 was installed."

From: http://technet.microsoft.com/en-us/library/cc773360(WS.10).aspx
0
 
Sushil SonawaneCommented:
Refer the following link to  delete a failed Domain Controller object from Active Directory

(http://www.petri.co.il/delete_failed_dcs_from_ad.htm)

If you want to add another DC in network which have 2008 server OS installed then please refer these link.
(http://technet.microsoft.com/en-us/library/cc733027(v=ws.10).aspx)
0
 
mikromikroAuthor Commented:
BlackBoxTech

I do not follow the relevance of the schema comment you left or the link.  It discusses upgrading to 2003 R2 schema.

I was asking about the 2008 R2 Schema BUT I am not installing any 2008 R2 DC's presently just member servers.   It sure seems I have no reason to upgrade the schema?  

Reminder which I may not have made clear  --> I have ONLY 2003 R2 DC's.

This link seems to say only if I am adding 2008 R2 DC's should I upgrade schema.  http://www.petri.co.il/prepare-for-server-2008-r2-domain-controller.htm

sushil84

You left two links that have no value.  
The first link you left was already left in the first response.
The second link you left talks about adding a 2008 DC.  I never mentioned adding anything in Server 2008 plus even 2008 R2 I had mentioned was only as a member server.  This link would be for adding 2008 R2 DC's but it makes it pretty clear that I need not upgrade the schema at all since I am not adding 2008 R2 DC's.  AGREED???

http://www.petri.co.il/prepare-for-server-2008-r2-domain-controller.htm
0
 
BlackBoxTechCommented:
Yes, you are correct. You do NOT need to upgrade the schema if all you're doing is adding another 2003 DC.
0
 
Sushil SonawaneCommented:
If you not adding 2008 domain contoller in network and only keep as member server then you don't require upgrade schema version.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now