Before planning your Exchange Server 2013 migration, you need to ensure that you are familiar with all its features like virtualization, retention, modern public folders, managed availability, transport, unified messaging, EWS, Outlook Web App etc.<\/p>\n\n\n\n
As Exchange is critical to the communication network, it is important to do a smooth Exchange migration which causes minimum or zero interruption to the organizational communication. In this blog, we will see how to migrate all users and services from Exchange 2007 to Exchange 2013 and finally decommission the old Exchange 2007.<\/p>\n\n\n\n
Active Directory Preparation :<\/p>\n\n\n\n
When we install Exchange Server, it needs to store User mailboxes\u2019 \nand Exchange Server\u2019s configuration information in the organization. So \nit is important that Active Directory is duly prepared before you \ninstall Exchange 2013 in the organization. \n
Following things need to be done before you deploy Exchange Server 2013 in the environment : \n
A) Extend Active Directory Schema \n
B) Prepare Active Directory and \n
C) Prepare Active Directory Domains <\/p>\n\n\n\n
To ensure that AD preparation is done correctly, verify that the \nrangeUpper property on ms-Exch-Schema-Version-Pt is set to the correct \nvalue. After this force AD replication.<\/p>\n\n\n\n
Exchange Server 2013 Installation :\n
When you are ready for running Exchange Server setup, ensure that \nserver is fully updated with latest patches. To install Windows Features\n using PowerShell Run Windows PowerShell as Administrator and paste the \nfollowing command:<\/p>\n\n\n\n
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, \nNET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, \nRSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, \nRSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, \nWeb-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, \nWeb-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, \nWeb-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, \nWeb-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console,\n Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, \nWeb-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, \nWindows-Identity-Foundation<\/p>\n\n\n\n
After the installation is complete, Restart your server. And after \nthe reboot, download and install Microsoft Unified Communications \nManaged API 4.0. Core Run-time 64-bit, Microsoft Office 2010 Filter \nPacks 64 bit, Microsoft Office 2010 Filter Packs SP1 64 bit.<\/p>\n\n\n\n
You should be using as few certificates and host names as\n possible for cost control since certificate providers charge a fee \nbased on number of host names you add to your certificate. By default, \nExchange comes with self-signed certificates, we will replace this \ncertificates with the ones relevant to our case.<\/p>\n\n\n\n
mail.contoso.com : FQDN for most connections to Exchange including \nMicrosoft Outlook, Outlook Web App, Outlook Anywhere, the Offline \nAddress Book, Exchange Web Services, POP3, IMAP4, SMTP, Exchange Control\n Panel, and ActiveSync<\/p>\n\n\n\n
autodiscover.contoso.com : FQDN used by clients that support Auto \ndiscover, including Microsoft Office Outlook 2007 and later versions, \nExchange ActiveSync and Exchange Web Services clients<\/p>\n\n\n\n
legacy.contoso.com: FQDN used by all external and internal clients for old server i.e. Exchange Server 2007.<\/p>\n\n\n\n
Next, We will create certificate request, for this open EMS and run the New-ExchangeCertificate cmdlet command:\n
Once the certificate is created, get it signed by the appropriate \ncertification authority (CA) and use the Import-ExchangeCertificate to \nimport the certificate.<\/p>\n\n\n\n
Then Exchange Server 2013 need to be configured to use the certificates using the Enable-ExchangeCertificate command.<\/p>\n\n\n\n
Please note that Enable-ExchangeCertificate cmdlet cannot be used to \nenable a wildcard certificate for POP and IMAP services, also it cannot \nbe used to enable a certificate for federation.\n
Use private key to export the certificate and import it on Exchange 2007 CAS servers using the same steps.<\/p>\n\n\n\n
Follow the given steps to configure Exchange Server 2013 virtual directories using EMS :<\/p>\n\n\n\n
Exchange Control Panel\n
To configure Exchange Control Panel (ECP) virtual directories properties, use Set-EcpVirtualDirectory cmdlet.<\/p>\n\n\n\n
Outlook Web App\n
To configure Outlook Web App virtual directories use Set-OwaVirtualDirectory cmdlet.<\/p>\n\n\n\n
Offline Address Book\n
To configure offline address book virtual directory use Set-OABVirtualDirectory cmdlet.<\/p>\n\n\n\n
ActiveSync\n
Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft\n Exchange ActiveSync settings on specified virtual directory.<\/p>\n\n\n\n
Web Services\n
To modify Exchange Web Services virtual directory use \nSet-WebServicesVirtualDirectory cmdlet on the server running Exchange \nServer 2013.<\/p>\n\n\n\n
AutoDiscover\n
To set properties on specified Client Access Server objects use Set-ClientAccessServer cmdlet.<\/p>\n\n\n\n
Outlook Anywhere\n
To set properties on a computer running Microsoft Exchange Server \n2013 enabled for Microsoft Outlook Anywhere use Set-OutlookAnywhere \ncmdlet.<\/p>\n\n\n\n
In Exchange Server 2013, OABGen (Offline Address Book \nGeneration) service which runs on Mailbox server generates offline \naddress book.<\/p>\n\n\n\n
Change the default OAB on Exchange 2013 database using Get-MailboxDatabase and Set-MailboxDatabase<\/p>\n\n\n\n
Receive Connector\n
To create this connector use the New-ReceiveConnector cmdlet.<\/p>\n\n\n\n
Send Connector\n
Now add the new Exchange Server to the existing send connector by the Set-SendConnector cmdlet.<\/p>\n\n\n\n
Transport Rules:\n
Transport rules cannot be migrated from Exchange Server 2007 to \n2013. So you need to do the following to get Transport rules in Exchange\n Server 2013:<\/p>\n\n\n\n
Use Export-TransportRuleCollection cmdlet to export all transport rules from Exchange Server 2007\n
Copy the exported Transport Rule file to the system which has Exchange Server 2013 installed on it\n
Use Import-TransportRuleCollection cmdlet to import the Transport Rules from the file to the Exchange Server 2013<\/p>\n\n\n\n
In the Exchange 2007 management shell you need to run the following commands :<\/p>\n\n\n\n
Outlook Web App\n
Use Set-OwaVirtualDirectory cmdlet to modify properties of MS Outlook Web App virtual directories.<\/p>\n\n\n\n
Offline Address Book\n
Use Set-OABVirtualDirectory cmdlet to configure offline address book virtual directory.<\/p>\n\n\n\n
ActiveSync\n
Use Set-ActiveSyncVirtualDirectory cmdlet to configure the Microsoft\n Exchange ActiveSync settings on specified virtual directory.<\/p>\n\n\n\n
Web Services\n
To modify Exchange Web Services virtual directory use \nSet-WebServicesVirtual Directory cmdlet on the server running Exchange \nServer 2007.<\/p>\n\n\n\n
Unified Messaging\n
To modify an existing Exchange Unified Messaging virtual directory, run the Set-UMVirtualDirectory cmdlet.<\/p>\n\n\n\n
Outlook Anywhere\n
To set Microsoft Outlook Anywhere properties on Microsoft Exchange Server 2007 use Set-OutlookAnywhere cmdlet.<\/p>\n\n\n\n
Threat Management Gateway Rules\n
Now create and update your TMG publish rules.<\/p>\n\n\n\n
Next update your publish rules for Exchange 2007 to accept \nconnections for Legacy name space. And then publish Exchange Server 2013\n using TMG.<\/p>\n\n\n\n
Domain Name System Configurations:<\/p>\n\n\n\n
In the Internal DNS, point mail.contoso.com and \nautodiscover.contoso.com to Exchange 2013 server. And in \nLegacy.contoso.com new record points to Exchange 2007 Server. In the \nPublic DNS, point mail.contoso.com and autodiscover.contoso.com to TMG \nlistener and for Legacy.contoso.com point new record to TMG Listener.<\/p>\n\n\n\n
Next you can use New-MoveRequest cmdlet to start mailbox \nor personal archive migration. To check mailbox readiness before \nstarting to move mailboxes you can use WhatIf parameter. You can also \ncreate batch move if you want.<\/p>\n\n\n\n
To start with, take snapshot of the current Public Folders in Exchange Server 2007 EMS using the following commands: \n
Get-PublicFolder, Get-PublicFolderStatistics and Get-PublicFolderClientPermission.<\/p>\n\n\n\n
Next, Create CSV files using scripts \n(Export-PublicFolderStatistics.ps1 and \nPublicFolderToMailboxMapGenerator.ps1). In this way you will get the CSV\n file mapping PFs to new PF mailboxes.<\/p>\n\n\n\n
In the Exchange 2013, create PF mailboxes using New-Mailbox \n\u2013PublicFolder cmdlet. Migrate PF content using \nNew-PublicFolderMigrationRequest cmdlet.<\/p>\n\n\n\n
Before starting the final migration, lock down Exchange Server 2007 using the following cmdlets.<\/p>\n\n\n\n
Set-OrganizationConfig \u2013PublicFoldersLockedForMigration $True (In Exchange 2007)<\/p>\n\n\n\n
Set-PublicFolderMigrationRequest <name> -PreventCompletion $False (In Exchange 2013)<\/p>\n\n\n\n
Resume-PublicFolderMigrationRequest <name> (In Exchange 2013)<\/p>\n\n\n\n
Test new public folders to ensure everything is alright. Then us the following cmdlet to unlock the PF migration.<\/p>\n\n\n\n
Set-OrganizationConfig -PublicFolderMigrationComplete:$true<\/p>\n\n\n\n
Open Exchange Server 2007 management shell and run the following command to remove mailbox databases.<\/p>\n\n\n\n
Get-MailboxDatabase | Remove-MailboxDatabase<\/p>\n\n\n\n
Remove the public database and in the cmd run the following command to uninstall Exchange:<\/p>\n\n\n\n
Setup.com \/mode:uninstall<\/p>\n\n\n\n
The above mentioned steps helps you to complete the entire Exchange Server 2007 to 2013 migration process. <\/p>\n\n\n\n
If you have not moved public folder replicas to another server, \nor if you have not removed all of the public folders in the public \nfolder database, you will receive an error stating that the public \nfolder database cannot be removed because it contains public folder \nreplicas.<\/p>\n","protected":false},"excerpt":{"rendered":"
Before planning your Exchange Server 2013 migration, you need to ensure that you are familiar with all its features like virtualization, retention, modern public folders, managed availability, transport, unified messaging, EWS, Outlook Web App etc. As Exchange is critical to the communication network, it is important to do a smooth Exchange migration which causes minimum […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-688","post","type-post","status-publish","format-standard","hentry","category-exchange-server"],"yoast_head":"\n