1 / 57

Exchange Online: Simple Migration

yaholo
Download Presentation

Exchange Online: Simple Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Exchange Online: Simple Migration

    2. Agenda What is Simple Migration? Why do it? Simple IMAP migration Cutover Exchange migration Staged Exchange migration with simple Co-existence

    3. Coexistence Migration

    4. Cutover IMAP Migration

    5. Built on Cmdlets New-MigrationBatch Start-MigrationBatch Get-MigrationBatch Get-MigrationStatus Complete-Migration Test-MigrationServerAvailability

    6. Simple IMAP Migration Tested against Cyrus, Courier, Dovecot, UW, Exchange Server 2003 and Exchange Server 2007 (many customers migrated from other IMAP servers) Provide remote server settings, list of users and it takes care of the rest Max 10 connections to remote server to avoid overloading servers/bandwidth Tested against Cyrus, Courier, Dovecot, UW, Exchange Server 2003 and Exchange Server 2007 (many customers migrated from other IMAP servers) Provide remote server settings, list of users and it takes care of the rest Max 10 connections to remote server to avoid overloading servers/bandwidth

    7. Requirements for IMAP Migration No OnPremises tool install required

    8. Requirements for IMAP Migration No OnPremises tool install required Access to IMAP ports (143/993)

    9. Requirements for IMAP Migration No OnPremises tool install required Access to IMAP ports (143/993) Users must be provisioned in the cloud Bulk provisioning, CSV parser, manual, etc.

    10. Requirements for IMAP Migration No OnPremises tool install required Access to IMAP ports (143/993) Users must be provisioned in the cloud Bulk provisioning, CSV parser, manual, etc. Gather user credentials or setup admin credentials

    11. Requirements for IMAP Migration No OnPremises tool install required Access to IMAP ports (143/993) Users must be provisioned in the cloud Bulk provisioning, CSV parser, manual, etc. Gather user credentials or setup admin credentials Prepare a CSV file with list of users EmailAddress, username, password

    12. Flow of a Typical IMAP Migration Incremental syncs every 24 hours, non-configurable Multiple CSVs, sequentially Incremental syncs every 24 hours, non-configurable Multiple CSVs, sequentially

    13. Flow of a Typical IMAP Migration

    14. Cutover Exchange

    15. Cutover Exchange

    16. Cutover Exchange Migration Objective: Provide a simple & complete cutover migration experience for on-premises exchange customers to move the cloud Supports migrating mailbox content from Exchange Server 2003 and later Migration from on-premise or hosted systems Merge operation; not Move High fidelity migrations Mail, calendar, tasks and many more

    17. Cutover Exchange Migration Has its own provisioning built in Autodiscover < 10k mailboxes < 50k object count Creates distribution groups and GAL contacts in the cloud Creates distribution groups and GAL contacts in the cloud

    18. Requirements Enable Outlook Anywhere (RPC/HTTP) on source server Need to have CA issued certs if they are not already setup Give full access permissions to all mailboxes that will be migrated “Receive-As” preferred/easier Accepted domain setup in the service

    19. Provisioning NSPI != Dirsync LegDNs SEM performs its own provisioning to create mailboxes, DLs and contacts in the cloud for an organization Uses NSPI to reach into the on-premise directory NSPI is the protocol that Outlook uses to get to your address book Will only read some attributes from directory Brings over LegDNs and other SMTP proxy addresses to maintain reply-ability SEM performs its own provisioning to create mailboxes, DLs and contacts in the cloud for an organization Uses NSPI to reach into the on-premise directory NSPI is the protocol that Outlook uses to get to your address book Will only read some attributes from directory Brings over LegDNs and other SMTP proxy addresses to maintain reply-ability

    20. 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

    21. Architecture

    22. Scope Partial migrations

    23. Scope Partial migrations DDL or Security Groups

    24. Scope Partial migrations DDL or Security Groups System mailboxes

    25. Scope Partial migrations DDL or Security Groups System mailboxes MailboxGUIDs preservation

    26. Scope Partial migrations DDL or Security Groups System mailboxes. MailboxGUIDs preservation Config on sync interval 26 | Microsoft Confidential

    27. Scope Partial migrations DDL or Security Groups System mailboxes. MailboxGUIDs preservation Config on sync interval Folder exclusion

    28. Scope Partial migrations DDL or Security Groups System mailboxes. MailboxGUIDs preservation Config on sync interval Folder exclusion Time range selection

    29. What Will Be Migrated? Message Items Delivery Reports NDRs Read/Non-Read Receipt Folders Rules Categories

    30. What Will Be Migrated? Calendar items Recurrences Exceptions Meeting Request/Cancelation/Response OOF settings Categories

    31. What Will Be Migrated? Tasks Notes Contacts Public delegates Folder permissions Custom forms Outlook settings (e.g. Folder favorites)

    32. End User Experience Admin needs to distribute new passwords to end users (using mail/prints ) Users creates their profile using new passwords All mail is downloaded from the cloud mailbox OST resync is not avoidable

    33. Flow for Typical Cutover Exchange Migration Incremental syncs every 24 hours, non-configurable Typically one time, rerun for errors, new mailboxes Licensing will happen later in Office 365, 30 day grace period Incremental syncs every 24 hours, non-configurable Typically one time, rerun for errors, new mailboxes Licensing will happen later in Office 365, 30 day grace period

    34. Flow for Typical Cutover Exchange Migration Incremental syncs every 24 hours, non-configurable Typically one time, rerun for errors, new mailboxes Licensing will happen later in Office 365, 30 day grace period Incremental syncs every 24 hours, non-configurable Typically one time, rerun for errors, new mailboxes Licensing will happen later in Office 365, 30 day grace period

    35. Walkthrough: Cutover Exchange Migration

    36. Microsoft Confidential

    37. Microsoft Confidential

    38. Microsoft Confidential

    39. Microsoft Confidential

    40. Microsoft Confidential

    41. Microsoft Confidential

    42. Microsoft Confidential

    43. Microsoft Confidential

    44. Staged Exchange

    45. Staged Exchange

    46. Staged Exchange

    47. Staged Exchange

    48. Simple Coexistence Regular mail flow between all mailboxes It is a topology Defined by the presence of MSO Dirsync Mailboxes are spread across cloud and on-premises End goal is to fully exist in the cloud

    49. Staged Exchange Migration Objective: Developed to enable migration for Simple Co-existence topologies Detects the presence of MSO Dirsync for Office 365 tenants If IsDirsyncRunning=No Then Cutover Migration Else If IsDirsyncRunning=Yes Then Staged Migration Until the switch to Office 365, EDU tenants will only have Staged Exchange Migration

    50. Requirements Same as cutover Outlook Anywhere Permissions to mailboxes + MSO Dirsync

    51. Provisioning and Passwords Provisioning For every migrating on-Premise mailbox there needs to be a MEU or Mailbox in the cloud Migration Service Relies on DirSync to do the provisioning Passwords Target mailbox passwords need to specified for all the users. Optionally, Administrators can force user to change it on first logon.

    52. CSV File One user per line – Primary SMTP of mailbox Up to 1000 mailboxes in each CSV Smart-check against the cloud directory

    53. Differences from Cutover Incremental syncs not needed Users start using their cloud mailboxes when they are created, new mail is available immediately, old content fills in Stamps targetAddress on source mailboxes to support mail flow from on-premises to cloud Optional password change There are no incremental syncs with Staged migration, one time initial sync Users start using their cloud mailboxes when they are created, new mail is available immediately, old content fills in Stamps targetAddress on source mailboxes to support mail flow from on-premises to cloud Optional password change There are no incremental syncs with Staged migration, one time initial sync Users start using their cloud mailboxes when they are created, new mail is available immediately, old content fills in Stamps targetAddress on source mailboxes to support mail flow from on-premises to cloud Optional password change

    54. Flow for Typical Staged Exchange Migration

    55. Flow for Typical Staged Exchange Migration

    56. Q & A

More Related