• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 214
  • Last Modified:

Adding a 2003 DC to and existing 2000 Active Directory network

I was reading this post but it didn't answer my question fully.

http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21507304.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.
0
andersenks
Asked:
andersenks
  • 4
  • 3
  • 2
2 Solutions
 
Jay_Jay70Commented:
Hi andersenks,

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 :)
0
 
andersenksAuthor Commented:
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?
0
 
Jay_Jay70Commented:
it will but if you remove from the site completely, you need to make sure that you transfer the FSMO roles appropriately
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Debsyl99Commented:
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 :))
0
 
andersenksAuthor Commented:
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
0
 
Debsyl99Commented:
Ok - so no worries on the exchange server part then. How long will you have the two separated? Generally my understanding with default settings is that you can keep the two separated for about 60 days tops without having to do a dcpromo/forceremoval and cleanup of AD prior to adding the second DC back in. The main problem you'll have is if you try and create user accounts at the site where the dc dos not hold fsmo roles resides ie RID master role. I'd consider the following:
DNS - make sure that prior to moving (and prior to running dcpromo) you point DC2003 at the original 2000DC's IP address as primary DNS server and itself as secondary. Make sure that DNS is AD-integrated on both servers in the Dns console and will accept dynamic updates and zone transfers from each DC. All DNS records should then get replicated between the two DC's. Prior to the move change the 2003 servers DNS to point at itself as primary DC and at DC2000 as secondary. Keep the 2000 DC pointing at itself as primary DNS server until you move it. Prior to the move also consider where you may make make changes within AD - ie user and computer accounts. If you're changing nothing at your original site but may change things at the new site then transfer the fsmo roles to DC2003 if that's the DC moving to new site or vice versa.
Also consider DHCP if that's being handled by either server. Depending in the number of workstations you have at either site you could configure DHCP to allocate two different address ranges on the same subnet - so making sure that all pc's will get the correct ip settings regardless of which site they're at. Both DHCP servers if configured will need to be authorised - see the link if you're not familiar with this.
As Jay Jay mentioned both servers will need to be set as Global Catalog servers. Another point to mention is that you need to make sure that the time difference in the clock settings on both dc's is well within 5 mins of each other before you try bring them back together or you'll get replication problems.
Just in case they're useful see the following:
How to install and configure a DHCP server in an Active Directory domain in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300429&sd=tech
Frequently asked questions about Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/kb/291382
Hope that helps
Deb :))
0
 
Debsyl99Commented:
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
0
 
Jay_Jay70Commented:
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
0
 
Jay_Jay70Commented:
ahh i see whats going on :) now i feel like a goose,

your going to run into some authentication issues at your new site,

to be honest, i would promote a new Domain in the new office, and then promote your old DC back in once you move accross, as far as i can see you are asking for trouble with the way you have planned
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now