• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 475
  • Last Modified:

Splitting Existing Windows Active Directory 2003

We have an Active Directory 2003 forest root domain XYZ.COM with two child domains A.XYZ.COM and B.XYZ.COM our email environment is Notes 8.5

The business is splitting into two independence entity due to take-over. We are now planning to create two new Greenfield Windows 2008 Active Directory Domains A.Com and B.COM and migrate A.XYZ.COM and B.XYZ.COM

Can you please advice the best approach / tools / method for the migration? Are there risks I need to bear in mind (DNS Trusts, etc)? Can I have a mixture of 32bit / 64bit Domain Controllers in the two new Domains / what are the benefits?

Many thanks
1 Solution
There is no facility to chop off part of the AD tree in this way.  You will have to create a new domain, migrate the accounts and users to it, then demote all DCs from the existing domain untill they are all gone and the child domain no longer exists.

There is no issue to having a mix of 32 and 64bit DCs - 64Bit machines can address more RAM and support advanced stuff like HyperV.
Mike KlineCommented:
I took it as he wanted to do a migration to the new domains not a "prune and graft" (not supported as KCTS said)

You can use a migration tool.  (trust should be setup between the target and source forest).  Microsoft makes the free ADMT  http://blogs.technet.com/b/askds/archive/2010/06/19/admt-3-2-released.aspx

Not sure how big you all are but there are also a few good third party migration tools.  Quest and NetIQ both make tools.  If you do have money to spend I'd look at Quest first.

I'd personally standup a new domain as a 2008 R2 domain.  That is only an 64 bit release.


Try not to shoot yourself in the foot by picking top-level real names for the domains. Go with second levels (ad.yourdomain.com) or fake ones (yourdomain.local). Picking yourdomain.com will just result in headaches.  
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Monika-DAuthor Commented:
Thank you all for your response.

Thank you for the clarification.

Yes, I want to do a migration to the new domains. Is 2008 R2 only a 64 bit release? Does that mean you cannot  have a mixture of 32 bit and 64bit Domain Controllers for W2k8 AD?

What are the possible headaches that will result from picking the first level rather than the second levels for real names for the domains?

Many Thanks
"What are the possible headaches that will result from picking the first level rather than the second levels for real names for the domains?"

Imagine you name your AD domain "company.com". Your corporate website is located at www.company.com and that name points to your webservers. When lazy people (like myself) on your lan need to go to your website and just type "company.com" into the browser, their computer will be connecting to your domain controllers rather than your web server. There are hundreds of questions on this site involving that very scenario and there are some pretty dirty hacks to get around it, but proper planning from the start can avoid it. You have the opportunity to not make that mistake. Most people inheriting poorly planned systems do not.

And yes, w2k8 is 64bit only. You can still mix domain controllers, but the 32bit ones will be 2k3 and your forest/domain functional level will be at most up to 2003 until they're all 2008.
Monika-DAuthor Commented:
Thank you jar3817 for the clarification.

Can anyone please point me to any repository where I can find a template design document for Active Directory 2008 R2 deployment?

Many Thanks
Monika-DAuthor Commented:
No comment
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now