Link to home
Create AccountLog in
Avatar of BobPrinceExpert
BobPrinceExpertFlag for United States of America

asked on

Need to remove un-necesary lower level AD Child Domain as part of new server install/migration.

We have a W2003 AD Domain "city.local" and a child domain of "library.city.local"
The Domain controller for "Library.city.local" is a W2000 AD system - that is being replaced with a W2003R2 system.
The parent Domain is W2003.
It has been decided that the child domain is not required.
We want to find the best method to eliminate the child domain - to minimize the effect on several PC systems
and a Terminal Server that uses a GPO lockdown. A new terminal server will also be introduced.
Wish to transfer as many objects (Computer accounts, users, policies) as possible trying to minimize effort.
There are several PC's that use a hardware lockdown system and GPO lockdowns.
We can do it the hard way - move PC's to workgroup, export AD accounts,etc but looking for time saving steps.
Avatar of martin_babarik
martin_babarik
Flag of Czechia image

Hi, I'd say this article is the info you are looking for:
http://support.microsoft.com/kb/326480/en
Let me know if there is something you want to be explained further.
Regards

Martin
ASKER CERTIFIED SOLUTION
Avatar of ManicD
ManicD
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of BobPrinceExpert

ASKER

We will look in to "movetree" as that sounds like it fit's in to what we plan to do.
Basically since we are installing new servers - we will set them up in the parent domain.
THen sounds like we can use "movetree" to move over objects that we still need.
In some cases - we have some generic users - so probably recreate them - but move over GPO's,etc.
Thanks for the tip.
Bob