Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failed Removing Active Directory

Status
Not open for further replies.

Cisco79

MIS
Sep 19, 2003
27
KW
I had more than one domain controller with name xxx.local , and i decided to change the domain name to yyy.com. I started with some domain controllers and everything is ok.
HOwever, I'm trying to remove the Active Directory from the last domain controller , I get the following msg(( The operation failed becuause: The server is not the last domain controller in the domain ))
and when i try to remove it without checking (this is the last domain controller in domain))
i get the following msg :
((failed finding a sutiable domain controller for the domain xxx.local , the specified domain either doesn't exist or couldnt be contacted))
Moreover , this DC has an Exchange2000 which i dont need it any more and i cant remove it as well..
anyone know what my problem is?
um i dono if this help but i have done a domain trust between old and new domain xxx.local and yyy.com , however even after i remove it i got same msgs.
thank you ;)
 
Looks to me that you need to seize the FSMO roles on your new domain controllers... including the schema FSMO.

There have been lots of threads about this recently. Search for those here.
 
Dear hunterdw,
No , I just want to remove the active directory and exchange from my old DC, it will become a memeber server then in the new domain, not a new DC.
I didnt find any thread sorry, can you give me one link.
thnak you
 
Read here..


Not the exact problem you have, but it outlines the fsmo

Here's what I'm assuming... it appears that since you want to remove active directory from your old DC, you first have to make sure any FSMO roles that that DC holds are transferred to other machines. If you want to remove active directory from a DC that holds the SCHEMA fsmo role, you'll have do do that before demoting it via dcpromo.

Make sense?
 
Thank you for the link, but it is not my problem.
i have only 3 FSMO, where is the other 2?
 
Before you can remove a 2000/2003 domain controller, especially one that holds FSMO roles for any domain, you must ensure that the GC for that domain has been moved to another domain controller.

So, you have a couple options.

1) you can put that old computer back in place and do a dcpromo and demote it. When that server is demoted back to a member server, dcpromo finds another appropriate domain controller and moves the FSMO roles to that DC.

or

2) if you have removed the FSMO and can't find it, of if you have fdisk/gdisk'ed the computer you can still take care of things.

Start from a command line "ntdsutil" without the quotes. Type "roles" without the quotes. The command promt will change to "fsmo maintenance:" without the quotes.

Type "connections" without the quotes. the prompt changes to "server connections:" without the quotes.

type "connect to server servername" without the quotes and where servername is the server that you can to transfer the FSMO role to.

type "quit" without the quotes to return to FSMO maintenance.

Type "transfer fsmotype master" without the quotes. You will have you confirm.

If taht works, yeah. If not, type "seize fsmotype master" without the quotes.

type "quit" without the quotes twice and you are done.

You may need to transfer the RID FSMO or Schema master or whatever. If so, use the "transfer rid master" or "seize rid master" or "transfer domain naming master" or "seize domain naming master" or "transfer schema master" or "seize schema master" as appropriate.

One word of caution. If you size a RID, domain naming or schema master, make sure you NEVER EVER EVER plug that old master computer (the one that used to have the fsmo role) back in again. You'll wreck your AD if you do. Wipe it.

Make sense?

--DW
 
You need to change the roles, so that server is the master, like what they say above, but then you'll probably have to go into the ntdsutil and clear out all other sites and other servers that are orphaned in there..


BuckWeet
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top