Vous êtes sur la page 1sur 38

This session details Step 3 (Enhanced) Hybrid migrations for deploying Office 365

services. Understand the implications of this deployment approach and the steps
required to expand the service offerings as part of FastTrack Enhanced phase.

Summary of migration options

Introduction to Hybrid
capabilities

Exchange Server 2013 Hybrid


improvements

Infrastructure dependencies

Step by steps deployments

Hybrid migration

Summary of Migration Options *


IMAP migration

Cutover migration

Staged migration

Hybrid 2010

Exchange 5.5

Exchange 2000

Exchange 2003

Exchange 2007

Exchange 2010

Exchange 2013

Notes/Domino

GroupWise

Other

Import of Archived/Offline Mail

Migration

IMAP migration (IMAP)


Supports wide range of email platforms
Email only (no calendar, contacts, or tasks)

Cutover Exchange Migration (CEM)


Good for fast, cutover migrations up to 2,000 mailboxes
No migration tool or computer required on-premises

Staged Exchange Migration (SEM)

Hybrid

No server required on-premises


Identity federation with on-premises directory

Hybrid deployment
Manage users on-premises and online
Enables cross-premises calendaring, smooth migration, and easy off-boarding

Hybrid 2013

PST Migration

PST Migration

Self Service or Admin Driven Options


Control

Self Service

Admin-Driven

Deployment Type

Description

Federation Trust

Delegated authentication for on-premises/cloud web services


Enables Free/Busy, calendar sharing, message tracking, online
archive, and more

Integrated Admin
Experience

Manage all of your Exchange functions, whether cloud or onpremises from the same place - Exchange Administration
Center (EAC)

Native Mailbox
Move
Secure Mail Flow

Remote move migration (Online mailbox moves)


Preserve the Outlook profile and offline file (OST)
Leverages the Mailbox Replication Service (MRS)
Authenticated and encrypted mail flow
Preserves the internal Exchange messages headers
Support for compliance mail flow scenarios (central transport)

Hybrid Coexistence Feature Comparison


Feature

Simple

Hybrid

Mail routing between on-premises and cloud (recipients on either side)

Mail routing with shared namespace (if desired) on both sides

Unified GAL

Free/Busy and calendar sharing cross-premises

Out of Office understands that cross-premises is internal to the organization

Mailtips, messaging tracking, and mailbox search work cross-premises

OWA redirection cross-premise (single OWA URL for both on-premises and cloud)

Single tool to manage cross-premises Exchange functions (including migrations)

Mailbox moves support both onboarding and offboarding

No outlook reconfiguration or OST resync required after mailbox migration

Preserve auth header (ensure internal email is not spam, resolve against GAL, etc.)

Centralized mail flow , ensures that all email routes inbound/outbound via on-prem

Hybrid Coexistence Feature Example


Cross-Premises Free/Busy and
Calendar Sharing
Creates the look and feel of a
single, seamless organization for
meeting scheduling and
management of calendars
Works with any supported Outlook
client

Hybrid Coexistence Feature Example


Cross-Premises MailTips

Correct evaluation of Internal vs.


External organization context
Allows awareness and correct
Outlook representation of MailTips

Hybrid Coexistence Feature Example


Cross-Premises Mail Flow

Preserves internal organizational


headers (e.g. auth header)
Message is considered trusted
and resolve the sender to rich
recipient information in the GAL
(not SMTP address)
Restrictions specified for that
recipient are honored

Hybrid Coexistence Feature Example


Single OWA URL

Ensures a good end-user


experience as mailboxes are
moved in-and-out of the cloud
since OWA URL remains
unchanged (points to on-premises
hybrid CAS)
Log in experience can be improved
by adding domain name into your
cloud URL so that you can access
your cloud mailbox without the
interruption of Go There page

Exchange 2013 CAS/MBX server on-premises


Hybrid configuration in place
On-premises config, O365 config, federation using MFG, certificates, etc.
Much of the config is automated by the Hybrid Configuration Wizard

Directory Sync tool enabled in

Exchange 2003 is not supported (*)


Delegation Coexistence cross-premises
(delegate permissions are migrated when users are in the same
batch)
Migration of Send As/Full Access permissions

* For Exchange organization running Exchange 2003, consider


using Exchange 2010 SP3 Hybrid deployment

On-premises Systems
Remote Mailbox
Primary SMTP address:
user@contoso.com
Remote Routing address:
user@contoso.mail.onmicrosoft.com

Office 365
Mailbox
Primary SMTP address:
user@contoso.com
Secondary SMTP address:
user@contoso.mail.onmicrosoft.com

AD
Forest

Exchange
2013 CAS

Exchange
Online

Where
Local Exchange
Request
Authentication
Mailbox
Outlook
is server
my
authentication
profile
attempts
mailbox?
success
information
updated.
passes
to discover
a redirect
endpoint
to
through DNS record
contoso.mail.onmicrosoft.com
autodiscover.contoso.mail.onmicrosoft.com
OST
rebuild not required!

Adaptive HCW

Integrated Support for Edge

Enhanced Secure Mail

Flexible Exchange Online Protection (EOP) Connection and Internet


Mail Routing

Improved Centralized Mail Transport

Integrated Mailbox Migration and Move Wizard

On-premises Exchange Org


Office 365 Directory
Synchronization
App

Office 365

Users, Groups, Contacts via DirSync

Secure Mail Flow


Sharing (free/busy, MailTips, archive, etc.)

Existing
Exchange
2007 or
later

Exchange
2013 CAS
and MBX

Mailbox Data via MRS

Clients

autodiscover.contoso.com
mail.contoso.com

5
1

E2010 or E2010 or
2007 Hub 2007 CAS

E2013
CAS

Internet facing site

Install Exchange SP and/or RU/CU across the ORG


Prepare AD with Exchange 2013 (schema, Org, domains)
2. Deploy Exchange 2013 CU1 (or above) servers

Autodiscover & EWS


SMTP

Install both Exchange 2013 MBX and CAS servers


Exchange 2010
or 2007 Servers
SP/RU

Intranet site

1. Prepare

Set an ExternalUrl for the Exchange Web Services vDir

SP/RU

E2010
or 2007
MBX

Office 365

3. Exchange 2007 Create legacy namdspace


Create DNS record point to legacy Exchange 2007 CAS
3 bis. Obtain and Deploy Certificates
Obtain and deploy certificates on Exchange 2013 CAS
Exchange 2007 - Deploy certificates on Exchange 2007 CAS
4. Publish protocols externally
Create public DNS A records for the EWS and SMTP endpoints
Validate using Remote Connectivity Analyzer

E2013
MBX

5. Switch autodiscover namespace to Ex2013 CAS


Change the public autodiscover DNS record to resolve to
Exchange 2013 CAS and update vDirs (and re-validate)
6. Run the Hybrid Configuration Wizard
7. Move mailboxes

Clients

Office 365

autodiscover.contoso.com
mail.contoso.com

E2010 or E2010 or
2007 Hub 2007 CAS

Prepare AD with E2013 schema

2. Deploy Exchange 2013 servers


Install both E2013 MBX and CAS servers

4
E2013
CAS

E2010
EDGE

SP/RU

Install E2010 EDGE servers (if not already deployed)


Exchange 2010
or 2007 Servers
SP/RU

Intranet site

7
Internet facing site

Set an ExternalUrl for the Exchange Web Services vdir

3. Obtain and Deploy Certificates

Obtain and deploy certificates on E2013 CAS servers


& E2010 EDGE servers
If Exchange 2007 create legacay namespace (DNS and certs)

4. Publish protocols externally

Create public DNS A records for the EWS and SMTP endpoints
Validate using Remote Connectivity Analyzer

6
E2010
or 2007
MBX

Install Exchange SP and/or updates across the ORG

Autodiscover &
EWS
SMTP

5
1

1. Prepare

5. Switch autodiscover namespace to E2013 CAS


E2013
MBX

Change the public autodiscover DNS record to resolve to


E2013 CAS

6. Run the Hybrid Configuration Wizard


7. Move mailboxes

Hybrid Configuration Wizard


Start HWC from on-premises EAC
Sign-in to Office 365 (non ADFS)*
1)
And relaunch the HCW
3)
Confirm running the wizard
4)
Select hybrid domain*
5)
View/Copy domain proof token*
6)
Choose transport options
7)
Choose receive 2013 CAS server(s)
8)
Choose send 2013 MBX server(s)
9)
Select transport certificate
10) Enter external FQDN 2013 CAS
11) Enter Org Management AD account
12) Enter Global Admin O365 account
13) Choose Update to configure hybrid
14) Wait for HCW updates to complete
15) Review instructions post HCW completion
1)
2)

* Adaptive steps

In EAC, select
recipients | migration

Select Migrate to
Exchange Online

Start migration
wizard
Choose hybrid
remote move and
follow prompts

Set of Migration Cmdlets

Migration Batch
cmdlets can also
start a hybrid
move

> New-MigrationBatch
Set of Hybrid Move Cmdlets
> Start-MigrationBatch
> New-MoveRequest
> Get-MigrationBatch
> Get-MoveRequest
> Get-MigrationStatus
> Get-MoveRequestStatistics
Diaginostic switch
> Complete-Migration
improves
> Suspend-MoveRequest
troubleshooting
> Test-MigrationServerAvailability
> Resume-MoveRequest
> Remove-MoveRequest
New!

> Get-MigrationBatch -Diagnostic

Hybrid move
cmdlets continue
to be available

Outlook.com Help
Migration to Exchange online
IMAP Migrations
Cutover Exchange Migrations

Staged Exchange Migrations

Exchange Team Blog


Introduction to Hybrid

Deploying Hybrid (Exchange 2013)


Managing Hybrid (Exchange 2013)
Decommissioning Hybrid (2010 related
article)

TechNet
Hybrid Deployments
Deploying an Hybrid Configuration with
the Exchange Hybrid Configuration
Wizard

https://www.testexchangeconnectivity.com/
Server - https://www.testexchangeconnectivity.com/
Client https://testconnectivity.microsoft.com/?tabid=Client

http://gallery.technet.microsoft.com/Exchange-ClientNetwork-8af1bf00
http://www.microsoft.com/enus/download/details.aspx
http://technet.microsoft.com/enus/library/hh974318.aspx
http://blogs.technet.com/b/thomas_ashworth/