What are the implications, if any, of adding a Windows 2003 server to our existing 2000 domain? We have four 2000 DCs at the moment with ISA and Exchange.
Thanks in advance![]()
What are the implications, if any, of adding a Windows 2003 server to our existing 2000 domain? We have four 2000 DCs at the moment with ISA and Exchange.
Thanks in advance![]()
None bad I wouldn't have thought.
Depends on what you intend to do with it... please speculate on the subject i.e. is it going to be the new DC, an app server, etc?
Cheers,
Nath
If you add a 2003 DC you will need to update the schema. Im not sure if that is the case with just a member server as well but Im sure someone will clear that up.

The schema only needs updating if you add a DC. To be honest, you will probably want the server to be a DC as it will be the start of your migration to 2003.
If you are going to migrate to the server, I've found the active directory migration tool works well, you'll find you have to add it as a component though (which seems silly to me, but hey, it's Microsoft!!)
Stewart Knight
Network Manager
Appleby Grammar School
You have to run "forestprep" and "domainprep" to prepare your existing AD setup. Those are both on the I386 folder of your Windows 2003 Server CD if my memory serves me right.
I chickened out of doing any of that lol
I used the ADMT (as mentioned above) to transfer the users to the new domain. I manually exported the shares (as I was transfering the data HDD to the new server) and voila - worked really nicely (except for the passwords as it wouldnt do it. Might be coz the old server was a NT4 server - I'm not sure but it didn't cause me *too* much hassle).
Stop posting ppl...I'll never get anymore work done at this rate lol
N.
I managed to get users and passwords over from NT with no problem using the ADMT. The problem I had was getting the new machines to join the domain. In the end I had to script the unjoing and joining using netdom.
Were you doing it on the same domain? i.e. old DC to new DC (currently member server to be promoted to DC) but on the same domain?
I created a new domain for the purpose so maybe this was the trouble but it did all i needed. I wasn't interested in the computer objects because the NT domain and server was very "basic" if ya know what I mean and I took it as far as I could learn and needed to.
GP is a dream compared to the old systemI still use it tho of course to lock down 98 - I custom made adm's and although it took a bit of tweaking, it works really well
Regardes,
N.
Hi.
A little late perhaps, but we added a new 2003 DC to our existing 2000 AD domain (for SIMS etc) and carried out the obligatory "forestprep" and "domainprep" without any problems.
It's chugging away happily now![]()
Paul
We are replacing both of our DC's which currently have win2k on them with 2 new servers running win2k3.
As far as i understand if they are join an exsiting domain then there should not be a problem and should be a smooth transition.
If you are adding your win2k3 server purely as a member server then there should be no knock on effects to the win2k domain.

@ICTNUT: Adding member servers has no effect, but if you add 2003 DCs you MUST update the schema first (setup /forestprep & setup /domainprep).
i migrated to 2003 domain last year and even wit hthe state of the 2000AD it migrated fine, tbh its all gone wizard idiot proof and microsoft hold your hand for 99% of it
There are currently 1 users browsing this thread. (0 members and 1 guests)