Remove subdomain from 2003 Forest

This is how our network was set up...

Main HQ with three branches.  We were going to have the TLD as company.local and then subdomains for each branch including a subdomain for HQ, which would be hq.company.local.  We went so far as to create the subdomain hq.company.local on a 2008 R2 box but never wound up using it.  The DC for hq.company.local has been powered off since April 2011.  AD Sites and Services indicates that AD Connections exist between hq.company.local and the TLD DCs as well as the other subdomain DCs.  We want to now remove the hq.company.local subdomain.  I just powered it back on and tried to run the AD replications to it manually using ADSS, which failed.

Since AD replication is failing to hq.company.local, I'm assuming that if I demote the hq.company.local domain controller that AD throughout the entire company will not reflect that the hq.company.local subdomain has been removed.  

Not quite sure where to start here in getting hq.company.local fully removed from my forest, which is in 2003 mode since all 3 TLD DCs are 2003 x64 Enterprise.  Any suggestions?
sedberg1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Try demoting if this fails then go through a metadata cleanup to remove the data out of AD.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm
0
sedberg1Author Commented:
I understand that I would demote the hq.company.local domain controller.  However, the metadata cleanup would be done from where?  We have three DCs on the TLD: AD1, AD2, and AD3.  AD2 hosts all 5 FSMO roles.
0
Darius GhassemCommented:
From any one of the functioning DCs.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

sedberg1Author Commented:
So I had to force remove AD from the hq.company.local DC since it kept failing at authenticating with the TLD to remove DNS delegation.  The AD connections are still present in ADSS on the TLD.  Should I manually delete those?  Should I do that before or after metadata cleanup?
0
Darius GhassemCommented:
Do metadata cleanup
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sedberg1Author Commented:
Ummm...so do I do metadata cleanup before or after deleting the AD connections?
0
Darius GhassemCommented:
Just do that metadata cleanup this will remove all lingering objects for this subdomain
0
sedberg1Author Commented:
The instructions are for removing a domain controller from a domain that includes more than one domain controller.  My issue is that this is a single domain controller in a subdomain.  If I remove the single domain controller, will it automatically remove the subdomain as well?
0
Darius GhassemCommented:
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.