Exchange SMTP connectors

Exchange 2007/2010 to 2010 migration  =  Don’t need to create new SMTP connector in Exchange 2010 – Just add Exchange 2010 as source server and after migration remove old server as source.


Exchange 2003 to 2010 migration = Need to create new SMTP connector on Exchange 2010 server.


You will receive the below error when you try to the add the new Exchange 2010 server to the SMTP connector that already exists in Exchange 2003 (In Exchange 2010 EMC). Exchange 2010 doesn’t recognize the 2003 SMTP connector so a new connector has to be created.

Running out of space during Mailbox Move Exchange 2010

A lot of times when you are busy doing a mailbox move you will see that the transaction logs can actually grow just as big as the size of the Database. So what can happen is you can run out of space on your database drive and the mailbox move will stop.

To work around this issue you can temporarily enable Circular Logging that will keep deleting the transaction logs while the mailbox move in progress.

To achieve this do the following:

1. Open Exchange Management Console – Go to Organisation – Mailbox

2. Select the Mailbox Database you are performing the move on. Right click – Properties

3. Enable Circular Logging

4. Restart the information Store Service for changes to take affect. (Please note this will temporarily disconnect your users)

After this please be sure to enable it as the Transaction logs assist in recovery situations.


Get Mailbox Sizes Exchange 2010 powershell.

I always struggle to find a straight forward command for getting Mailbox sizes in Exchange 2010. Although there is a lot of information out there, they all seem to over complicate things and don’t just give you what you require.

This is all you need:

Get-MailboxStatistics -Database “Mailbox Database*” | Select DisplayName, ItemCount, TotalItemSize | Sort-Object TotalItemSize -Descending | Export-CSV C:\MailBoxSizes.csv

This command will get the mailboxes sizes for all Databases beginning with Mailbox Database, Sort them according to size and export to a csv file.

Export mailboxes to PST – Exchange 2007

Below are the steps for exporting all mailboxes to PST’s.

You can’t run the export from a 64bit OS.

Below describes the steps:

1. Find a server/PC with a 32bit OS.

2. Install the Exchange Management Tools (Exchange 2007 SP1 or later) – You can install this from the Exchange Media.

3. Install Outlook 2003 (SP2 or later).

4. From the Exchange Management Shell run the following command:

get-mailbox -server “Your server name” | export-mailbox -PSTfolderPath “Folder Path”

This will export all mailboxes to PST’s. It won’t remove any data from the mailboxes, it will just make a copy to the PST’s.

If if re-run the export it will merge the mails into the PST’s.

One problem I came across while trying to do the export was an error due to insufficient access rights on the mailboxes. Below is the error I received:

Error was found for ‘User’ because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an inspecified service provider.

To resolve this run the following command:

Get-Mailbox -Server “Server name” | Add-MailboxPermission -user “User with which you run the Export command” -AccessRights FullAccess





Exchange server not routing mail to another Exchange server

When you have two exchange servers and they are not routing mail correctly to one another, check the receive connector – If the other Exchange servers IP fall in the range that is specified in the custom internal relay connector with different permissions. Then the Exchange servers won’t be able to route from one to another.

Also note the following:

After we followed the Exchange deployment kit for 2007 – 2010 migration – We could not send mails from mailboxes that were moved to the new exchange 2010 server – You need to add the new server to the ‘source’ server tab on the new servers send connector.

Public Folders not Replicating Exchange 2007 to Exchange 2010

During your migration from Exchange 2007 to Exchange 2010 you have followed our guide to replicate your Public Folders but when checking the Folder are still not replicating.

One of the reasons that can cause this is when the 2007 server was originally migrated from Exchange 2003 and an empty “Servers” containers was originally left in the old First Administrative Group.

To resolve the issue please follow the following steps:

1. Connect to one of your Domain Controllers

2. Open Adsiedit

3. Expand the Configurations container and go to: CN=Services, CN=Microsoft Exchange, CN=”Your Organisation”, CN=Administrative Groups, CN=First Administrative Group, CN=Servers


4. Check to see if the Servers container is empty. If its empty delete the container.

5. Give it some time and use the following command to see if Public Folder replication has started.

Get-PublicFolderStatistics -Server Exchange 2010

6. When this is done you can complete the Public Folder migration using this guide.

Public Folder replication Exchange 2007 to 2010

When migrating from Exchange 2007 to 2010 and you have moved all the mailboxes across. Now comes the time to move the Public Folders. Below is a set by step guide with the required Powershell commands to move your Public Folders.

1. Add new Exchange 2010 server to the Personal Public Folder replica set:

.\AddReplicaToPFRecursive.ps1 -server Exchange2007 -TopPublicFolder “\” -Servertoadd Exchange2010

2. Add new Exchange 2010 server to the System Public Folder Replica set:

.\AddReplicatoPFRecursive.ps1 -TopPublicFolder “\Non_IPM_Subtree” Servertoadd Exchange2010

3. Manually Start the replication process.

Update-PublicFolderHierarchy -Server Exchange2010

4. Monitor the replication status

Replication can days to happen so do it as early as possible. Run the below commands on new and old server to compare the amount of Public Folders and items to know when all Public Folder items have replicated.

Old Server:

Get-PublicFolderStatistics -Server Exchange 2007

New Server:

Get-PublicFolderStatistics -Server Exchange 2010

5. When the Replication has completed we need to remove the old server from the Replica set.

.\RemoveReplicaFromPfrecursive.ps1 -server Exchange2010 -TopPublicFolder “\” -ServerToRemove Exchange2007

.\RemoveReplicaFromPfrecursive.ps1 -server Exchange2010 -TopPublicFolder “\Non_IPM_Subtree” -ServerToRemove Exchange2007

6. Once this is completed go the the Exchange 2007 server – EMC – Server Configuration – Mailbox. On the properties of your Mailbox Database under client settings change the Default Public Folder Database to the one residing on the Exchange 2010 server.

7. To uninstall Exchange you will need to delete the old Public Folder Database. Log onto the EMS of your Exchange 2010 server and run the following command:

Remove-PublicFolderDatabase -Identity “Old Public Folder Database”




Slow Mailbox move Exchange 2003 to 2010

You’ve completed the initial part of the Exchange 2010 migration and have now come to the point were you need to start moving mailboxes. You start to move the mailboxes but they seem to be taking ages to move. If you look under your move request tab you will see that only 2 mailboxes are moving at a time. I think the reason Microsoft limits this to 2 is because Exchange was configured so you can move the mailboxes during business hours with hardly any interference to the users.

Like most of us thou we move mailboxes outside of office hours so we would like to speed up the process.

Below is the steps to increase how many simultaneous mailboxes can move at any one time.

1.  Edit the following file: C:\Program Files\Microsoft\Exchange Server\V14\Bin\MsExchangeMailboxReplication.exe.xml using Notepad.

2. Increase the “MaxActiveMovesPerSourceMDB” from 2 to your desired number. I have found 5 to be a good starting point. Make sure you do this under MRSConfiguration section not the section above it.

3. Restart the Microsoft Exchange Replication Service and restart the Mailbox Move.

This should resolve the slow move. I have found that this makes a massive difference from taking 2 days to move a certain amount of mailbox to only 8 hours.