Question Locked

Exchange Server 2007 Installation in a 32-bit environment

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I have a problem that I'm not sure how to solve. I work for a small non-profit who currently has three Windows Server 2003 servers all running 32-bit OS. We need to install Windows Exchange Server 2007 into this environment, so we need to upgrade at least one of these servers to 64-bit OS. One server runs as the primary domain controller and DNS, another server runs as a secondary domain controller, print server, and file server, the third server runs as an app server. It turns out the primary app on the app server cannot run in a 64-bit OS, so I cannot upgrade that one. The primary domain controller is a much more powerful server than the secondary controller, so I would prefer to use that hardware; however, I know it is not advised (or supported I believe) to run Exchange on your domain controller. My question is this: Can I promote my secondary domain controller to be the primary controller, rebuild the old primary domain controller to use 64-bit OS, put Exchange on it, and also make it a secondary domain controller? Is that a feasible and advisable configuration? Is there any other options that anyone can see that I could pursue. Thanks.

~Pat

4 replies

by kjell_andorsen

Here is what I would do.

Migrate all FMSO roles to the secondary DC, make sure all data migrates properly, and that the secondary DC is set up to hadnle all the primary server was set up to do (Global catalog, DNS etc). Then run DCpromo on the primary DC to demote it from a DC to a member server.

Check you environment to make sure everything is working with the remaining DC.

Rebuild the old DC with a 64-bit OS, and install Exchange 2007.

At this point I would not recommend promoting the Exchange server to a DC, this will most likely cause problems down the road. I would recommend getting a cheap new (or even used) server to act as a secondary DC.

In a small environment a DC doesn't need to run on particulalry beefy hardware so this should not be a huge cost. Depending on the power of the remaining hardware you might even be able to run a virtualized instance.

Getting the funding approved for another server can of course be tricky, but it really would be the best solution, and would likely cost you less in the long run than trying to add the DC role to the exchange server.

by dumphrey

you would be better off getting a new box to put this on. An exchange server can be hard on hardware, and mixed in with a DC, even a secondary one, can cause serious disk usage, ram usage, and processor usage. Also, having exchange on the same server as a DC seems risky to me...
by the time you purchase an OS, exchange 2007, licenses for 2007, a new box to put the OS on is a drop in the bucket.

All that being said, yes you can indeed do what you want to do. Make sure to move all FSMO roles onto the secondary DC, make sure its a global cataloge, and I would move dns there as well, even if only only temp, though the application server may be a better choice atm...
Exchange needs DNS up and running when it boots, having DNS on another server prevents having to fiddle with start up service times..
I would suggest at least 4 GB of ram for Exchange and maybe another 1GB for secondary DC usage.. so 5 to 6 GB total in the box. Also I would strongly recommend a second disk (or better raid array) for the Exchange database, separate from the OS/AD partition.

So, Primary DC gives up DNS to App server (move dns), and all FSMO roles to DC 2. Ensure dc2 has a global catalog. Demote DC1 with dcpromo. Rebuild machine, install 64 bit server. Install Exchange. Run dcpromo after Exchange is up and running (tested).
If you find being an Exchange server and DC is too much, its cheaper to build/buy a box to act as a second/back up DC then it is for an Exchange 2007 server.
EDIT: I just read Kjell's post. He said it much clearer then I did. I second his opinion.

by cg it

Their cheap enough that it's more cost effective to buy a new box than monkey around with FMSO roles, promoting, demoting, upgrading, and all the inherent problems that might arise and the time to fix all the problems that probably will arise, and that doesn't include those problems that probably will arise in the future because Exchange has to share resources, storage space, with a DC.

This discussion is closed to new replies.