Upload
maximillian-bryan
View
221
Download
0
Tags:
Embed Size (px)
Citation preview
Exchange Online: Simple Migration OptionsName Ram PoornalingamTitle Program ManagerMicrosoft Corporation
Session Objectives and Takeaways
Session Objective(s): Migration OverviewCutover Simple Exchange migration Staged Simple Exchange migrationWhat’s Coming?
Key TakeawayUnderstand the migration solutions availableUnderstand when and how to use them
Migration Overview
1 150 5,000 25,000
Organizational Size in Users
SEM(Cut-Over SEM)
SEM with DirSync(SSEM)
MRS
Mig
ratio
n S
olu
tion
s
<1 Week 2 Weeks 3 Weeks Several Months
Co-existence
None Mailflow/GalSync Free/Busy, Archive in Cloud
Time For Migration including Planning
Example Profiles and Solutions
1• Source: E2007• Users: 250• Time: Weekend• Identity Mgmt:
On-premise• Co-
existence:Simple• Solution:SSEM
4• Source: E2010• Users: 250• Time: Weekend• Identity Mgmt:
On-premise• Co-
existence:Rich• Solution:MRS
2• Source: E2003• Users: 75• Time: Weekend• Identity Mgmt:
On-premise• Co-
existence:Simple• Solution:SSEM
5• Source: E2003• Users: 75• Time:
Weekend• Identity Mgmt:
Cloud• Co-
existence:None• Solution:SEM
3• Source: E2010• Users: 75• Time: Weekend• Identity Mgmt:
Cloud• Co-
existence:None• Solution:SEM
6• Source: E2003• Users: 2075• Time: 1 Week• Identity Mgmt:
On-Premise• Co-existence:
Simple• Solution:SSEM
Cutover Simple Exchange Migration
Objective:
A simple Exchange migration solution for small and medium businesses to move to Office 365
6
Cutover Exchange
7
8
Cutover Exchange
Cutover Exchange Migration
CapabilityMigration from Exchange Server 2003 and greaterOn-premise or hosted systemsIntegrated Provisioning High fidelity migrations- Mail, calendar, tasks and many more
9
Requirements
<= 1k mailboxes<= 50k object countEnable Outlook Anywhere (RPC/HTTP) on source server
Need to have CA issued certs if they are not already setup
10
Permissions
Create Migration User Mailbox say miguserFor Hosted Scenarios, give full access to miguser on all the mailboxes to be migratedFor On-Premise, give receive-as access to miguser . This can be done at the DB scope
Microsoft Confidential
Passwords
No access to passwords from source directory New passwords created for all provisioned mailboxes
A link to download passwords are sent to admin at the end of migration Users must change password at next login
Microsoft Confidential 12
ArchitectureA simplistic view
Source E2K3/E2K7
RPCNSPI
1
Datacenter
2' Migration Service
MRS (RPC/HTTP)
2
HTTPS
Source server endpoints
Datacenter processes
1. Leverages NSPI to read directory and provision recipients
2. Uses RPC/HTTP (Outlook Anywhere) to migrate data
13
DNS Server
ExchangeServer
New-Organization
MSO DirSync
CAS CAS
System Mailbox
2a
1https://portal.microsoftonline.com
Exchange Online
Office 365
1
2b
2c
Migration Service
MRS
HUB
3
5
Office 365- SEM Migration
Add Customer domain:contoso.com
MRS
Update Cname Record
2a
2b
2c Verify Domain Ownership
Admin Actions
Service Actions
Service Actions
Scans requestjob queue
Enable License on Users
12
3 In Office365 -enters Server Info, and Test and Start
4 MS: Creates Job and Job Items
6 Connect to MRS and validate request
7 Create AD Object and a merge request job in system mailbox
8 Tickle MRS Service
12
Federated Mailbox
User Mailbox
MS: reaches out through NSPI, calls BPS to provision users, contacts, groups etc.
5
Merge-Request CmdLet
4
4
6
7
7
8
Admin Actions
9
9
10
Complete Migration11
11Migration Service
AD
Connects to source and target mailbox and copy messages
Bulk Provisioning
Service
10
96 8 9
10
10
Bulk Provisioning
Service
10
4
Scope
NO
15
Partial Migrations
DDL or Security Groups
OST Preservations
Folder Exclusions
Time Range Selections
Client side search folders
Client side rules
Quick Steps
RSS Feeds
Arbitration Mailbox
Config Sync on IntervalDumpster 1.0
What Will Be Migrated?
Message Items Delivery ReportsNDRs Read/Non-Read Receipt
FoldersRulesCategories
• Read status • Flags • Mapping of special folders
• Deleted Items• Sent items• Drafts• Search folders
16
What Will Be Migrated?
Calendar items Recurrences Exceptions Meeting Request/Cancelation/ResponseOOF settings Categories
Calendar
Microsoft Confidential 17
What Will Be Migrated?
Tasks NotesContacts Public delegates Folder permissions Custom forms
Other
Microsoft Confidential 18
End User Experience
End user gets the password from AdminEnd user performs the first logon to reset the password.End user creates a new outlook profile and OST file and re-syncs all the content
Microsoft Confidential 19
Flow for Typical Cutover Exchange Migration
Enable Outlook/Anywhere
Setup mailbox permissions
Enter remote server details
Provision MBXes, MEUs, contacts,
DLs,
Microsoft Confidential 20
Flow for Typical Cutover Exchange Migration
Initial Sync
Incremental syncs
Change MX record
Complete migration
Final Sync/Clean-up
Microsoft Confidential 21
Piloting
No simple piloting experienceAll users will be migrated to the cloudInternal emails sent between on-cloud mailboxes will not be transmitted to on-premise mailboxesMail will flow to source mailbox until MX record switch
Cutover Exchange Migration
Demo
23
Staged Exchange Migration
Objective: A simple Exchange migration solution for medium and large businesses to move to Office 365
Microsoft Confidential 24
Staged Exchange
25
Staged Exchange
Microsoft Confidential 26
Staged Exchange
Microsoft Confidential 27
Staged Exchange
Microsoft Confidential 28
Requirements
Same as cutover Outlook AnywherePermissions to mailboxes
+ MSO Dirsync
29
Provisioning and Passwords
ProvisioningFor every migrating on-Premise mailbox there needs to be a MEU or Mailbox in the cloudMigration Service relies on DirSync to do the provisioning
PasswordsTarget mailbox passwords need to specified for all the users. Optionally, Administrators can force user to change it on first logon.
Microsoft Confidential 30
CSV File
31
Differences from Cutover
Incremental syncs not neededUsers start using their cloud mailboxes when they are created, new mail is available immediately, old content fills inStamps targetAddress on source mailboxes to support mail flow from on-premises to cloudOptional password change
32
Flow for Typical Staged Exchange Migration
Setup MSO Dirsync
Setup mailbox permissions
Prepare CSV
Enter remote server details
Upgrade MEUs to MBXs
Microsoft Confidential 33
Flow for Typical Staged Exchange Migration
Add TargetAddress to On-prem mailbox
Data sync
Change MX Record
Complete migration
Clean up
Simple Coexistence
Microsoft Confidential 34
Piloting
GoalsMigrate only test accountsNo easy off boarding solution
Microsoft Confidential
What’s Coming
What?1. Multiple Batch Support• Ability to schedule multiple batches.
Only one active batch• Ability to retry failed Users in that batch• No more finalization• Batch Lifecycle management• Reporting changes
• No overall report
2. MigrationUser• Live per user statistics like items
migrated, skipped, last successful sync time
3. Migration Dashboard Enhancements4. Troubleshooting enhancement
1. Skipped items2. Error Details
When?1. GA2. Public Beta 3. GA4. GA
Documentation Links
Cut-Over SEMhttp://help.outlook.com/en-us/beta/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Staged SEMhttp://help.outlook.com/en-us/beta/ff959224.aspx
Microsoft Confidential
In Review: Session Objectives and Takeaways
Session Objective(s): Migration OverviewCutover Simple Exchange migration Staged Simple Exchange migration
Key TakeawayUnderstood the available migration solutions Understood when and how to use them
Related Content
Breakout Sessions/Chalk TalksUC315 Using Microsoft Exchange Sever 2010 to Achieve Rich Coexistence with Exchange OnlineUC310 Foreign Email Migration and Coexistence to Exchange Server 2010OFC203 What Do Existing Customers Need to DO to Prepare for Office 365?
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.
Question & Answer
41