Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Start new W2k3 Domain without upgrading older W2k DC

Status
Not open for further replies.

Bigtm

IS-IT--Management
Nov 2, 2006
52
GB
Hello, Just for information, if I wanted to start a new W2k3 Domain complete with users, groups, organisational units e.t.c. but not upgrade the existing W2k DC or join the existing domain with view to promoting the W2k3 server to DC status, how would i procede?

I want to extract the W2k DC AD structure and import it to a brand new W2k3 domain controler. Why do that when there are other option you may ask but I am rather interested on your pro thoughts. Come on lads(and ladies), lay it on me.

Many Thanks,
BigTM.


 
With this scenario you have 2 choices:

1) Join the existing domain, promote the 2k3 server, seize all FSMO roles, then demote the 2000 DC.

2) You could setup a forest-level trust between your 2003 and 2000 domains. Then, you have to migrate the resources from 2000 to 2003.

I highly recommend that you concentrate on option 1. Option 2 would be a pain because migration is not as simple as it might seem. If you do migrate, I suggest the Quest Domain Migration Wizard for the software. Some use the ADMT, but I prefer the Quest tool.
 
I never recommend seizing roles if possible. TRANSFER THEM GRACEFULLY. And if you do that, you have a lot of preparation to go through to make sure you don't create problems and you should ALWAYS do a backup.

Another option is to use the Active Directory Migration tool to move users to the new domain. Frankly, I think it's doing things the hard way and I RARELY recommend going this route. In my opinion, it's better to simply upgrade the domain.
 
When I said seize, I was not specifically talking about seizing them via ntdsutil. I agree 100% transferring FSMO roles is the way to go.

As for migration, as I said, I think that is a bad idea as well.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top