Skip to content

Migrating and removing Exchange 2007 to Exchange 2010


This migration process is not mysterious nor with degree of difficulty "mission impossible". Starting yesterday afternoon and finally today at dawn we did two migration with Exchange 2007 environments to Exchange 2010.

The process is the same as migrating from Exchange 2003 to Exchange 2007, side-by-side. Creates a new server that automatically will participate in the same organization, move mailboxes and change the server responsible for OAB.

For those who don’t know the process Exchange 2003 to Exchange 2007, see the videos of the series migration (portuguese).

However, Exchange 2010 will give a surprise in Exchange 2007 who comes at some point and is about these which I’ll address, after staying until 5: 30 in the morning in more a migration "pounding head".

Blocking attachments in OWA (easy)

OWA will bar attached files of any type if not implemented Setup ON EACH SERVER CAS. The first screen below shows the configuration that must be activated and the second the list of blocked files/permitdios:



Run Exchange 2010 in Outlook 2003 (easy)

Exchange 2010 requires RPC traffic is encrypted, so it is necessary to change the user profile for Outlook 2003 to use encryption in the communication. You can see this by using the cmdlet Get-RpcClientAccess | fl and verifying the attribute "Encryption Required" must be "true".

Just go in Outlook, edit the profile and select "Encrypt data between Outlook and Microsoft Exchange" which is in the tab "Security" of Outlook 2003.

Change server of send email (easy)

When create “Send Connectors” (Organization –> Hub Transport) Exchange attach this task a active server.

Open all send conector, add new server and remove old server.

Changing the generator of the Offline Address List OAB (Easy)

Only a server generates a list that is downloaded to the cache of Office Outlook and OWA. Change it to the new server:


Besides, if your organization does not use more versions of Office before 2003, you can change the mode of distribution of OAB, as below. Important steps forward in one of them will remove the public folders and distribution of the OAB it can become inconsistent.


Remove the Mailbox Default installation (medium)

When you install Exchange 2010 it creates a mailbox with an identifier value numerico randomico where it hosts the mailboxes of the system calls the "arbitrary". To remove this mailbox first must move the mailboxes to another database systems with the cmdlet below:

Remover Mailbox Default

The first one Get-Mailbox-Database <nome> – Abitration will lists the mailboxes and the second – Get-Mailbox-Database <Nome> | Arbitration New-MoveRequest-TargetDatabase < name new MB > performs the list and sends to the move pipe.

Remove the Public Folder server before (Hard)

You need to remove the contents of public folders. If you have public folders created by users or additional first you need to make the replica to the new server, expect to replicate the reply and remove the original server. This can be done by the tool "Public Folder Management" which is in the console of the Exchange Tools.

To move all public folder system, you should run the script that is in the MoveAllReplicas.ps1 scripts installation of Exchange Server, passing as parameters –Server <actual> -NewServer <new>. Yet another step is necessary to go into each mailbox and on the "Client Settings" change the public folder that is used as standard in each of the databases.

If after these steps you still can not remove the Mailbox role will need to make an outline documented that involves opening ADSIEDIT.msc and follow the path:

Configuration -> Configuration -> Services -> Microsoft Exchange -> Organization-> Administrative Groups -> Administrative Group -> Servers -> Server 2007 -> InformationStore -> desired Storage Group

On the right of the screen will list the arrays stored in that group. Delete the public folder manually.

NOTE: It is highly recommended to backup the AD before running ADSIEDIT

Adjust the ISA or TMG rules for ECP-Control Panel Exchange 2010 (hard)

In the rules of OWA ISA 2004, Forefront TMG or ISA Server 2006 for Exchange 2003 and Exchange 2007 there was only one virtual directory to be published, OWA. Now in Exchange 2010 there is also the ECP virtual directory.

To adjust the publishing rule to open its properties and change Paths tab as the image below including the ECP virtual directory as prefix:


Adjust the IIS to access the ECP and OWA (hard)

Even at this point there is the problem that the ECP not between because the authentication mode in IIS. To adjust this add on installation of Web Server in Roles Windows feature anonymous authentication and the IIS virtual directory add this type of authentication, as well as the Basic and Windows:


This change is made in the ECP virtual directory, but if you have problems accessing OWA after migration disable Forms mode and enable Basic modes and Windows on the OWA virtual directory.


These tips have helped me to achieve the migration process already some time, but share the experiences is always important. If you also have some additional point in the process of migrating Exchange 2007 to Exchange 2010, send in comments and I’ll add in this post.

From → Exchange

One Comment
  1. Eu realmente adoro este blog, que me impede de ficar entediado no trabalho. Continuem o bom trabalho: P

Leave a Reply

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

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

Google photo

You are commenting using your Google 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 )

Connecting to %s

%d bloggers like this: