Embed Size (px)
Citation preview
Migration to Office 365Eyal Doron - senior technical support – Office 365 Israel
2
Part 1
• What should I know before I jump into the deep water?
• Office 365 - Subscription plans
• Office 365 – Trail account
• Office 365 – what should I know before I move to the cloud ?
• Migration to the cloud - General concepts
AGENDA
3
Part 2
• Cutover Exchange Migration (CEM)
• Hybrid migration
• IMAP Migration
• Staged Exchange Migration (SEM)
• Tools, tips
•
AGENDA
4
Set expectation The purpose is to present obstacles\issues that could can cause unpleasant experience to Partner\customer that want to move to the cloud
5
Set expectation |Mail Migration The purpose is to provide high level presentation about the optional migration path, the different charters of each of the migration options by choosing the “right” migration option base on the business scenario.
The presentation is not intended to be “How to“ presentation.
To be able to “know” how to implement the migration process its recommended to have “hands-on experience”
6
Moving to the cloud!
There could be many “hold ups” that could delay the process Partners point of view: unfamiliar area, un know Territory, Job security etc
Customer point of view: data privacy, data safety, costs, new interfaces, products, technologies
7
Common goal
You ( Microsoft partners), we ( Microsoft) and the customer have few common goals: 1. Happy and satisfied customer 2. Improvement and optimization of business
process
8
Easy and simple ?
Yes, but…..If you understand the formula
Training\education
=Hands on experience+Easy and simple
9
The three building block for success
Know to difference between the Subscription plans
Know to difference between the Migration options
Know the deferent option\tools and technology that you can use and how to
use them
Office 365 - Subscription plans
11
Office 365 - Subscription plans
Office 365 portal: Mix and match, modular license plans
12
Office 365 - Subscription plans | information Office 365 - comparing P, M and E plans
13
Office 365 - Subscription plans | information Office 365 service comparison
14
Office 365 - Subscription plans | information Office 365 Service Descriptions
15
Office 365 - Subscription plans | less is more ?Each of the subscription plans offer different products, technology, options etc.
Many time the basic assumption is that Best interests of the client\customer is to guide him to Purchase to most “low price” subscription plan.
Office 365 – Trail account
17
Office 365 – Trail account
Compare Office 365 for business planshttp://office.microsoft.com/en-us/business/compare-office-365-for-business-plans-FX102918419.aspx
18
Office 365 – Trail account
Microsoft Office demoshttps://www.microsoftofficedemos.com/
Office 365 – what should I know before I move to the cloud ?
20
Office 365 – what should I know before I move to the cloud ? Client desktop Desktop OS Desktop hardware Desktop Software updates
Outlook version
21
Office 365 – what should I know before I move to the cloud ? Office 365 mail infrastructure Mail Flow Deleted mail item policy
Migration to the cloud General concepts
23
Migration ?
Most of the time when we mention the term “migration” we relate to the organization mail infrastructure.
The mail infrastructure could be: Exchange On-Premises mail infrastructure. POP3\IMAP4 mail infrastructure
24
Migration ?
SharePoint migration In the current time, there is no built-in tools for SharePoint Online migration to Office 365.
25
Migration ?
When we describe mail infrastructure migration we relate to: 1. Directory objects: Users, groups and contacts2. Mailbox content
26
Multiple IdentitiesWhen a customer join Office 365 services, each of the users will have two Identities: 1. On-Premises Active directory identity. 2. “Cloud” identity ( AD Azure user account).
27
Identity management and directory objectsThe subject of Identity management and directory objects relate to two realms: 1. Migration to the cloud 2. Day to day directory management
28
Migration to the cloud different scenarios Office 365 offers a verity of methods and tolls that was designed to provide a proper solution for different type of organizations and different scenarios.
29
on-Premises mail infrastructure | Users and mailboxes
30
Mail migration |Best practice methods
SOHO\SMB Organization Mid\Large organization
CoexistenceCloud only
Cutover Migration Hybrid Migration
Co existence
KIS = Keep is simple
31
Scenario 1: Non existing mail infrastructure The charter for this scenario is: a small organization that didn't have a mail infrastructure and, most of the time doesn't use Domain and Active Directory infrastructure.
In this scenario, the “new user's account” will be created in the AD Azure and, a mailbox will be assigned to each of these users. The user management standard operation such as: reset user password, update user details and son on, will be implemented by using the Office 365 management portal.
32
Scenario 2: Existing mail infrastructure Under the classification of:” Existing mail infrastructure” we can classify two types of mail infrastructures: 1. Hosted\External mail infrastructure. 2. on-Premises mail infrastructure.
33
Hosted\External mail infrastructure. The charter for this scenario is: An SMB organization ( most of the times) that use an external mail service. The Hosted\External mail services could be also classified into two types of categories:
1. Exchange based Hosted\External mail services.
2. External “Internet” mail services (POP3\IMAP4\SMTP).
34
Hosted\External mail infrastructure. When relating to Other Hosted\External mail services (POP3\IMAP4\SMTP), we can migrate (copy) the content of the mailboxes to Office 365 mail infrastructure but we will have to create a “user account” for each of the users whom their mailboxes will be migrated to the cloud.
When relating to a scenario of: migrating from Exchange based Hosted\External mail services, the basic assumption is that we can also import the “user account” to the AD azure directory additionally to the process of migrating the mailbox content.
35
on-Premises mail infrastructure In a scenario of: on-Premises mail infrastructure the assumption is that the existing mail infrastructure is based on Exchange on-Premises. ( in case that the organization uses other products the charters are very similar or identical to the scenario of: External “Internet” mail infrastructure).
36
on-Premises mail infrastructure | Users and mailboxes In a on-Premises mail infrastructure migration there are couple of optional scenarios that relate to the subject of Users and mailboxes:
37
Migration option decision factors
37 | Microsoft Confidential
DEPLOYMENT PLAN
Migration solution is part of the
plan
Source server
ExchangeIMAPLotus NotesGoogle
Size
LargeMediumSmall
Identity management
On-premisesSingle sign-onOn-cloud
Provisioning
DirSyncManual/Bulk ProvisioningAutomatic Provisioning
Coexistencerequirement
SimpleRich
38
Migration to Office 365
39
Migration type characters
40
Migration to Office 365 - Pre requirements for Exchange On-Premises server
IMAP migration
Cutover
migration
Staged migration
2010
hybrid
2013
hybrid
Exchange 5.5
Exchange 2000
Exchange 2003
Exchange 2007
Exchange 2010
Exchange 2013
Notes/Domino
GroupWise
Other
*Additional options available with tools from migration partners
Summary of migration options*S
imp
le m
igra
tion
sH
ybri
d
IMAP migrationSupports wide range of email platformsEmail only (no calendar, contacts, or tasks)
Cutover Exchange migration (CEM)Good for fast, cutover migrationsNo migration tool or computer required on-premises
Staged Exchange migration (SEM)No migration tool or computer required on-premisesRequires Directory Synchronization with on-premises AD
Hybrid deploymentManage users on-premises and onlineEnables cross-premises calendaring, smooth migration, and easy off-boarding
41
CUTOVEREXCHANGEMIGRATIONS(CEM)
43
Cutover migration – Features and Benefits Simple and quick migration solution High-fidelity solution – all mailbox content is migrated. Typically best suited to small and medium
organizations. Users are provisioned automatically during migration. Works with Exchange 2003 and newer Works with on-premises or hosted Exchange systems Identity management in the cloud (at least initially) On-premises migration Tools is not required ( the
migration tool is included in the Exchange Online management interface)
44
CEM – Requirements and Limitations Up to 1000 mailboxes in source system Outlook Anywhere service on source system –
Exchange On-Premises server (must have SSL certificate issued by a public CA)
Migration Account with Full Access or Receive-As permissions to all mailboxes that will be migrated
Directory Sync tool disabled in O365 tenant SMTP domains configured in O365 tenant
45
CEM accounts and passwords Accounts provisioning
Migration tool creates users, mailboxes, DLs and contacts Migration enables replies to migrated messages
(i.e. provision process brings over the Legacy DNs)
Passwords No access to passwords from source directory New passwords created for all users A link to download passwords is sent to admin Users must change password on their first login
46
CEM – Data Migration Scope
Migrated Mail messages and
folders Rules and categories Calendar (normal,
recurring) Out-of-Office settings Contacts Tasks Delegates and folder
perms Outlook settings (e.g.
favorites)
Not Migrated Security Groups, DDLs System mailboxes Dumpster Send-As Permissions Messages larger than 25
MB
47
CEM – Data Migration Scope
Partial migrations are not possible (folder exclusion, time range)
Mailboxes enabled for Unified Messaging cannot be migrated
Existing cached-mode files (OST files) cannot be preserved
48
CEM – User Experience
Admin needs to distribute new passwords to users Users create their new Outlook profile using O365
username and new passwords (Autodiscover) All mail is downloaded from the Office 365 mailbox
(i.e. the OST file must be recreated)
49
Migration Tool launched from Exchange Admin Center (EAC)
In EAC, select recipients | migration
Start migration wizard
Choose migration type
and follow prompts
Wizard:
Enter server settings and admincreds
Deltasync every
24 hours
Mark migration as
complete
Change MX
record
CEM – Migration Flow
50
Initial sync
Final sync and
cleanup
License users
Configure
Outlook Anywhe
re
Test using ExRCA
Assign migrati
onperms
Migration
toolprovisi
onsusers
mailboxes
DLscontact
sin O365
51
Cutover migration | Migration process
52
Cutover migration | Mail Flow
53
Cutover migration | Mail Flow
54
Cutover migration - Related links• Migrate All Mailboxes to Exchange Online with a Cutover
Migration
• Exchange Cutover Migration
• From the MVPs: Exchange 2007 cutover migration to the NEW Office 365
Video links
• Ignite Webcast - Cutover and Staged Migrations
• Exchange Online: Migrating Mailboxes to Office 365
• Migrating Email to Office 365
STAGEDEXCHANGEMIGRATIONS(SEM)
56
SEM – Features and Benefits
Simple and flexible migration solution High-fidelity solution – all mailbox content is
migrated Typically best suited to medium and large
organizations Users are provisioned with Directory Sync prior to
migration No limit on the number of mailboxes Users can be migrated in batches (up to 1000 per
batch) Works with Exchange 2003 and 2007 only, on-
premises or hosted Identity management on-premises On-premises migration tool is not required
57
SEM – Requirements and Limitations Outlook Anywhere service on source system
(must have SSL certificate issued by a public CA) Migration Account with Full Access or Receive-As
permissions to all mailboxes that will be migrated Directory Sync tool enabled in O365 tenant SMTP domain(s) configured in O365 tenant SEM is not supported with Exchange 2010 and
2013 Only simple coexistence is available
(no sharing of free/busy, calendar, etc.)
58
SEM - deployment Uses Directory Synchronization for GAL synchronization Enabler for mail routing between on-premises and Office 365 using a
shared DNS namespace
Provides a unified GAL experience
Can be used with cloud identities or federated identities
Does not require an on-premises Hybrid server
59
SEM accounts and passwords Accounts provisioning
Migration tool relies on DirSync to do provisioning For every on-premises mailbox to be migrated there needs
to be a MEU or Mailbox in Office 365
Passwords The DirSync include the ability to sync On-Premises AD users
password to the cloud ( this feature is optional not mandatory)
60
SEM – Data Migration Scope
Migrated Mail messages and
folders Rules and categories Calendar (normal,
recurring) Out-of-Office settings Contacts Tasks Delegates and folder
perms Outlook settings (e.g.
favorites)
Not Migrated Security Groups, DDLs System mailboxes Dumpster Send-As Permissions Messages larger than 25
MB
61
SEM – Data Migration Scope
Partial migrations are not possible (folder exclusion, time range)
Mailboxes enabled for Unified Messaging cannot be migrated
Existing cached-mode files (OST files) cannot be preserved
62
SEM batch file format
CSV format Email address, password, force change password
One user per line Max of 1000 users in each CSV Smart-check against the Office 365 directory
63
SEM – User Experience
Admin needs to distribute new passwords to users Users create their new Outlook profile using O365
username and new passwords (AutoDiscover) All mail is downloaded from the Office 365 mailbox
(i.e. the OST file must be recreated)
Configure
Directory
Sync
Wizard:
Enter server settings and admincreds
Mark migration as
complete
Change MX
record
SEM – Migration Flow
64
Initial Sync
Final sync and
cleanup
License users
Configure
Outlook Anywhe
re
Test using ExRCA
Assign migrati
onperms
65
Convert mailboxes after a SEM
Convert Exchange 2003 mailboxes to mail-enabled users after a staged Exchange migration
Convert Exchange 2007 mailboxes to mail-enabled users after a staged Exchange migration
66
DirSync’s role in migrations: Enables coexistence
Provisions objects in Office 365 with same email addresses as the objects in the on-premises environment
Provides a unified Global Address List experience between on-premises and Office 365 Objects hidden from the GAL on-premises are also hidden from the
GAL in Office 365
Enables coexistence for Exchange Works in both simple and hybrid deployment scenarios
Enabler for mail routing between on-premises and Office 365 with a shared domain namespace
67
Stage migration | Migration process
68
Stage migration | Migration process
69
Stage migration | Migration process
70
Stage migration - Related links• Staged Exchange Migration
• Migrate Mailboxes to Exchange Online with a Staged Migration
• Manage Migration Batches in Exchange Online
Video links
• Ignite Webcast - Cutover and Staged Migrations
• Exchange Online: Migrating Mailboxes to Office 365
• Migrating Email to Office 365
Hybrid
72
Hybrid – Overview Suitable for mid\large organization that need to test\
try\get familer with the Office 365 mail infrastructure
73
Hybrid infrastructure – Logical wrapper
74
Hybrid Deployment Features Secure mail routing between on-premises and
Exchange Online organizations. Mail routing with a shared domain namespace. A unified global address list, also called a “shared
address book”. Free/busy and calendar sharing between on-
premises and Exchange Online organizations. Centralized control of outbound mail flow A single Outlook Web App URL for both the on-
premises and Exchange Online organizations.
75
Hybrid Deployment Features Move existing on-premises mailboxes to the Exchange
Online organization. Centralized mailbox management using the on-
premises Exchange Management Console Message tracking, MailTips, and multi-mailbox
search between on-premises and Exchange Online organizations.
Cloud-based message archiving for on-premises Exchange mailboxes
76
Exchange Server Deployment Assistant Exchange Server Deployment Assistant
How do I Decide• Exchange Deployment Options Whitepaper• Office 365 for Enterprise Service Descriptions• Office 365 Advisor • Microsoft Office 365 Deployment Readiness Tool• Microsoft Office 365 Deployment Guide for
Enterprises
Microsoft Confidential77
78
Hybrid – Components Office 365 Hybrid server(s) - On Premises Active Directory synchronization ADFS Microsoft Federation Gateway Transport Certificates Hybrid Configuration Wizard
79
Office 365 and Hybrid server(s) - On Premises Office 365 for enterprises Microsoft Exchange 2010 SP3 or later Mailbox, Client Access, and Hub Transport server roles
Windows Server 2003 forest functional mode or higher
80
Microsoft Federation Gateway Identity service that runs over the Internet Uses SSL certificates and proof of domain ownership Establish trust relationships with multiple partners O365 Tenant automatically creates Federation Trust
Creat
e Auto
Org Relationship
81
Hybrid Configuration Wizard Guides End-to-End process for Hybrid Deployment
Replaces approximately 50 manual steps Validate Permissions Verify Prerequisites and Topology Creates the HybridConfiguration object in Active Directory
Makes the configuration changes to create and enable the hybrid deployment
82
Hybrid Configuration Coexistence domain
Adds as accepted domain <domain>.mail.onmicrosoft.com Adds as secondary proxy domain to any e-mail address policies
Exchange federation Check for an existing federation trust Use Existing or Create a federation trust Create and Configure organizational relationships Enable free/busy sharing, Outlook Web App redirection, message
tracking, and MailTips
Mailbox Moves Enable the Mailbox Replication Service (MRS) proxy
Mail flow Configure On Premises Servers and FOPE for Mail Routing
83
Hybrid infrastructure – Mail Shared SMTP Namespaces Secured and Authenticated Mail Flow
Channel Privacy Receiver Authentication with Domain Validation Sender Authentication
Each organization treats the other one as an internal
84
Hybrid infrastructure | Directory and Mailbox migration
85
Hybrid infrastructure – Mail flow
Mail routing: pre-coexistence
86
On-premises
Messa
ge fi
lterin
g
MX Record:contoso.com
User ObjectMailbox-enabledProxyAddresses: SMTP: [email protected]
Exchange
Active Directory
Mail routing: on-premises to Office 365
87
On-premises
Messa
ge fi
lterin
g
MX Record:contoso.com
Exchange
Active Directory
Office 365
MX Record:contoso.onmicrosoft.com
contoso.mail.onmicrosoft.com
Exc
hange O
nlin
e P
rote
ctio
n
Exchange Online
Online Directory
DirSync DirSync Web Service
Logon Enabled UserMailbox-enabledProxyAddresses: SMTP: [email protected] smtp: [email protected] smtp: [email protected]
User ObjectMail-enabled (not mailbox-enabled)ProxyAddresses: SMTP: [email protected]: SMTP: [email protected]
Mail routing: Office 365 to on-premises
88
On-premises
Messa
ge fi
lterin
g
MX Record:contoso.com
Exchange
Active Directory
Office 365
MX Record:contoso.onmicrosoft.com
contoso.mail.onmicrosoft.com
Exc
hange O
nlin
e P
rote
ctio
n
Exchange Online
Online Directory
DirSync DirSync Web Service
Logon Enabled UserMail-enabled (not mailbox-enabled)ProxyAddresses: SMTP: [email protected] smtp: [email protected] smtp: [email protected]: SMTP: [email protected]
User ObjectMailbox-enabledProxyAddresses: SMTP: [email protected]
89
Hybrid infrastructure - Related links Hybrid Configuration Wizard Prerequisites Hybrid Deployment Prerequisites Checklist - Exchange 2003 and Office 365 Hybrid Deployment Exchange Hybrid Deployment and Migration with Office 365
IMAP MIGRATIONS
91
IMAP – Features and Benefits Works with a large number of source mail systems Works with on-premises or hosted systems Users can be migrated in batches On-premises migration tool is not required
92
IMAP – Requirements and Limitations On-premises migration tool is not required Access to IMAP ports (TCP/143/993) Users + mailboxes must be provisioned prior to
migration Bulk provisioning, CSV parser, manual, etc.
SMTP domains configured in O365 tenant Gather user credentials or setup admin credentials Prepare a CSV file with list of users
EmailAddress, UserName, Password Max of 50,000 rows Max 10 MB in size
93
IMAP – Data Migration Scope
Migrated Mail messages
(Inbox and other folders) Maximum of 500,000
items Possible to exclude
specific folders from migration(e.g. Deleted Items, Junk E-Mail)
Not Migrated Contacts, Calendars,
Tasks, etc. Excluded folders Folders with a forward
slash( / ) in the folder name
Messages larger than 25 MB
94
IMAP – Migration Flow
Deltasync every
24 hours
Mark migration as
complete
Change MX
record
Gather IMAP creds and
prepare CSV
Provision
users+
mailboxes
in O365
(license
assigned)
Wizard:Enter server settings and
upload CSV
Initial sync Final
sync and
cleanup
Additional Resources
Outlook.com Help
Simple Migrations
Compare Simple Migration Types
IMAP Migrations
Cutover Exchange Migrations
Staged Exchange Migrations
Tools
Exchange Remote Connectivity Analyzer
Exchange Client Network Bandwidth Calculator
PST Capture
PowerShell Scripts
95
Recommended tools
97
Hybrid – Requirements and Limitations
99
Microsoft Office Configuration Analyzer Tool 1.1 Microsoft Office Configuration Analyzer Tool 1.1
100
IdFix DirSync Error Remediation Tool IdFix DirSync Error Remediation Tool
101
Microsoft Remote Connectivity Analyzer Microsoft Remote Connectivity Analyzer
102
Microsoft Exchange Server MAPI Editor Microsoft Exchange Server MAPI Editor
103
Office 365 Network Analysis Tool Office 365 Network Analysis Tool
104
Office 365 - Troubleshooting wizards Office365 Outlook Connectivity Guided
Walkthrough Mail Flow Guided Walkthrough for Office 365 Hybrid Environment Free/busy Troubleshooter
105
Tools -Exchange Client Network Bandwidth Calculator
Exchange Client Network Bandwidth Calculator
106
Tools -View all tools View all tools
107
Tools -View all tools Lync Online Sign-in Guided Walkthrough
Recommended Links
109
Related reading• Exchange Server Migrations
• Mailbox Migration to Exchange Online
• Office 365 Deployment Guide for Enterprises
Video OFFICE 365 GUIDES EXCHANGE GUIDES Exchange Online: Migrating Mailboxes to Office 365
Its recommended to visit the Office 365 Hebrew bloghttp://office365tech.microsoft.co.il
I hope that the information was useful. See you on the next presentation Eyal doron
© 2012 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.
