Migrating a single W2K DC to a single W2K3 DC

By martian ·
I'd like to pose this question to see what my alternatives are.
We have an aging P-III W2K server that is the DC for our domain. It is our only Windows server. Exchange is NOT used here.
We have procured a newer P4 W2k3 server to replace it. The current plan is to decommission the old server on completion of the migration process.
Presently, it appears that I have two options:
1- Prepare the domain for insertion of a w2k3 server into it, bring up the new server as a member server in the same domain, promote it and transfer all the functions and finally demote and remove the old server.

or 2- bring up the w2k3 server as a new forest/domain, create the necessary trusts, migrate the functions, then remove the old forest/domain and rename the new one.

We would really like to be able to keep the current domain name as something else would be kinda goofy. (we're using businessname.local)
I haven't found anything in Microsoft's documentation that clearly says you can re-use the old name. Then again, all their scenarios are based on enterprise models which use more than one server.

Any thoughts, advice, recommendations and pitfalls to avoid would be appreciated.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Use Option 1

by scott_heath In reply to Migrating a single W2K DC ...

Microsoft has articles describing how to do just want you want. You'll need to prep the current domain for the schema extension of W2K3. I believe it is adprep, yes? The do what you suggested. promote the W2K3 server, then demote the W2K server.

Collapse -

Option 1 sounded right

by martian In reply to Use Option 1

Option 1 sounded right.
My concern was that the current domain was previously upgraded/migrated from NT and I wasn't sure that any of the "flawed leftovers" would carry across. I don't want them to!
And from my reading so far, yes adprep is the procedure used that I was referring to for preparation for insertion of a ws2k3 server.
I'm planning on doing this over the holidays to ensure no downtime for my users.
Ah, the trials of being a one server shop...
I'm just glad our email server is not on Exchange!

Thanks for the helpful reply

Related Discussions

Related Forums