In this article I describe the migration from Exchange Server 2010 to Exchange Server 2013. I have created the following test environment for the migration:
Test environment
DC01 is a Windows Server 2012 Domain Controller that provides the Active Directory forest "frankysweb.local". Exchange 2010 SP3 on Server 2008 R2 is installed on Server EX2010. Service Pack 3 for Exchange 201 is a prerequisite for the migration. Server EX2013 is a member server of the "frankysweb.local" domain. The operating system is Windows Server 2012. CLT01 is a Windows 8 client with Outlook 2013 installed, it is only used for testing.
Installation Exchange 2013
Before Exchange 2013 can be installed, the prerequisites for Exchange 2013 must be created. In addition to Exchange 2013, there are other components that need to be downloaded first:
Microsoft Exchange Server 2013 CU1
Microsoft Unified Communications Managed API 4.0, Core Runtime 64-Bit
Microsoft Office 2010 Filter Pack (64 Bit)
Microsoft Office 2010 Filter Pack SP1 (64 Bit)
The time until the downloads are completed can be bridged by installing the operating system requirements, and the required roles/features can be added via Powershell:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Server-Media-Foundation, RSAT-ADDS
After restarting the server, the FilterPack, Service Pack and UCMA Runtime can be installed.
Once the prerequisites have been installed, the Exchange installation can be started. When you call up Setup, you will be asked whether new updates should be downloaded; at the moment there are none. If you like, you can skip this step.
A few files are copied...
As soon as the data has been copied, you are ready to go
Agree to license agreement
Here, everyone must decide for themselves whether to send data to Microsoft
I am installing a single server environment, so both Exchange 2013 roles on one server
Select path
Here comes an important point, if you install an Exchange-compatible virus scanner solution later, you should deactivate the built-in function here, but currently the market is still clear, so I leave the function switched on
This is followed by an analysis of the prerequisites. Normally, only a warning is displayed that the setup will extend the Active Directory schema. After clicking on "Install", the schema is updated and Exchange is installed
After a while the setup has run through
The Exchange Shell on the new server should now display both Exchange servers
So far so good, let's get started with the configuration.
Exchange 2013 configuration
As long as there is no admin mailbox on the Exchange 2013 server, you end up on the ECP of the Exchange 2010 server when you call up the ECP of the Exchange 2013 server. Exchange 2013 therefore performs a redirect and automatically searches for the responsible server.
If the administrator mailbox (or the mailbox of an Exchange administrator) is not moved, you will end up in the ECP of the Exchange 2010 server:
EDIT: It is not absolutely necessary to create a new user, you can also access the ECP of the Exchange 2013 server under the following link:
Since I only want to move the mailboxes at the end, I first create the user "ExAdmin" and add it to the "Organization Management" group
To make things a little easier, I rename the database created during installation on the EX2013
Get-MailboxDatabase | Set-MailboxDatabase -Name MBDB02
Then I create a mailbox for the user "EXADMIN" in the new database MBDB02
Enable-Mailbox exadmin -Database MBDB02
Now I can log on to the Exchange 2013 ECP with the user "Exadmin":
Now the actual configuration can begin. So that Exchange 2013 can also send mails directly and does not have to be routed via the Exchange 2010 server, Sever EX2013 is added to the send conector as the source server:
My send connector is called "To Internet", here EX2013 is added as the source server
Next, I configure the certificates for Exchange 2013. How this works, I have already described hereso I'll spare you that part at this point:
Exchange 2013: SAN certificate and internal certification authority (CA)
If you use public folders and also want to migrate them, you must create a public mailbox. Public folder databases as in previous Exchange versions no longer exist in Exchange 2013. Instead, there are now public mailboxes. There are currently no public folders in my test environment, but the migration is described very clearly in the Technet:
http://technet.microsoft.com/de-de/library/jj150486(v=exchg.150).aspx
This essentially completes the configuration, so I can move on to the migration.
Migration
The migration of mailboxes can be carried out conveniently via the EXP. To do this, go to "Recipients" and the "Migration" tab, then click on the plus sign
In the wizard, I can simply select the mailboxes that I want to move to the new Exchange 2013 database
The target database is specified in the next dialog:
Then just click on "New" and you're ready to go
If the mailboxes have been successfully moved, they have the status "Finalized"
EDIT: The EXADMIN user also receives an e-mail informing them of the status of the batch
All user mailboxes are migrated in the same way, including the system mailboxes (although I'm still not quite sure whether you actually need them, but better safe than sorry)
The second batch with the system mailboxes is also complete and all mailboxes now have the status "Finalized" and are located in the Exchange 2013 database MBDB02
Now I delete the batches, they are no longer needed
A query as to whether there are still mailboxes in the Exchange 2010 database MBDB01 no longer returns any results
Get-MailboxDatabase MBDB01 | Get-Mailbox
Get-MailboxDatabase MBDB01 | Get-Mailbox -Arbitration
So now I can take the Exchange 2010 database offline and remove it
Dismount database MBDB01
Remove-MailboxDatabase MBDB01
There are now no more databases on the Exchange 2010 server
Next, I remove the Exchange 2010 server as the source server for the SendConnector "To Internet"
Then I delete the old offline address book, but I'm still not quite sure whether this is necessary...
Once the steps have been completed, it is time to uninstall Exchange 2010. Wistfulness spreads.
Uninstall Exchange 2010
After checking the message flow and the connection to the mailboxes, I can uninstall Exchange 2010. As mentioned above, this is the beta version of the article, I haven't noticed any problems so far, but that doesn't mean that they can't still occur, the connection via OWA, Active Sync and Outlook was possible without any problems, that's enough for now until I've tested other things.
Exchange 2010 can be uninstalled under Programs and Features
The wizard starts
Deselect all server roles and deselect the administration console
The check reports no errors, you are ready to go
The uninstallation is running, everything is fine
After a short time Exchange 2010 is completely uninstalled... R.I.P.
If Exchange has been uninstalled, the server can be removed from the domain and shut down permanently. Outlook connects to the new Exchange 2013 server.