SBS 2003 server included in a Server2003R2 domain, but now can't demote or remove from the Domain

Well after ready many other similar issues on the subject, I understood that it's trick/hard/ not possible to include an SBS2003 server on my Server2003R2 Domain.
Well I managed to include it and make it a Secondary Domain Controler.

Now after reading issues on SBS2003 with my Domain, I want to remove it.....

and there is nothing I can do, I get -> "can't access the domain!!!" which is weird because I login to this SBS box from the domain, and cannot login on this machine.

So other,than format reinstall, what can I do to make this machine a simple computer in or out of the Domain!
nomore active directory so it stops complaining and rebooting every 60 min.

Thanks

Crs707Asked:
Who is Participating?
 
KCTSConnect With a Mentor Commented:
You could try DCPROMO /Force but I don't expect that to work either. As LeeW says Sieze the FSMO roles (see http://support.microsoft.com/kb/255504), phusically remove the 'in limbo DC' and run a metadata cleanup ( see http://technet2.microsoft.com/WindowsServer/en/library/012793ee-5e8c-4a5c-9f66-4a486a7114fd1033.mspx?mfr=true) to remove all traces of the failed DC from Active Directory.
0
 
KCTSCommented:
SBS Cannot participate in an existng Domain, You can however add additional Win2003 DCs to an SBS domain. Somehow it seems that you have partially put the SBS machine into a domain and it is now in a state of limbo where is is neither truely in the domain nor truely out of it either.

I don't see any alternatve but you just remove it physicaly and then remove all traces of it from your Win2003 AD. You can then rebuild the SBS server from scratch.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
You're stuck.

SBS CAN participate in an existing domain, but it MUST be made the FSMO master domain controller.  You simply cannot make the SBS server any other kind of server.  It MUST be a domain controller and it MUST be the FSMO master - you wanted to buy a "cheaper" version of Windows Server with Exchange and possibly other applications... but that discount has certain strings attached.  And you're trying to cut them - which is a violation of the license agreement and results in reboots of the server every hour or so.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Crs707Author Commented:
Alright, makes sense...

but now how can I change or remove that server?

DCPROMO fails

can't put it on a workgroup

I can't login to the machine I'm stuck in the domain!!!

tks
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Power it off.  Use another DC to seize the FSMO roles.  That's pretty much the only way you're going to be able to get rid of it - which also will require an NTDSUTIL metadata cleanup.
0
 
Crs707Author Commented:


The computer is now a stand alone machine, and based on you previous comments and other comments I have read, it looks like it will stay on a workgroup, since I can't make this a "computer" in my domain, since it has to be the DC FSMO master....

Thanks again.

cheers.
0
All Courses

From novice to tech pro — start learning today.