Adding a 2003 DC to and existing 2000 Active Directory network
I was reading this post but it didn't answer my question fully.
https://www.experts-exchange.com/questions/21507304/Windows-2003-compatibility.html?query=active+directory+2003+and+2000+work+together&clearTAFilter=true
- I have a client that is currently running a 2000 AD domain strucure.
- They are going to be moving to a new building soon.
- I want to add a 2003 DC to the network.
- When they move to the new location, move the 2003 DC to the new location and leave the 2000 DC at the old location so they have operability at both locations while they move.
Is this feasable? I'm going to be testing it in a test network but was interested to find out if anyone has tried this.
Thank you in advance.
https://www.experts-exchange.com/questions/21507304/Windows-2003-compatibility.html?query=active+directory+2003+and+2000+work+together&clearTAFilter=true
- I have a client that is currently running a 2000 AD domain strucure.
- They are going to be moving to a new building soon.
- I want to add a 2003 DC to the network.
- When they move to the new location, move the 2003 DC to the new location and leave the 2000 DC at the old location so they have operability at both locations while they move.
Is this feasable? I'm going to be testing it in a test network but was interested to find out if anyone has tried this.
Thank you in advance.
ASKER
Thank you for the response Jay_Jay70. What would happen when I remove the 2003DC from the network? Will the 2000DC take over and continue to manage the network?
it will but if you remove from the site completely, you need to make sure that you transfer the FSMO roles appropriately
Hi
I don't think Jay Jay covered this so just in case - a couple of practicalities:
In W2K the schema may need to have write access enabled to allow adprep to run. This needs to be run on the schema master but if you only have one dc then that'll be the one to run it on.
Schema Updates Require Write Access to Schema in Active Directory
http://support.microsoft.com/?kbid=285172
Also if you're running exchange 2000 server you need to run the following prior to adprep
Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers
http://support.microsoft.com/kb/314649
I've done what you're doing a couple of times now - no problems if you maintain the domain across a WAN but you don't say if you're planning on maintaining a connection between the two DC's or what your future plans are for them both. Jay Jay covered this part using AD sites and services etc.
If you add the 2003 server as a dc to the domain and then just unplug it and move it out to a new office you'll have problems with two servers that can't replicate. Even if you seized the fsmo roles on the non-fsmo holder and cleaned up AD on both - you'll end up with two dc's that both think they're the fsmo role holder for the same domain and then you want be able to bring them back together.
Deb :))
I don't think Jay Jay covered this so just in case - a couple of practicalities:
In W2K the schema may need to have write access enabled to allow adprep to run. This needs to be run on the schema master but if you only have one dc then that'll be the one to run it on.
Schema Updates Require Write Access to Schema in Active Directory
http://support.microsoft.com/?kbid=285172
Also if you're running exchange 2000 server you need to run the following prior to adprep
Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers
http://support.microsoft.com/kb/314649
I've done what you're doing a couple of times now - no problems if you maintain the domain across a WAN but you don't say if you're planning on maintaining a connection between the two DC's or what your future plans are for them both. Jay Jay covered this part using AD sites and services etc.
If you add the 2003 server as a dc to the domain and then just unplug it and move it out to a new office you'll have problems with two servers that can't replicate. Even if you seized the fsmo roles on the non-fsmo holder and cleaned up AD on both - you'll end up with two dc's that both think they're the fsmo role holder for the same domain and then you want be able to bring them back together.
Deb :))
ASKER
Good info Debsyl99, thank you very much!
I'm not going to be maintaining a connection via WAN for the Domain. I was planning on promoting the 2003 server to a domain controller so they will have a total of two DC's (one 2003 DC and one 2000 DC). When they are ready to move; move the 2003 DC to the new location and leave the 2000 DC running at the old location until they are completly moved out and then moving that to the new location as well.
There is no Exchange server on this domain.
Thanks again
I'm not going to be maintaining a connection via WAN for the Domain. I was planning on promoting the 2003 server to a domain controller so they will have a total of two DC's (one 2003 DC and one 2000 DC). When they are ready to move; move the 2003 DC to the new location and leave the 2000 DC running at the old location until they are completly moved out and then moving that to the new location as well.
There is no Exchange server on this domain.
Thanks again
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Fogot this one:
How can I transfer some or all of the FSMO Roles from one DC to another?
http://www.petri.co.il/transferring_fsmo_roles.htm
How can I transfer some or all of the FSMO Roles from one DC to another?
http://www.petri.co.il/transferring_fsmo_roles.htm
hmm just refresh me as to why we are transferring FSMO roles around? the only reason to really move the FSMO roles over is if you are planning on getting rid of a DC
there is a lot of text above and i only skimmed over it so apologise if i missed something
there is a lot of text above and i only skimmed over it so apologise if i missed something
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
basically all you need to do is run DCPROMO and add the new domain controller as an additional DC.
you need to run the adprep tools first though to extend the schema
with windows 2003 R2 (release 2) you will need to run the adprep tools from the second cd supplied in the 2 cd set!
\CMPNENTS\R2\ADPREP
you can also download here
http://www.microsoft.com/downloads/details.aspx?familyid=5B73CF03-84DD-480F-98F9-526EC09E9BA8&displaylang=en
this boosts the schema up to cope with R2 functionality
http://www.microsoft.com/windowsserver2003/r2/whatsnewinr2.mspx
after that, once replication has occured and you want to move to a new site, in sites and services, create an additional site for the new building and assign the DC to it, make sure your new DC is a global catalog as well, assign the subnets under sites and services and your home and humming free :)