Re: Replacing current DNS/DHCP server...

From: Sharad Naik (sharadnaik_at_nospam-vsnl.net)
Date: 09/10/04 

Date: Fri, 10 Sep 2004 13:32:08 +0530

What you want to do can be done as follows:

Point win 2003 to win 2000 for DNS and on win 2000 DNS , make sure that
dynamic updates are allowed.
1. First by running dcpromo make win 2003 an 'additional domain controller
for existing domain'.
See this link for the same:
http://support.microsoft.com/default.aspx?scid=kb;en-us;238369#5
Let the wizard install the DNS. After installation is completed allow time
for replication.
2.Make win 2003 Global Catalogue and allow time for replication.
3. In win 2000 DNS, make all the primary (forward / reverse) zones AD
integrated if they are not, and chose
replication to all domains in the domain controller. Allow time for
replication.
(Please note only AD integrate zones are replicated.)
4. If there are any secondary zones in win 2000 DNS, you should create same
secondary zones in win 2003 DNS
updating from the respective DNS server(s). Allow time for secondary zone
transfer.
5. Install WINS on win 2003 and make win 2000 & win 2003 replication
partners. Allow time for replication.
6. On win 2000 server backup DHCP database in a path available on the
network. Then install DHCP on win win 2003,
do restore backup giving the path of the above backup file. Check that
scopes , options etc. are properly created.
On win 2000 stop DHCP server and start DHCP server on win 2003. From one of
the clients do ipconfig /renew
and verify that win 2003 DHCP is serving the clients.
7. Break the WINS replication partnership between win 2000 and win 2003
after verifying the replication is
completed.
8.Remove Global Catalogue role from win 2000 Server.
9. Run DCPromo on win 2000 server and remove AD, (NOT select 'this is the
last domain controller ..)

Sharad

"Exo" <Exo@discussions.microsoft.com> wrote in message
news:32EA5E6E-1DC8-4F81-AF51-B22C66F5CB4B@microsoft.com...
> Hi,
>
> Currently, i have a domain controller (server) running on Windows 2000
> server, handling DNS, DHCP, Wins, and Active Directory services.
>
> I want to repace it with a new server running on Windows 2003. Basically,
> other than the computer name. I want to have exact same configuration
then
> demote the 2000 DC and remove it out of the picture.
>
> Currently, i already have a new server in question and i already installed
> Windows 2003 server on it. It 's still part of the Workgroup or just a
> StandAlone server. That is, it hasn't been promoted yet.
>
> 1) From here, how do i proceed with this DNS, WINS, DHCP, Active Directory
> migration?
>
> 2) Do need third party tools to perform these tasks?
>
> 3) I want to make sure that every configuration will stay intact. How do i
> do it?
>
> Any help on this would be much much appreciated.
> Thanks for your time and consideration.
>
> -Exo

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... DNS server has updated its own host records. ... If this DNS server's Active Directory replication partners do not have the ...
    (microsoft.public.windows.server.active_directory)
  • Re: multiple errors in Active Directory
    ... Connection-specific DNS suffix: ... If this computer is a domain controller for the specified domain, ... The attempt to establish a replication link for the following writable ... DNS server has updated its own host records. ...
    (microsoft.public.windows.server.active_directory)
Loading