• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 290
  • Last Modified:

How to Migrate from Server 2003 to Server 2008 Box.

I have a 2008 server, running Exchange 2007. My DC is server 2003, I want to move the DC to that new server as well. I want to use the old server for a different project, and also learn more about 2008 Active Directory.

 Does anyone have any links to help me out with this, i'm trying to search google. I don't really find much on it, the only help that comes up is this same explaination but in different links. http://www.biztechmagazine.com/article.asp?item_id=324

Do I dcpromo it, move the fsmo roles, and global Catalog as I would 2003. I know i have to run adprep, and etc. I've done that already for the exchange server. Also Do I have to focus on anything for the Exchange server part of it, I know best practice is not to have DC on server 2008. I'm on a budget right now.

Thank you in advance I appreciate any help!
  • 2
1 Solution
The correct procedure to transfer all the critical Domain Controller roles is as below. Please note that you cannot change the DC role of the server whilst Exchange is installed as this will break Exchange - you need to uninstall Exchange before you make the changes shown below.

First you need to run ADPrep /domainprep and ADPrep /forestprep on the existing 2003 DC. The ADPrep.exe tool is within the Sources folder on the Server 2008 DVD. Once these commands have worked successfully, you can continue.

The only DNS server configured at this stage on the new server should be the IP of one of your other Domain Controllers. Use dcpromo to promote the server as an additional domain controller in the existing domain after you have removed Exchange temporarily.

Ensure DHCP, DNS and Global Catalog roles are moved across to your new server. If you are using AD-integrated DNS (which you should) this is as simple as installing the DNS server on the new server (DNS information will replicate with AD) and the DHCP configuration simply needs to be copied from one server or the other. Make sure the DNS server addresses in DHCP AND any statically assigned devices point to one new server for primary, and the other new server for secondary DNS if you install DNS onto it.
For DHCP if you spread it around multiple servers, it is as simple as setting IP scopes on the correct subnet which DON'T overlap (otherwise both servers will give out the same addresses and you will have IP conflicts)

Make sure all the FSMO roles are removed from the first server and transferred to one of the other servers. If you are a single-domain environment, there are no performance or functionality gains from spreading FSMO roles around between servers. They COULD be spread around - it is up to you, but it is recommended they are consolidated onto one server. FSMO transfer guide here: http://support.microsoft.com/kb/324801 and you may like this one: http://www.petri.co.il/transferring_fsmo_roles.htm.
Note you can test if the current server has any FSMO roles by running (at a command prompt)
netdom query fsmo
and examining the output of server FQDNs.
If you see anything about SEIZING FSMO roles, DO NOT undertake this procedure, in this case you can TRANSFER the roles which is a less painful procedure.

For DNS, you should have all zones Active Directory integrated, which means the DNS information is stored in Active Directory and transferred with existing DC-to-DC replication. This eliminates the need for zone transfers. To convert to AD-integrated DNS (or ensure you have this configuration), check out http://support.microsoft.com/kb/198437.

For the Global Catalog role, you can ensure at least one other server is a GC by following http://support.microsoft.com/kb/313994. More information on the Global Catalog role (including why it is needed for user and computer logons) can be found at http://support.microsoft.com/kb/216970.

As a test, shut down the existing DC and make sure all Active Directory and client workstations are functioning properly. If they are, you should be safe to go ahead and run DCPROMO to demote the DC to member server.

Make sure then replicate any data and shares off the server if you intend on completely removing it from your network.

Note that DNS and DHCP can be installed using Server Manager.

I just want to specifically make the Exchange part of the procedure more clear. It IS a supported configuration to have Exchange on a DC - particularly in smaller environments with just 1 or 2 servers, it may not be feasible to have any other configuration. Before doing any of the transfer I've described above of Active Directory, you MUST uninstall Exchange completely. You can reinstall it after the DC role is moved across.
TJacoberger1Author Commented:
Thank You for the all the information, I appreciate it.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now