Forest root restoration after domains physically relocated

[Brett Hunsaker]

We had a single forest made of of two domains (say a.com and b.com).
"a.com" had a single domain controller, was the first domain and thus the
root of the forest.

All the machines in the b.com domain were physically relocated. Now the
domain controllers cannot contact the root domain, have no Enterprise or
Schema Admins groups, and other consequences in our failure to plan this
move.

So, is there any concept of promoting one of the DCs in b.com to become the
new root? How to we reinstate the Schema Admins and Enterrpise Admin
groups?

Any pointers would be appreciated.

 

[Herb Martin]

We had a single forest made of of two domains (say a.com and b.com).
"a.com" had a single domain controller, was the first domain and thus the
root of the forest.

All the machines in the b.com domain were physically relocated. Now the
domain controllers cannot contact the root domain, have no Enterprise or
Schema Admins groups, and other consequences in our failure to plan this
move.

So, is there any concept of promoting one of the DCs in b.com to become the
new root? How to we reinstate the Schema Admins and Enterrpise Admin
groups?

No, there is no support for domain prune and graft from
one forest to another.

Any pointers would be appreciated.

Get back a minimal DC for the Root and maintain
it just for that.
[/QUOTE]