Install Exchange 2010

Exchange Server 2010 can be installed on either Windows Server 2008 64-bit with Service Pack 2, or Windows Server 2008 64-bit R2, and either Standard or Enterprise editions.

System Requirements

First, you need to make sure that your Active Directory (AD) environment and your Exchange server meet the minimum requirements:

Prerequisites

We are going to install Exchange 2010 on a Windows Server 2008 R2 operating system. Before installing Exchange we need to install some Windows components. It's important that you don't miss anything here because the Exchange 2010 installer does not provide very good feedback if Server 2008 R2 is missing required components.

  1. Net Framework 3.5 & and updates
  2. Powershell 2.0
  3. Windows Remote Management
  4. System Converter: Microsoft Filter Pack (for Hub Transport and Mailbox Server roles only)

Note: There is a PowerShell script that automates the process of installing the prerequisites. This script makes things much easier Exchange2010Prereqs.ps1

 

Suppress Link State Updates
This explains how to use Registry Editor to suppress propagation of minor link state updates between routing groups in Microsoft Exchange Server 2010 and Exchange Server 2003.
To perform this procedure, you must log on to the Exchange 2003 server by using an account that is delegated membership in the local Administrators group.

  1. Open Registry Editor.
  2. Locate HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters.
  3. Right-click Parameters and select New | DWORD value. Name the new DWORD value SuppressStateChanges.
  4. Double-click SuppressStateChanges.
  5. In the Value data field, enter 1.
  6. Close Registry Editor, and then restart the SMTP service, the Microsoft Exchange Routing Engine service, and the Microsoft Exchange MTA Stacks services for the change to take effect.

PREPARE LEGACY EXCHANGE PERMISSIONS

The installation process requires Active Directory to be prepared. The GUI is should do all the AD upgrades during install, but we'll run these commands in the shell. When migrating from Exchange 2003 to 2010, we transition the Exchange specific permissions. Exchange Server 2010 uses E-Mail Address Policies instead of Exchange Server’s 2003 Recipient Update Service. By running this command, you prepare the Active Directory for the coexistence of both. You must be logged in as member of the Enterprise Admins group.
setup /PrepareLegacyExchangePermissions or setup /pl

The Active Directory schema must be extended with Exchange 2010 specific attributes. This command will create a connection to the schema master and update the schema with attributes specific to Exchange 2010. You must run as a member of the Enterprise Admins and as a member of the Schema Admins group and Run this on a computer that is in the same domain and the same Active Directory site as the schema master.
setup /PrepareSchema or setup /ps

This command prepares the local Active Directory for Exchange 2010, for example it creates a new OU called “Microsoft Exchange Security Groups”. In this container you’ll find a few default security groups that are quite handy for the administration of Exchange Server 2010. Be a member of the Enterprise Admins group to successfully perform this.
setup /PrepareAD or setup /p

The last command prepares domains other than the domain where your Schema Master is located.
setup /PrepareDomain or setup /pd ( setup /PrepareDomain:child.FQDN.com )
For multiple domains use the /preparealldomains switch.

This also performs multiple tasks. It creates a new domain global group named Exchange Install Domain Servers in the current domain. Next it adds this group to the Microsoft Exchange System Objects container and to the Exchange Servers group at the root domain.

Note: if you have mail enabled users in child domains, be sure to run:
setup /PrepareDomain:child.domain.com for the child domain, or use /PrepareAllDomains switch.

Exchange 2010 Installation

Now we're ready to run the Exchange 2010 installer. We'll go through a typical installation that includes the Client Access, Hub Transport, and Mailbox roles. This is what you will want to install if you are only going to be running one Exchange server. If you scale out your Exchange architecture with multiple servers then you will want to familiarize yourself with the Exchange server roles for a proper deployment.

  1. Logon to the desktop of your soon to be Exchange server with a Domain Admin account.
  2. Run setup from the Exchange 2010 media.
  3. Click on "Step 3: Choose Exchange language option" and choose one of the options (Install only languages from the DVD will be fine in most cases).
  4. Click on "Step 4: Install Microsoft Exchange."
  5. Click Next at the Introduction page.
  6. Accept the license terms and click Next.
  7. Make a selection on the Error Reporting page and click Next.
  8. Stick with the default "Typical Exchange Server Installation". If you want to change the path for the Exchange 2010 installation, click Browse, locate the appropriate folder in the folder tree, and then click OK. Click Next.
  9. Make a selection on the Client Settings page and click Next.
    If you want your Exchange server to be available externally then choose a domain name such as owa.mydomain.com, click Next.
  10. Select your Exchange 2003 in the Mail Flow Settings. This will create a routing group connector, click Next.
  11. Make a selection on the Customer Experience Improvement Program page and click Next.
  12. If all the prerequisites are there, then you can click Install.
  13. When the installation has finished go back to the Exchange installation page click on "Step 5: Get critical updates for Microsoft Exchange."
  14. Install Microsoft Update (if necessary) so that Windows update will check for non-OS updates, and verify that there are no Exchange updates.
  15. Enter the Setup Key for Exchange, in EMC under Server Configuration.

 

Mailbox Server Role Coexistence

At the Exchange 2010 Management Console, mailboxes located on Exchange 2003 Servers are classified as "Legacy Mailbox".

The process of moving mailboxes to Exchange 2010 is called Local Move Request (local is for moving within the same forest). When moving from Exchange 2003, the user is disconnected during the move process. Unfortunately, online mailbox moves are only possible if the source mailbox is located on Exchange 2007/2010.

Mailbox move requests can be performed using both Exchange Management Console and Exchange Management Shell. For example:

New-MoveRequest -Identity domain\neil -BadItemLimit 50 
-DomainController 'dc.child.domain.com'
-TargetDatabase 'BI Mailbox Database'

Once the mailboxes are moved, we should proceed with moving public folders. To discover public folder replicas, at the shell run the following:

Get-PublicFolder -recurse | FL Name,Replicas

The next step is to open the Exchange 2003 System Manager and to locate the Public Folder store database. Here right-click the database and choose Move All Replicas. When prompted to choose for a destination public folder database, select the one located on Exchange 2010.

The process can be monitored using the same Exchange Management Shell command:
Get-PublicFolder -recurse | FL Name,Replicas

The Exchange 2003 Recipient Update Service should also be reconfigured to use Exchange 2010 Servers. This is done from the Exchange System Manager.

At the end, mailboxes and public folder databases on Exchange 2003 servers should be deleted using the Exchange System Manager. This process does not delete the database files from the file system, so file deletion should be done manually.

When all resources are moved to the Exchange 2010 Servers, the routing group connectors between the Exchange 2003 and 2010 routing groups should be deleted using the Exchange 2003 System Manager.

Finally Exchange 2003 can be removed from Control Panel | Add Remove Programs on Windows 2003.

Post Installation Steps

Now that you have Exchange 2010 installed, you will need to do some basic configuration in the Exchange Management console to get mail flowing to/from your server.

  1. Open the Exchange Management Console via Start >> All Programs >> Microsoft Exchange Server 2010 >> Exchange Management Console
  2. Expand Microsoft Exchange On-Premises so you can see: Organization Configuration, Server Configuration, Recipient Configuration, and Toolbox
  3. Under Organization Configuration >> Hub Transport >> Accepted Domains add a new Accepted Domain for the domain you wish to use for email addresses. For example, your AD domain will be listed by default (i.e. ad.myorganization.com). You will probably want to add "myorganization.com" as an Authoritative Domain.
  4. Under Organization Configuration > Hub Transport > Send Connectors > New Send Connector>
    Pick a name such as "Internet Send Connector", change the drop down to "Custom"> Next > Add Address Space. Enter "*" in the Address field and check the box to include all subdomains > OK > Next.
    Now, if you want your Exchange server to route mail directly, then click Next on the Network setting page, but if you want to route your email through an upstream provider then select "Route mail through the following smart hosts" and Add ... a mail gateway such as smtp.comcast.net.
    Click Next > Next > Next > New.
  5. Under Server Configuration >> Hub Transport >> Right-click Default *** >> Properties >> Permission Groups tab, check the box for Anonymous users. This will allow your Exchange server to accept incoming mail delivery from remote mail servers.
  6. The old Exchange server relies on the recipient update service, the new server does not. You need to issue some powershell commands to fix it. Start Exchange Management Shell.
    Issue the following command:
  7. Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq "Legacy"} | 
     Set-EmailAddressPolicy –IncludedRecipients AllRecipient
    Once executed, you need to press "Y" to accept.

  8. At this point locate the directories that hold your new Exchange databases and logs, and MAKE SURE that these folders have been excluded from your normal AV scanning. AV has a habit of quarantining Exchange log files and breaking the database - this is easy to fix when the stores won't mount but it's not good!
  9. Under Recipient Configuration >> Mailbox, create mailboxes for your existing AD users (or create a new user & mailbox)
    1. New Mailbox ... >> select User Mailbox >> Next >> Existing users >> Add ... >> select an existing AD account >> OK >> Next >> specify an alias (e.g. the AD user name) >> Next >> New
  10. If you want to use an SSL certificate for Outlook Web App, IMAP, POP, etc. click on Server Configuration and import or create the certificate

Conclusion

That's it! You should now be able to browse to https://mail.myorganization.com/owa (or https://localhost/owa from the server) and logon via the Web interface to send and receive mail!

Note: client's (outlook 2003) will need to change the Security settings to: Encrypt data between Outlook and Exchange.