LittleFishy
MIS
I've got a domain controller server currently running Win Server 2000 which is running out of space so I want to replace it with a new server which will be running 2003. Ideally I don't want my users to notice that the server has been changed, so from what I've read I have to do the following:
New server as member server.
Demote existing domain controller to member, rename and turn off.
Rename the new server & IP (to old ones) and then promote.
Is it as simple as that and will there be any problems with 2000 & 2003 domain controllers on the same network?
Our current network was originally setup with a file & print acting as a domain controller (the one I want to replace), a exchange server also running AD and then the same combination at another site (4 domain controllers in total).
I've seen a few postings asking similar questions, but I want to get it right so would be grateful if anyone could confirm I'm going to be doing it right.
Thanks.
New server as member server.
Demote existing domain controller to member, rename and turn off.
Rename the new server & IP (to old ones) and then promote.
Is it as simple as that and will there be any problems with 2000 & 2003 domain controllers on the same network?
Our current network was originally setup with a file & print acting as a domain controller (the one I want to replace), a exchange server also running AD and then the same combination at another site (4 domain controllers in total).
I've seen a few postings asking similar questions, but I want to get it right so would be grateful if anyone could confirm I'm going to be doing it right.
Thanks.