chris goosen infrastructure consultant kloud solutions
TRANSCRIPT
Exchange 2013 Hybrid Deployments - Migrating on your terms….Chris GoosenInfrastructure ConsultantKloud Solutions
EXL334
Migration Planning Process
Plan Prepare Migrate
Why, What, How
Migration Strategy
Solution Design
Pilot Deployment
Comms. plan
Setup Tenant
Implement DirSync*
Establish Coexistence*
Assign licenses
Comms. to end-users
Migrate Data
Update DNS records
Migration OptionsIMAP migration
Supports wide range of email platformsEmail only (no calendar, contacts, or tasks)
Cutover Exchange migration Good for fast, cutover migrationsNo Exchange upgrade required on-premises
Staged Exchange migrationNo Exchange upgrade required on-premisesIdentity federation with on-premises directory
Hybrid deploymentManage users on-premises and onlineEnables cross-premises calendaring, smooth migration, easy off-boarding
IMAPCutover
Staged Hybrid
Exchange 5.5 X
Exchange 2000
X
Exchange 2003
X X X X*
Exchange 2007
X X X X
Exchange 2010
X X X
Exchange 2013
X X X
Notes/Domino X*
GroupWise X*
Other X
* Additional options available with tools from migration partners
Cutover Migrations
On-premises Exchange org (Exchange 2003+)
Office 365
Provisioned via Outlook Anywhere
Mailbox data via Outlook Anywhere
Staged Migrations
On-premises Exchange org (Exchange 2003, 2007)
Office 365
Provisioned via DirSync
Mailbox data via Outlook Anywhere
Cutover vs. Staged MigrationsCutover is all at once limited to 1000 users
Staged is a few users at a time.
Staged requires DirSync
Both use the Outlook Anywhere protocol to copy data
Both work for Exchange 2003/2007 deployments
Both require a new Outlook profile – OST/OAB Download
Hybrid Deployment
On-premises Exchange org (Exchange 2007+)
Exchange 2013
CAS & MBX Office 365
Provisioned via DirSync
Secure Mail flow
Mailbox data via Mailbox Replication Service (MRS)
Exchange Federation (Free/Busy, Mail Tips, Archive, etc.)
Hybrid DeploymentExchange federation enabled rich coexistence
Leverages the Mailbox Replication Service (MRS)
Secure mail flow
Integrated admin experience
Supports Exchange 2007+
Which Migration Option?
Cutover
Staged
Hybrid
Small Medium Large
<1 Week 2 Weeks 3 Weeks Several Months
None Mailflow/GALSync Rich Coexistence
Org. Size
Time
Features
ToolsExchange Deployment Assistant: http://aka.ms/exdeploy
Onramp: http://onramp.office365.com
IdFix: http://cgoo.se/idfix
Exchange Remote Connectivity Analyzer: http://www.testexchangeconnectivity.com
What’s new?Streamlined wizard & reduction of configuration tools
Enhanced secure mail
Improved centralised mail transport
Integrated Edge Transport server support
Improved support for Exchange Online Protection
Improved status and logging information
Unified mailbox move wizard
PrerequisitesOn-premises Exchange – Must be ≥ Exchange 2007
Office 365 tenant – Must be at ≥ 15.0.620.28
Custom domains should be registered in Office 365 tenant
Directory Synchronisation is required
Autodiscover should be correctly configured
Certificates – SAN certificate issued by a trusted public CA
If using EdgeSync, configure it prior to using HCW
Confirm Office 365 Tenant VersionGet-OrganizationConfig | Format-List AdminDisplayVersion,IsUpgradingOrganization
AdminDisplayVersion ≥ 15.0.620.28
IsUpgradingOrganization = False
Hybrid Deployment CompatibilityOn-premises Exchange environment
Exchange 2010-based hybrid with v14 tenant
Exchange 2010-based hybrid with v15 tenant
Exchange 2013-based hybrid with v15 tenant
Exchange 2013 (CU1) Not Supported Not applicable Supported
Exchange 2010 SP3 Supported Supported Supported
Exchange 2010 SP2 Supported Not supported Not supported
Exchange 2010 SP1 Supported Not supported Not supported
Exchange 2007 SP3 RU10
Supported Supported Supported
Exchange 2007 SP3 Supported Not supported Not supported
Exchange 2003 SP2 Supported Supported Not supported
Hybrid Deployment StepsClients Office 365
autodiscover.contoso.com
mail.contoso.com
E2010 or 2007 Hub
E2010 or 2007 CAS
E2010 or 2007 MBX
E2013 CAS
E2013 MBX
E2010 EDGE
Exchange 2010 or 2007 Servers
Non internet-facing site
SP/RU SP/RU
Internet-facing site
1. PrepareInstall Exchange SP and updates across the OrgPrepare AD with Exchange 2013 schema
2. Deploy Exchange 2013 serversInstall both Exchange 2013 MBX and CAS serversInstall Exchange 2010 Edge servers (if required)Set an EWS ExternalUrl & enable MRSProxy
3. Obtain and Deploy CertificatesObtain and deploy certificates on Exchange 2013 MBX and CAS servers & Exchange 2010 Edge servers (if required)
4. Publish Protocols ExternallyCreate public DNS A records for the EWS and SMTP endpointsValidate using Remote Connectivity Analyzer
5. Switch autodiscover namespace to 2013 CASChange the public autodiscover DNS record to resolve
to Exchange 2013 CAS
6. Run the Hybrid Configuration Wizard7. Move mailboxes
1
2
3
EWS SMTP
45
6
7
1
2
3
45
6
Notes from the fieldAre you using TMG/ISA to publish EWS? Ensure that you are not using pre-authentication on the following paths:
/ews/mrsproxy.svc/ews/exchange.asmx/wssecurity/autodiscover/autodiscover.svc/wssecurity/autodiscover/autodiscover.svc
You may need to tweak the ‘Flood Mitigation’ limits - http://support.microsoft.com/kb/2654376
Have you enabled MRSProxy?
Add the following URLs to your “Local Intranet” Zone:
https://outlook.office365.comhttps://<on-premises_URL>
What’s New?Public folders are stored in public folder mailboxes
Each public folder mailbox includes the complete public folder hierarchy
No longer uses multi-master replication of folder hierarchy
Public folder mailboxes are stored in regular mailbox databases
Use DAGs for high availability and data redundancy
Cannot coexist with legacy public folders
Legacy vs. Modern Public FoldersLegacy Public Folders Modern Public Folders
Content Storage Public Folder database Public Folder mailbox
Content Replication Between databases Not possible
High Availability PF Replication Database Availability Group
Hierarchy Storage One per DB, multi-master Per mailbox, one master only
Hierarchy Synchronisation SMTP based Direct - Incremental
Search Items only Full text (including attachments)
Permission Management ACLs RBAC
Administration PF Management Consule, EMS EAC, EMS
Supported Outlook versions Any Outlook 2007+
Supported OWA versions OWA 2007, 2010 OWA 2013
Supported Exchange Server versions
Exchange 2010 and earlier Exchange 2013
When should you use Public Folders?
Team Collaboratio
n
Shared Email
Knowledge
Virtual Identity
Shared outcomes
Shared deliverables
Emails and Documents
History of public conversations
Accessible and searchable by
everyone
Appear as virtual identity, e.g.
Working on shared queues
Site Mailboxes
Public Folders
Shared Mailboxes
Modern Public Folder Architecture Clients
Public folders are based on the mailbox architecture
Hierarchy is stored in all PF mailboxes
Content can be broken up and placed across multiple mailboxes
Hierarchy Synchronisation:1. Client connects to a secondary PF
mailbox2. Client creates a new public folder3. Request is proxied to the primary PF
mailbox where it is written to PF hierarchy
4. PF hierarchy synchronisation triggered immediately to content mailbox
5. PF hierarchy is updated on all PF mailboxes:15 mins - users connected24 hrs - no users connected
1
2
3
451
2
3
45
CAS 2013
Folder 3Folder 4
Folder 1Folder 2
Folder 5Folder 6
Hierarchy Hierarchy Hierarchy
Secondary PF Mailbox
Primary PF Mailbox
Secondary PF Mailbox
Public Folders in Exchange Online Public Folder space is provided at no additional cost!
1.25 TB (50 PF mailboxes with 25 GB quota each)One single Public Folder can be as large as 19 GB
Microsoft manages Public Folder mailboxesWhen PF mailbox quota is reached, or active hierarchy connection count is exceeded, Exchange will create another PF mailbox, and move PF contentAuto-split process is not available in Exchange 2013 on-premises
Cross-premises accessExchange Online users can still access on-premises Public Folders Exchange 2013 on-premises users can access Public Folders in Exchange Online
Migration Planning Process
Plan Prepare Migrate
Analyse Public Folders
Review use cases
Understand user distribution
Comms. Plan
Clean-up Public Folders
Run Export and Map scripts
Create new PF Mailboxes
Initiate data migration
Comms. to end-users
Finalise Migration
Dismount legacy PF DBs
Migration ConsiderationsNo coexistence, the migration is a cutover migration
All mailboxes must be on Exchange 2013 and/or Exchange Online prior to Migration
Migrations are PowerShell based, there is no GUI!
Requires Exchange 2007 SP3 RU10 or Exchange 2010 SP3
Exchange Hybrid Deployment is not required*
Public Folders are migrated using Outlook Anywhere, Outlook Anywhere must be published to the internet
Public Folder Migration Scripts/CmdletsScript/Cmdlet Purpose
Export-PublicFolderStatistics.ps1 This script creates the folder name-to-folder size mapping file. (CSV)
PublicFolderToMailboxMapGenerator.ps1 This script creates the public folder-to-mailbox mapping file. (CSV)
Export-MailPublicFoldersForMigration.ps1This script exports the mail-enabled public folder objects from the on-premises Active Directory. Run this script on the legacy Exchange server. (XML)
Import-MailPublicFoldersForMigration.ps1Imports the mail-enabled public folder objects into Exchange Online. Run this script in Exchange Online.
New-Mailbox –PublicFolder Creates a new Public Folder Mailbox.
Set-PublicFolderMigrationRequest -PreventCompletion:$false
Allows the move request to go beyond 95%. Requires legacy Public Folders to be locked.
Set-OrganizationConfiguration –PublicFoldersLockedForMigration: $true
-PublicFolderMigrationComplete: $true
Locks access to legacy Public Folders and allows the Public Folder move request to complete.
Enables mail enabled Public Folders to receive e-mails.
Resume-PublicFolderMigrationRequest Restart a Public Folder migration request to synchronise any changes.
New-PublicFolderMigrationRequestNew-PublicFolderMigrationRequest -OutlookAnywhereHostName $OAHostName -CSVData $MapFile -RemoteCredential $Cred -RemoteMailboxLegacyDN $MailboxLegacyDN -RemoteMailboxServerLegacyDN $PublicFolderServerLegacyDN -AuthenticationMethod <Basic/NTLM>
$OAHostName = Get-OutlookAnywhere | Format-List Identity, ExternalHostName, IISAuthenticationMethods
$MapFile = Get-Content c:\PFMigration\pf2mbx.csv -Encoding Byte
$Cred = Get-Credential
$MailboxLegacyDN = Get-Mailbox Bob | Format-Table LegacyExchangeDN
$PublicFolderServerLegacyDN = Get-ExchangeServer –Identity Server | Format-Table ExchangeLegacyDN
Public Folder Migration Steps Clients
Exchange 2007/2010 – Legacy Public Folders
1. PrepareVerify existing Public FoldersExport-PublicFolderStatistics.ps1PublicFolderToMailboxMapGenerator.ps1Export-MailPublicFoldersForMigration.ps1Import-MailPublicFoldersForMigration.ps1
2. Create Public Folder MailboxesNew-Mailbox –PublicFolder -HoldForMigration:$true -IsExcludedFromServingHierarchy:$true
3. Begin MigrationNew-PublicFolderMigrationRequestHierarchy & Content CopyAuto-Suspend at 95%
4. Lock Source & Complete Migration RequestSet-OrganizationConfig -PublicFoldersLockedForMigration:$trueSet-PublicFolderMigrationRequest -PreventCompletion:$falseResume-PublicFolderMigrationRequest
5. Finalise MigrationSet-Mailbox -PublicFolder -IsExcludedFromServingHierarchy:$falseSet-OrganizationConfig –PublicFolderMigrationComplete:$trueDismount legacy Public Folder databases
1 23
4 5
1 23
4 5
Exchange Online – Modern Public Folder Mailboxes
Related ContentExchange Server 2013 Upgrade and Coexistence - EXL313Inside Office 365 - OSP211
Microsoft Office 365 Deployment - OSP312
Microsoft Exchange Server 2013 Sizing - EXL317Find me later at the closing presentation.
Additional LinksSample Email Migration End-user Communications - http://technet.microsoft.com/en-us/library/hh852412.aspxTMG may cause "Mailbox Move to the cloud fail with error“ - http://support.microsoft.com/kb/2654376Public Folder Migration Scripts - http://www.microsoft.com/en-us/download/details.aspx?id=38407 Public Folder Directory Sync Support Scripts - http://www.microsoft.com/en-us/download/details.aspx?id=38408
Developer Network
Resources for Developers
http://msdn.microsoft.com/en-au/
Learning
Virtual Academy
http://www.microsoftvirtualacademy.com/
TechNet
Resources
Sessions on Demand
http://channel9.msdn.com/Events/TechEd/Australia/2013
Resources for IT Professionals
http://technet.microsoft.com/en-au/
Keep Learning1. Download both Exchange Server 2013 and Lync Server 2013 and try in
your own environment
2. Trial Exchange and Lync Online
3. Contact your Microsoft or Partner Account Manager to arrange a time test drive Exchange and Lync in one of our Customer Immersion Experience Centres
4. Contact your Microsoft or Partner Account Manager to get a Lync business value assessment or an Exchange and Lync technical briefing
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.