Exchange server 2010 and Domain Controller

I am trying to prepare for some serve upgrades in a month or so. Currently I am running exchange server 2010 on a Windows 2003 R2 server. When exchange was initially installed the computer was a Domain controller.  I am looking at upgrading a couple servers to Windows 2008 R2. Because I wanted to upgrade Active Directory to 2008. I was thinking of moving the Domain Controller off the Exchange server. Before I upgrade the system I have 4 other Domain Controllers, Running windows 2003. How do make my exchange server a member server?
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Hypercat (Deb)Connect With a Mentor Commented:
It's OK to leave it the way it is, but the usual concern is that Exchange automatically grabs a whole boatload of memory and that can be a problem on a server that is also a DC. It depends on the size of your domain, number of and size of your mailbox store(s), number of mailboxes, etc.  For example, Microsoft itself has the SBS product which runs both the DC and Exchange on the same box, with the assumption that you have a small number of mailboxes (i.e., 20-30 or fewer).

If you have plenty of other DC resources in your domain, and if you also have a larger number of mailboxes, I would recommend moving to a member server (migrating the mailboxes, as I mentioned above). Then you could uninstall Exchange from the DC and that DC would function better, or you could repurpose that DC in some other way, making it a file server, print server, etc.
I am having a hard time understanding the question. Could you explain a little more what you mean by "How do I make my exchange server a member server?"
AmitIT ArchitectCommented:
It seems you have Exchange and DC on same server? Now you are planning to split and DC and Exchange to different server...If so...first install new server as Additional DC and move the FSMO role to that server. Then create a new server for Exchange 2010. Move the mailboxes to new server and later remove Exchange and DC from the current server....correct me if i understood it wrongly
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Hypercat (Deb)Commented:
This would require a complete uninstall of Exchange on the existing server, running dcpromo to change the server from a DC to a member server, and then reinstalling Exchange.  Once you have Exchange installed on a DC, you will break Exchange if you run dcpromo to remove Active Directory from it.  The only alternative would be to get a new server (or existing member server), install Exchange on it and migrate your mailboxes.
jerryanvAuthor Commented:
You have got it right, would it be worth the trouble to place exchange on a different server and get it off the DC, everything is running fine now, or am I a time bomb waiting to happen. I've been running this way for 2 years.
AmitConnect With a Mentor IT ArchitectCommented:
DC is the backbone for your env. Say in current situation, if due to Exchange your DC is also down. Then other application or user login will be affected. It is always recommended to keep DC alone and you should have more the one DC for each site. This will provide the fault tolerance, in case one DC is down other can take over.

Hope this clears your doubt
jerryanvAuthor Commented:
Thank everyone for there input
All Courses

From novice to tech pro — start learning today.