IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000...

31
Office 365 – Understanding Hybrid Deployments Daniel Kenyon-Smith Microsoft Consultancy Services UK

TAGS:

Transcript of IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000...

Page 1: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Office 365 ndash Understanding Hybrid DeploymentsDaniel Kenyon-Smith Microsoft Consultancy Services UK

AGENDA

Hybrid Coexistence Features

Hybrid Coexistence Planning and Deployment

Mailbox Replication Service (MRS) MigrationsMoves

IMAP

migration

Cutover

migration

Staged migration

2010

Hybrid

2013

Hybrid

Exchange 55

Exchange 2000

Exchange 2003

Exchange 2007

Exchange 2010

Exchange 2013

NotesDomino

GroupWise

Other

Additional options available with tools from migration partners

Summary of Migration Options S

imp

le M

igra

tion

sH

yb

rid

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

3

Hybrid BenefitsMakes your on-premises organization and cloud organization work together like a single seamless organization

Offers near-parity of featuresexperience on-premises and in the cloud

Seamless interactions between on-premises and cloud mailboxes

Migrations in and out of the cloud transparent to end-user

4

Hybrid Key Features

5

bull Delegated authentication for on-premisescloud web services

bull Enables FreeBusy calendar sharing message tracking online archive and more

Federation Trust

bull Manage all of your Exchange functions whether cloud or on-premises from the same place - Exchange Administration Center (EAC)

Integrated Admin Experience

bull Online mailbox movesbull Preserve the Outlook profile and offline file (OST)bull Leverages the Mailbox Replication Service (MRS)

Native Mailbox Move

bull Authenticated and encrypted mail flowbull Preserves the internal Exchange messages headersbull Support for compliance mail flow scenarios (central

transport)Secure Mail Flow

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 2: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

AGENDA

Hybrid Coexistence Features

Hybrid Coexistence Planning and Deployment

Mailbox Replication Service (MRS) MigrationsMoves

IMAP

migration

Cutover

migration

Staged migration

2010

Hybrid

2013

Hybrid

Exchange 55

Exchange 2000

Exchange 2003

Exchange 2007

Exchange 2010

Exchange 2013

NotesDomino

GroupWise

Other

Additional options available with tools from migration partners

Summary of Migration Options S

imp

le M

igra

tion

sH

yb

rid

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

3

Hybrid BenefitsMakes your on-premises organization and cloud organization work together like a single seamless organization

Offers near-parity of featuresexperience on-premises and in the cloud

Seamless interactions between on-premises and cloud mailboxes

Migrations in and out of the cloud transparent to end-user

4

Hybrid Key Features

5

bull Delegated authentication for on-premisescloud web services

bull Enables FreeBusy calendar sharing message tracking online archive and more

Federation Trust

bull Manage all of your Exchange functions whether cloud or on-premises from the same place - Exchange Administration Center (EAC)

Integrated Admin Experience

bull Online mailbox movesbull Preserve the Outlook profile and offline file (OST)bull Leverages the Mailbox Replication Service (MRS)

Native Mailbox Move

bull Authenticated and encrypted mail flowbull Preserves the internal Exchange messages headersbull Support for compliance mail flow scenarios (central

transport)Secure Mail Flow

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 3: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

IMAP

migration

Cutover

migration

Staged migration

2010

Hybrid

2013

Hybrid

Exchange 55

Exchange 2000

Exchange 2003

Exchange 2007

Exchange 2010

Exchange 2013

NotesDomino

GroupWise

Other

Additional options available with tools from migration partners

Summary of Migration Options S

imp

le M

igra

tion

sH

yb

rid

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

3

Hybrid BenefitsMakes your on-premises organization and cloud organization work together like a single seamless organization

Offers near-parity of featuresexperience on-premises and in the cloud

Seamless interactions between on-premises and cloud mailboxes

Migrations in and out of the cloud transparent to end-user

4

Hybrid Key Features

5

bull Delegated authentication for on-premisescloud web services

bull Enables FreeBusy calendar sharing message tracking online archive and more

Federation Trust

bull Manage all of your Exchange functions whether cloud or on-premises from the same place - Exchange Administration Center (EAC)

Integrated Admin Experience

bull Online mailbox movesbull Preserve the Outlook profile and offline file (OST)bull Leverages the Mailbox Replication Service (MRS)

Native Mailbox Move

bull Authenticated and encrypted mail flowbull Preserves the internal Exchange messages headersbull Support for compliance mail flow scenarios (central

transport)Secure Mail Flow

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 4: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid BenefitsMakes your on-premises organization and cloud organization work together like a single seamless organization

Offers near-parity of featuresexperience on-premises and in the cloud

Seamless interactions between on-premises and cloud mailboxes

Migrations in and out of the cloud transparent to end-user

4

Hybrid Key Features

5

bull Delegated authentication for on-premisescloud web services

bull Enables FreeBusy calendar sharing message tracking online archive and more

Federation Trust

bull Manage all of your Exchange functions whether cloud or on-premises from the same place - Exchange Administration Center (EAC)

Integrated Admin Experience

bull Online mailbox movesbull Preserve the Outlook profile and offline file (OST)bull Leverages the Mailbox Replication Service (MRS)

Native Mailbox Move

bull Authenticated and encrypted mail flowbull Preserves the internal Exchange messages headersbull Support for compliance mail flow scenarios (central

transport)Secure Mail Flow

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 5: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid Key Features

5

bull Delegated authentication for on-premisescloud web services

bull Enables FreeBusy calendar sharing message tracking online archive and more

Federation Trust

bull Manage all of your Exchange functions whether cloud or on-premises from the same place - Exchange Administration Center (EAC)

Integrated Admin Experience

bull Online mailbox movesbull Preserve the Outlook profile and offline file (OST)bull Leverages the Mailbox Replication Service (MRS)

Native Mailbox Move

bull Authenticated and encrypted mail flowbull Preserves the internal Exchange messages headersbull Support for compliance mail flow scenarios (central

transport)Secure Mail Flow

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 6: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid Coexistence Feature Comparison

6

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

FreeBusy and calendar sharing cross-premises

Out of Office understands that cross-premises is ldquointernalrdquo 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 inboundoutbound via on-prem

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 7: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid Coexistence Feature Example

7

Cross-Premises FreeBusy 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 ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 8: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid Coexistence Feature ExampleCross-Premises MailTips

Correct evaluation of ldquoInternalrdquo vs ldquoExternalrdquo organization context

Allows awareness and correct Outlook representation of MailTips

8

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 9: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Hybrid Coexistence Feature ExampleCross-Premises Mail Flow

Preserves internal organizational headers(eg auth header)

Message is considered ldquotrustedrdquo and resolve the sender to rich recipient information in the GAL (not SMTP address)

Restrictions specified for that recipient are honored9

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 10: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

10

Hybrid features and benefits summary Makes your on-premises organization and cloud organization

work together like a single seamless organization Offers near-parity of featuresexperience on-premises and

in the cloud Seamless interactions between on-premises and cloud

mailboxes Migrations in and out of the cloud transparent to end-user

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 11: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

11

2013 hybrid requirements Exchange 2013 CASMBX 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

SMTP domain(s) configured in O365 tenant Directory Sync tool enabled in O365 tenant

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 12: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

12

2013 hybrid limitations Exchange 2003 is not supported Delegation coexistence cross-premises

(delegate permissions are migrated when users are in the same batch)

Migration of Send AsFull Access permissions

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 13: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

13

Hybrid user experience If configured for SSO users login with their AD credentials

Otherwise admin needs to distribute new password to user Userrsquos current Outlook profile is updated with the Exchange

Online server name via Autodiscover Offline files (OST files) do not have to be recreated If using Outlook at the time of the mailbox move user is

prompted to close and reopen Outlook

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 14: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Office 365

Hybrid user experience mdash Autodiscover

14

On-premises systems

ADForest

Exchange 2013

CAS

Remote MailboxPrimary SMTP address usercontosocomRemote Routing address usercontosomailonmicrosoftcom

MailboxPrimary SMTP address usercontosocomSecondary SMTP address usercontosomailonmicrosoftcom

Exchange Online

Where is my mailboxLocal Exchange passes a redirect to ldquocontosomailonmicrosoftcomrdquo

Outlook attempts to discover endpoint through DNS record ldquoautodiscovercontosomailonmicrosoftcomrdquo

Request authenticationAuthentication successMailbox server informationOutlook profile updatedOST rebuild not required

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 15: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

15

2013 hybrid improvements (1 of 2) Adaptive HCW

HCW adapts to individual setup requirements and presents only necessary questions Automatically gathers information whenever possible

Integrated support for EdgeHCW supports configuring Exch2010 Edge Transport servers directly within the wizard

Enhanced secure mailSimpler to configure and no longer dependent on static IP addresses in the connector configuration

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 16: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

16

2013 hybrid improvements (2 of 2) Flexible EOP connection and internet mail routing

Support for updating MX and directing all inbound internet mail to EOP at any stage of the hybrid deployment ndash before during or after hybrid configuration

Improved centralized mail transportAdded flexibility and capability ndash centralized mail transport is supported even when pointing MX to EOP

Integrated mailbox migration and move wizardOne wizard regardless of scenario ndash hybrid staged cutover or IMAP

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 17: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

17

Office 365

2013 hybrid high-level architecture

On-premises Exchange org

Users Groups Contacts via DirSync

Existing Exchange 2007 or later

Office 365 Directory

Synchronizationapp

Exchange 2013 CAS and MBX

Secure Mail Flow

Sharing (freebusy MailTips archive etc)

Mailbox Data via MRS

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 18: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

18

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Set an ExternalUrl for the Exchange Web Services vdir

Exchange 2013 hybrid deploymentfrom an existing Exchange 2007 or 2010 environmentmdashno Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to

E2013 CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

45

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

7

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 19: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

19

2 Deploy Exchange 2013 servers

Install both E2013 MBX and CAS servers

Install E2010 EDGE servers

Set an ExternalUrl for the Exchange Web Services vdir

2013 hybrid deployment flowfrom an existing Exchange 2007 or 2010 environmentmdashwith Edge Transport server

E2010 or 2007 Hub

Internet facing site

Intranet site

Exchange 2010 or 2007

servers

1 Prepare

Install Exchange SP andor updates across the ORGPrepare AD with E2013 schema

4 Publish protocols externallyCreate public DNS A records for the EWS and SMTP endpoints

Validate using Remote Connectivity Analyzer5 Switch autodiscover namespace to E2013

CASChange the public autodiscover DNS record to

resolve to E2013 CAS6 Run the Hybrid Configuration Wizard

E2013 CAS

3 Obtain and deploy certificatesObtain and deploy certificates on E2013 MBX and CAS servers amp E2010 EDGE servers

Clientsautodiscovercontosocommailcontosocom

1 2

3

4

5

6

E2010 or 2007 CAS

E2010 or

2007 MBX

E2013 MBX

SPRU

SPRU

Office 365

7 Move mailboxes

Autodiscover amp EWS SMT

P

E2010 EDGE

7

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 20: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

20

Hybrid configuration wizard1) Start HWC from EAC2) Confirm running the wizard3) Select hybrid domain4) ViewCopy domain proof token5) Choose transport options6) Choose receive 2013 CAS server(s)7) Choose send 2013 MBX server(s)8) Select transport certificate9) Enter external FQDN 2013 CAS10) Enter Org Management AD account11) Enter Global Admin O365 account12) Choose Update to configure hybrid

Adaptive steps

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 21: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

21

Exchange 2013 tenant compatibility Exchange 2013 is only

supported against the next version of O365 tenant

Current O365 tenants must be fully upgraded to be compatible with Exchange 2013 on-premises

Exchange 2013 Setup and HCW include a tenant version check

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 22: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

22

Exchange 2010 hybrid support Exchange 2010 SP3 will be compatible with current and

new O365 tenants Exchange 2010 based hybrid deployments will continue to

support Exchange 2003 coexistence with the new O365 tenants

Now the the new O365 service is launched Exchange 2013 based hybrid is recommended for all new deployments (unless migrating from Exchange 2003)

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 23: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

23

Hybrid ndash Deployment Process

Sign up for Office

365

Register your

domains with

Office 365

Deploy Office 365 Directory

Sync

Install Exchange 2013 CAS

amp MBX Servers

(Edge opt)

Publish the CAS Server(Assign

SSL certificate firewall

rules)

Run the Hybrid Wizard

Exchange specific deployment tasks

(deep dive on next slide)

General Office 365 deployment tasks

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 24: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

24

Migration Tool launched from Exchange Admin Center (EAC)

In EAC select recipients | migration

Start migration wizard

Choose hybrid remote move

and follow prompts

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 25: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

25

Migration Tools also available via PowerShell

Example-new-MoveRequest -identity $_UserPrincipalName -Remote -RemoteHostName mailcompanycom -RemoteCredential $cred -TargetDeliveryDomain lsquotenantnamemailonicrosoftcom

Set of Hybrid Move Cmdlets

New-MoveRequest

Get-MoveRequest

Get-MoveRequestStatistics

Suspend-MoveRequest

Resume-MoveRequest

Remove-MoveRequest

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 26: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

26

Hybrid Considerations Flood mitigation - httpcommunityoffice365comen-uswikisexchangeoffice-365-move-mailbox-fails-with-transient-exceptionaspx

Ensure HCW has no pre-auth and EWS and autoD are published externally for TMG to use - httpcommunityoffice365comen-uswexchange1042aspx

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 27: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

27

Hybrid Considerations Ensure service address is added as secondary proxy to all mailboxes being

migrated Remove old proxies not used potentially added by legacy messaging

systems Ensure UPN is federated with tenant Registry fix is added to suppress AutoDiscover warning Locate messages over 25MB-

PFAD ExMerge Search-Mailbox (for 2010)

Internet access for Exchange set-exchangeServer (set-exchangeserver -internetwebproxyhttpproxyport)

Certs installed for TLS to FOPEEOP (Exchangecompanycom for example and must be public certs)

Ensure there are no 3rd party devices in use between Exchange on-prem and FOPE

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 28: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

28

Hybrid Considerations Hybrid Wizard Logging

By default located at CProgram FilesMicrosoftExchange ServerV14LoggingUpdate-HybridConfiguration

Attempt to find the AutoDiscover endpoint in Public DNS httpsautodiscoverdomainautodiscoverautodiscoversvc

You need your Autodiscover public DNS records for your SMTP domains pointing to an on-premises Exchange 2010 SP23 (2013) server

Test Autodiscover at wwwtestexchangeconnectivitycom

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 29: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Additional Resources

Exchange Team Blog

Introduction to Hybrid

Deploying Hybrid (Exchange 2013)

Managing Hybrid (Exchange 2013)

TechNet

Hybrid Deployments

Deploying an Hybrid Configuration with the Exchange Hybrid Configuration Wizard

29

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 30: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

Additional ResourcesTools

Exchange Remote Connectivity Analyzer

httpswwwtestexchangeconnectivitycom

Exchange Client Network Bandwidth Calculator

httpgallerytechnetmicrosoftcomExchange-Client-Network-8af1bf00

PST Capturehttpwwwmicrosoftcomen-usdownloaddetailsaspx

PowerShell Scriptshttptechnetmicrosoftcomen-uslibraryhh974318aspx

30

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31
Page 31: IMAP migration Cutover migration Staged migration 2010 Hybrid2013 Hybrid Exchange 5.5 Exchange 2000 Exchange 2003 Exchange 2007 Exchange 2010 Exchange.

copy 2012 Microsoft Corporation All rights reserved Microsoft Windows and other product names are or may be registered trademarks andor trademarks in the US andor other countriesThe 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

  • Office 365 ndash Understanding Hybrid Deployments
  • Slide 2
  • Summary of Migration Options
  • Slide 4
  • Hybrid Key Features
  • Hybrid Coexistence Feature Comparison
  • Hybrid Coexistence Feature Example
  • Hybrid Coexistence Feature Example (2)
  • Hybrid Coexistence Feature Example (3)
  • Hybrid features and benefits summary
  • 2013 hybrid requirements
  • 2013 hybrid limitations
  • Hybrid user experience
  • Hybrid user experience mdash Autodiscover
  • 2013 hybrid improvements (1 of 2)
  • 2013 hybrid improvements (2 of 2)
  • 2013 hybrid high-level architecture
  • Exchange 2013 hybrid deployment from an existing Exchange 2007
  • 2013 hybrid deployment flow from an existing Exchange 2007 or 2
  • Hybrid configuration wizard
  • Exchange 2013 tenant compatibility
  • Exchange 2010 hybrid support
  • Hybrid ndash Deployment Process
  • Slide 24
  • Slide 25
  • Hybrid Considerations
  • Hybrid Considerations (2)
  • Hybrid Considerations (3)
  • Slide 29
  • Slide 30
  • Slide 31

Cutover and ServiceNow

Cutover and ServiceNow

Exchange 2013 Migration & Coexistence

Exchange 2013 Migration & Coexistence

Migration From Exchange 2010 to Exchange 2013 Part One

Migration From Exchange 2010 to Exchange 2013 Part One

Cutover Template

Cutover Template

CutOver Plan Upgrade TEMPLATE

CutOver Plan Upgrade TEMPLATE

Cutover Forum Presentation

Cutover Forum Presentation

THE 2016 EXCHANGE MIGRATION SOLUTION SELECTION GUIDE · THE 2016 EXCHANGE MIGRATION SOLUTION SELECTION GUIDE ... When choosing a migration solution, ... or the removal of …

THE 2016 EXCHANGE MIGRATION SOLUTION SELECTION GUIDE · THE 2016 EXCHANGE MIGRATION SOLUTION SELECTION GUIDE ... When choosing a migration solution, ... or the removal of …

Exchange Migration Guide - IceWarp Mail Serverdl.icewarp.com/documentation/server/tools/Exchange_Migrator_Guide.… · Microsoft Exchange Server Location ... Exchange Migration Guide

Exchange Migration Guide - IceWarp Mail Serverdl.icewarp.com/documentation/server/tools/Exchange_Migrator_Guide.… · Microsoft Exchange Server Location ... Exchange Migration Guide

IMAP migration Cutover migration Staged migrationHybrid Exchange 5.5X Exchange 2000X Exchange 2003XXXX* Exchange 2007XXXX Exchange 2010XXX Exchange.

IMAP migration Cutover migration Staged migrationHybrid Exchange 5.5X Exchange 2000X Exchange 2003XXXX* Exchange 2007XXXX Exchange 2010XXX Exchange.

51 Cutover Templates

51 Cutover Templates

Weekly Cutover Market Call

Weekly Cutover Market Call

Cutover Plan v2

Cutover Plan v2

Exchange Migration Guide - IceWarp · Exchange Migration Guide 13 Migration from MS Exchange 2003 to 2007 Prior to Migration to IceWarp Server The whole process of migration is summarized

Exchange Migration Guide - IceWarp · Exchange Migration Guide 13 Migration from MS Exchange 2003 to 2007 Prior to Migration to IceWarp Server The whole process of migration is summarized

Data Migration Cutover Checklist Template

Data Migration Cutover Checklist Template

GMail Migration for Exchange

GMail Migration for Exchange

SRM Vendor Cutover Plan

SRM Vendor Cutover Plan

Cutover Migration Guide Step by Step › 2017 › 05 › cutover...6 Step 4: Connect Office 365 to your email system Now you set up the connection between your Exchange email system

Cutover Migration Guide Step by Step › 2017 › 05 › cutover...6 Step 4: Connect Office 365 to your email system Now you set up the connection between your Exchange email system

State Data Center - Washington Technology · 2020-01-07 · address particular phases (e.g. pre-cutover, cutover, and post-cutover). Checklist - A readiness checklist summarizing

State Data Center - Washington Technology · 2020-01-07 · address particular phases (e.g. pre-cutover, cutover, and post-cutover). Checklist - A readiness checklist summarizing

Migration in Hosted Exchange 2010

Migration in Hosted Exchange 2010

exchange migration 2003 to 2007

exchange migration 2003 to 2007