Tranfering DC, DHCP, DNS, Exchange to new ser

Microsoft Windows server 2003 enterprise
April 1, 2010 at 10:08:00
Specs: Windows 2003, Dual 2.4 P4 Xeon CPU 2 GB Ram
Server 1 hard drive failed and the hot spare died during rebuild.

I need to transfer to new server. I have 4 servers

Server 1: Dual 2.4 P4 Xeon CPU (On Last Leg)
Domain Controller Win2003 AD Enterprise, Exchange Server 2003, DNS, DHCP, File Server.

Server 2: Dual XEON 3.0 CPU 4 GB Memory
Print Server, Backup Server. (Checked the backup and everything looks good to recover the files. I Looked and the Information store and backed up with no errors. I did not back up the mail boxes it was not in the selection. This server also has a different name to avoid any conflicts, not sure if the name change will benifit anything, it a small amount of user, under 30 users are on this domain, so if I have to go to each workstation to change the name for the exchange server so be it.

Server 3: Dual XEON 3.0 CPU 4 GB Memory
Application Server. This app is resource intensive and sould not be a DC.

Server 4: P4 2.8 CPU Only 512 meg Memory
Application Server

I want to transfer the current DC server 1 to Server 2, I want to move the FSMO (Already Done except the Schema) the Exchange Server and DHCP, DNS as well. I did not do the schema because when I click OK to do the transfer it said that I had to remove the old server right away and I know It would cause problems with the exchange server. I looked on this forum and others and I cannot find one thing with this type of senerio, I found somethings close but It was not the same. I already DCPROMO this server as well and I can see the user's in ADUC.

I'm looking for step by step instructions to do this transfer before server 1 goes down for good. I think I should have moved the DNS and DHCP first according to some forum suggestions. Can you tell me if this is true and if it is, is there still away to still move forward.

If you need further info, Please write back and I will provide it


See More: Tranfering DC, DHCP, DNS, Exchange to new ser

Report •

April 1, 2010 at 13:54:24

That's ^^ the step by step from MS.

Otherwise, there is a forum at
They do FSMO transfers on a constantly.

How do you know when a politician is lying? His mouth is moving.

Report •

April 8, 2010 at 13:38:32
Update - I installed DHCP, DNS on the new server and checked and made sure everything looked the same and it was on the old server. I Moved the FSMO's and it went over to the new DC with no problems. When I checked to see if the server moved the policies and batch files, and they were not there. I looked in the Event Viewer and discovered that NTFRS was not working. Alot of errors. After a little investagating, I discovered that the registry settings had to be changed to get the FRS to restart a fresh connection. I made the changes on both servers and with in five minutes the polcies folder started to fill up. Once that was done I installed Exchange Server. Installed the service pack 2 and updates to the system to equal the old server.

I opened the System Manager for Exchange and found the old Information Server Store and the New one there. I began to move the mailboxes from the old store to the new one with no errors. After that I checked every setup settings in the old store and made the appropriate changes to the new one.

Changed the firewall settings. I then checked several workstations to make sure they where pointing to the new exchange server and the settings were correct. Sent email to several users, which showed up in the correct mailboxs.

I shutdown the failing server down and been running with no issues all day.

I want to thank guapo for the help. I learned alot from this and I do get great enjoyment from the learning and the work I do.


Report •

April 8, 2010 at 14:11:50
Well done, I'm glad it's solved.

How do you know when a politician is lying? His mouth is moving.

Report •

Related Solutions

Ask Question