Home > Exchange 2007 > Install Exchange 2007 on Windows 2008 Server, with Existing Windows 2003\Exchange 2003 Domain

Install Exchange 2007 on Windows 2008 Server, with Existing Windows 2003\Exchange 2003 Domain

I am running a Multi-Domain, Single Forest infrastructure.  The first domain in the Forest was Windows 2003.  The subsequent domain was Windows 2008.  I have Exchange 2003 installed on the Windows 2003 DC (Domain Controller).  I want to also note that Exchange 2003 was installed on the first domain before the second domain existed. 

My goal was to install Exchange 2007 on the Windows 2008 DC.  I ran into lots of issues.  Below is my recipe to perform an install with this type of setup.

Since my first DC was Windows 2003, that machine, by default became the Schema Master.  I had to change this FSMO role to the Windows 2008 DC before I could perform the "Setup /PrepareSchema" component.  However, this role is not easily changed with the native tools on a Domain Controller.  I had to register a DLL on the Windows 2003 server and then move the role.

I. Finding the Schema Master via Windows 2003 GUI

To find out who currently holds the Schema Master Role:

  1. Register the Schmmgmt.dll library by pressing Start > RUN and typing:

regsvr32 schmmgmt.dll

  1. Press OK. You should receive a success confirmation.

  2. From the Run command open an MMC Console by typing MMC.

  3. On the Console menu, press Add/Remove Snap-in.

  4. Press Add. Select Active Directory Schema.

  5. Press Add and press Close. Press OK.

  6. Click the Active Directory Schema icon. After it loads right-click it and press Operation Masters.image  image

  7. Change the role to the new 2008 server.

 

II. Prepare the Windows 2008 Domain for Exchange 2003

We must first perform an Exchange 2003 "Setup /DomainPrep" on the Windows 2008 Server using Exchange 2003 server installation files.  There are two reasons for this.  The first is the Windows 2008 domain needs to have permissions set for Exchange 2003 security groups since Exchange 2003 was installed before the inception of this domain.  Secondly, Exchange 2007 SP1 requires there be a Recipient Update Policy in place on the Exchange 2003 server for the Windows 2008 domain.  This is required during the Exchange 2007 SP1 setup and the Routing group you select.

Take note, since there are additional security models in Windows 2008 server, I copied the Exchange 2003 installation files over to the local drive.  You must then run a Command Window with elevated administrator rights. 

Such as "C:\E2K3RTM\Setup /DomainPrep".  You will need Domain Admin rights to perform this step.

You will get compatibility warnings, but select "Run Program" twice. 

clip_image002  clip_image002[4]

You must reboot the server.

You must then go to the Windows 2003\Exchange 2003 Server, launch Exchange System Manager –> Recipients –> Recipient Update Services and create a new Recipient Update Service for the new Domain.  Right click, Select "New", Browse to the new Domain, select the DC and click create.

clip_image002[6]

 

III. Prepare Active Directory for Exchange 2007

These are necessary steps to prepare Active Directory for Exchange 2007 SP1. Make sure that you run this commands from server that is in the same Active Directory Site as Schema Master DC.  In this case, the Windows 2008 server (DC). 

  1. Run setup /PrepareLegacyExchangePermissions (coexistence with Exchange 2003). Note: To successfully complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest.
  2. Run  setup /PrepareSchema (Note: You must not run this command in a forest in which you do not plan to run setup /PrepareAD. If you do, the forest will be configured incorrectly, and you will not be able to read some attributes on user objects.)
  3. Run setup /PrepareAD   (Note: If this is a new Exchange install, you will need to specify the name of the Org use: setup /PrepareAD /OrganizationName:MyOrg.com)
  4. Run setup /PrepareDomain to prepare local domain, run setup /PrepareDomain:domain.com to prepare specific domain, run setup /PrepareAllDomains to prepare all domains in forest.

PrepareAD
Setup.com /PrepareAD output.

After you run each command, you should wait for the changes to replicate across your Exchange Organization. It can take a while in large Active Directory site topology. You can always force replication via Active Directory Sites and Services.

IV. Prepare your Windows 2008 Server for Exchange 2007 SP1

There are a bunch of prerequisites which must be met as listed below:

  • .Net Framework v2.0 or 3.0
  • PowerShell RTM
  • MMC 3.0 (installed by default)
  • IIS 7 (Various components needed by different roles)

For now we are going to install an Exchange 2007 SP1 server in a new domain and new organization. We will install the CAS, HT and Mailbox roles on a single, stand-alone machine. In order to install the prerequisites we will run the following commands one after the other at a command prompt: 

******Note, these must be run from the PowerShell Command window with elevated administrator rights!!******

ServerManagerCmd -i RSAT-ADDS

ServerManagerCmd -i PowerShell

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Digest-Auth

ServerManagerCmd -i Web-Windows-Auth

ServerManagerCmd -i Web-Dyn-Compression

 

V. Install Exchange 2007 SP1

You can now run the Exchange 2007 SP1 setup.

clip_image002[8]

image

Advertisements
Categories: Exchange 2007
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: