Domain Controller and Exchange migration to new hardware

Domain Controller
Exchange Server
Microsoft Exchange migration
Dear friends, I'd like to ask about how to migrate a domain controller onto different hardware as this domain controller is as slow an Exchange server (one machine). I have a new server and i'd like to replace the old one with the new one. Thank you!

Answer Wiki

Thanks. We'll let you know when a new response is added.

The process is as follows:

Install Windows 2003R2 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 R2 machine to the existing domain as a member server

Take CD 2 from the Win2003R2 disks and insert it in your existing DC and run
Adprep /forestprep
Adprep /domainprep

NOTE: Adprep is in the \CMPNENTS\R2\ folder on CD2.

Once done you can then remove te CD and go back to the R2 machine.

Now back to the 2003R2 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)

Install DNS on the new server. Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will automatically replicate to the new domain controller along with Active Directory.
Don t 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 the new domain controller.

Check this link for transferring FSMO roles to the new DC.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Elegant
    I would personally use a program like StorageCraft Shadowprotect which has Hardware Independant Restore functionality. The process is, take existing server down, image backup (using shadowprotect) to a USB disk big enough to store entire disk space of old server. Leave old server down. Take new server, boot using shadowprotect CD, use the HIR restore function to restore C and D partitions (or however many you have), the HIR process basically asks for the correct drivers for things like RAID hardware, Motherboard chipset etc. Then after a little fiddling (read the documentation, its pretty good, but you need to research) around you will have a spanky new server running Exchange, Domain that your users will never know you have had downtime on. This method does not in anyway alter your existing, I would assume stable server, so you always have a fall back if the server migration goes wrong, or takes too long (and more to the point, gives you a perfect opportunity to practise!!)
    130 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: