RE: Adding a new Windows 2003 DCs to existing Windows 2000 domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Rodney (Rodney_at_discussions.microsoft.com)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 09:01:04 -0800

Thankyou very much for your help.. You are right about what I want to do
with the domain. Our end goal is to migrate all our DCs to 2003 to take
advantage of the new technology. Our DNS is Active Directory Integrated so
DNS sounds like it should be ok and I have used the DHCP backup and restore
tool once to move DHCP to another server so I should be good.

Again thankyou very much for your help it has put a lot of my questions to
rest.

"Frances [MSFT]" wrote:

>
> Hello Rodney,
>
> Good to hear from you.
>
> According to your message, I understand that you want to add 2 new win2k3
> DCs to the existing win2k domain. In the long run, you will end with a
> domain with 2 win2k3 DCs. Is this correct?
>
> You plan to add new win2k3 DCs into the domain, migrate DNS and DHCP roles
> to the win2k3 DC and then demote win2k DCs is quite good. Please don't
> worry about win2003 DCs coexisting with win2000 DCs in the same Domain. You
> can set the win2k3 domain function level to the Windows 2000 native.
>
> More information about the domain function level is available in the
> article below.
>
> Domain and forest functionality
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/p
> roddocs/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/stan
> dard/proddocs/en-us/sag_levels.asp
>
>
> As for the Exchange part, you may post in the
> microsoft.public.exchange.setup newsgroup to get the most accurate
> information.
>
> I will give you some information regarding your scenario.
>
> 1. Adding win2k3 DCs to win2k domain
> ============================
>
> Please use "adprep" to upgrade your win2k domain to win2k3 domain. After
> that procedure, the domain will contain the additional objects, attributes
> and permissions necessary to support the Windows Server 2003 Active
> Directory environment. Then you can add win2k3 DCs into the domain.
>
> The following articles are for your reference.
>
> Upgrading Windows 2000 Domains to Windows Server 2003 Domains
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
> guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
> ployguide/en-us/dssbf_upwn_zfid.asp
>
> Since "adprep" should run in DC containing certain roles, you may find the
> article helpful to view FSMO roles of a DC.
> 255690 HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
> http://support.microsoft.com/?id=255690
>
> 2. Migrating DNS
> ============
>
> If your DNS is AD-integrated, you don't have to migrate DNS. Because when
> you install AD-integrated DNS on 2k3, this process will auto replicate DNS
> from 2k to 2k3.
>
> If this is not the case, you can create a secondary zone to replicate the
> DNS information.
>
> 1) Create a secondary zone on the win2k3 DC for the zone on the win2k DC.
>
> 2) Transfer the zone over to the win2k3 DC.
>
> 3) Change the secondary zone on the win2k3 DC to a Standard Primary Zone.
>
> It is recommended to have AD-integrated zone because AD offers multimaster
> update and enhanced security. You can also enjoy the features. For example,
> DNS zones are replicated and synchronized to new domain controllers
> automatically whenever a new one is added to an Active Directory domain. In
> addition, directory replication is faster and more efficient than standard
> DNS replication.
>
>
> 3. Migrating DHCP
> ===========
>
> DHCP migration is simple. The following KB article provide good
> information. Although the source DC is NT, it also applies to win2k.
>
> 325473 HOW TO: Move a DHCP Database from Windows NT 4.0 Server to Windows
> Server 2003
> http://support.microsoft.com/?id=325473
>
>
> Hope this helps. If you have any further questions, don't hesitate to get
> in touch!
>
> Best regards,
>
> Frances He
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Relevant Pages

  • Re: Failure to replicate - new 2003 sp2 DC
    ... How DNS is setup in both DCs? ... Can both DCs solve each other domain? ... trying to get to replicate. ... Nar's FRS event log shows the following event sequence: ...
    (microsoft.public.windows.server.active_directory)
  • Re: DC RAID Configuration
    ... DNS is kind of a case of you generally have to do it, but if I have a choice, I won't put that on DCs either, especially in larger orgs, I tend to prefer DNS on UNIX especially if I need to do a lot of delegation to other admins. ... Just for your info the DCs will all host DNS and most likely DHCP too. ... ship disks to remote geographic locations to keep the servers up. ...
    (microsoft.public.win2000.active_directory)
  • Re: What needs to be transfered to new Domain Controller
    ... I forgot to mention that this is one of our child domains, with 2 DCs running ... I am using AD-int DNS. ... Please describe first the roles your servers have now, DNS, DHCP, Exchange ...
    (microsoft.public.windows.server.general)
  • Re: I can not figure out why?
    ... I have two windows 2000 DCs and two Windows 2003 DCs. ... all workstations new DNS to point the new DNS through the DHCP server ... you must be careful when selecting the new servers to be DNS servers. ... If the zone is ...
    (microsoft.public.windows.server.active_directory)
  • Re: Scavenging question
    ... I think that "DCpromo cycling" mentioned by Herb means "Demote your DCs and ... If you have another DC, you can transfer FSMO to that DC, clean install the ... Clients recieve all DNS information via DHCP so in that way XP ...
    (microsoft.public.win2000.dns)