Question Locked

Replacing old 2000 domain with 2003 domain

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi

I have a nice task ahead. replacing our old and malfunctioning 2000 Domain with a new set of domain controllers and i complete new AD design and a diffrent role setup.

Normaly when upgrading i just install a new 2003 server and prepare the servers (forestprep + domain prep + dcpromo) and transfer all roles to the new servers and then depromote the old 2000 servers.

BUT

now sinc this domain/AD has some serious problems, we need to set up new roles.

I see some obvious problems beside the users management, thatis all the service accounts.

Is there a good practice of doing this upgrade? Transfering some data from the old AD?

And then how can you easily apply the new domain to all clients? Approx 500.

Best Regards Andr?

5 replies

by cg it

if your creating a whole new infrastructure, which by your comments

" have a nice task ahead. replacing our old and malfunctioning 2000 Domain with a new set of domain controllers and i complete new AD design and a diffrent role setup"

which is what it appears your doing,
why are you worried about the old Domain Controllers?

what does sinc this domain/AD has serious problems mean?

prep the W2K domain for W2003 DCS, let KCC do it's thing and DCs replicate. demote the old W2K server.

by andre.karlsson

To be more exact our "old" domain has some serious problems. More exact it has every major problem you can imagine :).

I don't want risk the same problem being replicated from our old domain to our new domain, that is the reason i dont wish to prepare our old domain to win2k3 status and replicate the data to our new servers and then depromote the old servers. Since i see the possibilty that our problems will follow.

//Andr?

This discussion is closed to new replies.