Solved

What is the best procedure to replace a server running Windows Server 2000 with a new server running Windows Server 2003?

Posted on 2008-10-11
2
127 Views
Last Modified: 2012-05-05
Our domain controller is an HP ML370 Gen 1 PIII733 running Windows Server 2000 with Active Directory.  We also have an HP DL 100 running Windows Storage Server 2003 which is joined to the Windows 2000 domain.  We wish to replace the ML370 with a new ML 350 running Windows Server 2003 Standard Edition.  We have only one domain controller and we are not running Exchange Server.

Please advise which procedure is best.

Option 1
a) Upgrade the current ML370 Windows 2000 domain controller to Windows Server 2003
b) Join the new ML350 with Windows Server 2003 to the domain
c) Promote the ML350 to a domain controller
d) Remove the old ML370 from the domain

Option 2
a) Run ADPREP on the current Windows Server 2000 domain controller
b) Join the new ML 350 with Windows Server 2003 to the Windows 2000 domain
c) Promote the new ML 350 to a domain controller
d) Remove the old ML370 from domain


0
Comment
Question by:lakesidemetals
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 70

Accepted Solution

by:
KCTS earned 250 total points
ID: 22693239
The procedure is straight forward:

Install Windows 2003 on the new machine
Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)

Join the new machine to the existing domain as a member server

You now need to take the 2003 CD and put it in the 2000 Domain Controller and run ADPREP, specifically you need to run
Adprep /forestprep    followed by
Adprep /domainprep

Note: If the new Windows 2003 server is the R2 version use the version of adprep from the \CMPNENTS\R2\ folder on CD2, it its not the R2 version then use adprep from the i386 folder on the single 2003 CD.

Now back on the 2003 machine: from the command line promote the new machine to a domain controller with the DCPROMO command from the command line. Select -Additional Domain Controller in an existing Domain-

Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the "Global Catalog" checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

Now install DNS on the new server. Assuming that you were using Active Directory Integrated DNS on the first Domain Controller (and if not why not, it far more efficient, resiliant and more secure), DNS will automatically replicate to the new domain controller along with Active Directory. You will also need to configure a forwarder on the new DNS server http://www.petri.co.il/configure_dns_forwarding.htm

If you are using DHCP you should might want to spread this across the domain controllers (if you intend to keep both), or move it to the new DC, In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same network that does not overlap with the existing scope on the other Domain Controller. Dont forget to set the default gateway (router) and DNS Servers. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other.

Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP. and the domain could function for a while at least should any one of them fail. However for a fully robust system you need to be aware that the first domain controller that existed will by default hold what are called FSMO Roles. There are five of these roles that are held on a single server and are essential for the functioning of the network. If the second Domain Controller fails, then no problem as the FSMO roles are on the first Domain Controller.

If you really want rid of the original DC, then its vital you transfer the FSMO roles http://www.petri.co.il/transferring_fsmo_roles.htm

Make sure all clients are using the new server as the preferred DNS server (and that the new server points to itself for DNS). You can then power down the original DC and chack it all still works.

Once you are happy all is ok, power back on the original DC, DCPROMO it to remove AD and then remove it from thr domain
0
 

Author Comment

by:lakesidemetals
ID: 22693809
Thank you for the quick response.  I'll need a couple of days to test the solution before closing the question.
0

Featured Post

Raise the IQ of Your IT Alerts

From IT major incidents to manufacturing line slowdowns, every business process generates insights that need to reach the people required to take action. You need a platform that integrates with your business tools to create fully enabled DevOps toolchains.

You need xMatters.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

690 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question