Introduction

4 FeatureSimpleHybrid Mail routing between on-premises and cloud (recipients on either side) Mail routing with shared namespace (if desired) on both sides Unified GAL Free/Busy and calendar sharing cross-premises Out of Office understands that cross-premises is “internal” to the organization Mailtips, messaging tracking, and mailbox search work cross-premises OWA redirection cross-premise (single OWA URL for both on-premises and cloud) Single tool to manage cross-premises Exchange functions (including migrations) Mailbox moves support both onboarding and offboarding No outlook reconfiguration or OST resync required after mailbox migration Preserve auth header (ensure internal is not spam, resolve against GAL, etc.) Centralized mail flow, ensures that all routes inbound/outbound via on-prem

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

Cross-Premises MailTips Correct evaluation of “Internal” vs. “External” organization context Allows awareness and correct Outlook representation of MailTips 6

Cross-Premises Mail Flow Preserves internal organizational headers (e.g. auth header) Message is considered “trusted” and resolve the sender to rich recipient information in the GAL (not SMTP address) Restrictions specified for that recipient are honored 7

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

Hybrid Improvements

Deployment

Sign up for Office 365 Register your domains with Office 365 Deploy Office 365 Directory Sync Install Exchange 2013 CAS & MBX Servers (Edge opt) Publish the CAS Server (Assign SSL certificate, firewall rules) Run the Hybrid Wizard Exchange specific deployment tasks General Office 365 deployment tasks Demo

2. Deploy Exchange 2013 servers Install both E2013 MBX and CAS servers Set an ExternalUrl and enable the MRSPRoxy on the Exchange Web Services vdir E2010 or 2007 Hub Internet facing site Intranet site Exchange 2010 or 2007 Servers 1. Prepare Install Exchange SP and/or updates across the ORG Prepare AD with E2013 schema 4. Publish protocols externally Create public DNS A records for the EWS and SMTP endpoints Validate using Remote Connectivity Analyzer 5. Switch autodiscover namespace to E2013 CAS Change the public autodiscover DNS record to resolve to E2013 CAS 6. Run the Hybrid Configuration Wizard E2013 CAS 3. Obtain and Deploy Certificates Obtain and deploy certificates on E2013 MBX and CAS servers Clients autodiscover.contoso.com mail.contoso.com E2010 or 2007 CAS E2010 or 2007 MBX E2013 MBX SP/RU Office Move mailboxes EWS SMTP 7

In the Background

Set-hybridConfiguration/OrgRelationship AutoD

ExchangeDelegation who???

Tiny Tenant mode

Tenant Hydration

What the heck is the Service domain?

Stored in Active Directory

Logging and Troubleshooting

Logging for all changes made

Exchange 2007

Exchange 2003 Not HCW Related (New- Remot box behavior) Before SP2 Exchange Admin Group was the LegDN Now the External Admin Group is the LegDN for Remote Mailboxes by default

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Microsoft Confidential - For Internal Use Only 11/4/2012

Layer 4 LB mail.contoso.com Cloud FB request Internet facing site E2013 MBX E2013 CAS Intranet site E2010 MBX E2010 CAS HTTP PROXY Cross site proxy request Set 2010 URL to: `mail.contoso.com

SOAP request will include the following element: When an Exchange 2010 CAS server receives the EWS call, it will throw an HTTP 500 response Autodiscover response will have the following element: <h:ServerVersionInfo MajorVersion="14" MinorVersion="3" MajorBuildNumber="123" MinorBuildNumber="3" 2010 soap: Remove the TargetSharingEPR settings in the Organization Relationship

Hybrid OWA redirection does not work as expected, this is being addressed in cu3 This is not an issue on 2010 hybrid environments

Some customers are concerned that the EAP will overwrite users when HCW is run What if the EAP is not applied Will it revert the users primary address… There is a new values we use with HCW When we run update- AddressPolicy we use the “UpdateSecondaryAddressesOnly” parameter This prevents the users Primary SMTP address from getting overwritten with settings in the EAP

From 2010 sp3 ru2 you will see the domain proof missing… use Shell Get-FederatedDomainProof

From 2010 sp3 ru2 you will not be able to add additional domains to a federation trust from the UI, you have to use the shell as a workaround

The Move fail to initiate but there is no error This occurs for many reason Bad password, MRS disabled, publishing issues Use PowerShell or EAC to perform the hybrid moves

You will not be able to manage up-level objects, this means 2010 EMC cannot manage org settings for a wave 15 tenant. Use EAC instead for org management

Deployment guidance Exchange Deployment Assistant Troubleshooting articles General Hybrid troubleshooting Guided Walkthroughs Hybrid Free Busy Client Connectivity Mailflow

Lesson review

Please answer the survey questions posted at the end of this meeting. Let us know what sessions you want! Josh Topal at Feel free to give feedback too.

Q&A and Feedback

© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.