•
We are recording today’s session, and will have the slide show presentation
and the video recording on the original blog post and the Office 365
Community. You can find the video recording on our Video Channel http://www.youtube.com/microsoftoffice365
•
Questions can be asked at the end of the presentation through the Lync
Meeting Console.
•
We are recording today’s session, please understand that you may be
captured in the recording. If you do not wish to be recorded, please do not
type in the Lync IM Window or please leave the meeting.
Introduction
Feature
4
Simple Hybrid
Mail routing between on-premises and cloud (recipients on either side)
Mail routing with shared namespace (if desired) on both sides
Unified GAL
Free/Busy and calendar sharing cross-premises
Out of Office understands that cross-premises is “internal” to the organization
Mailtips, messaging tracking, and mailbox search work cross-premises
OWA redirection cross-premise (single OWA URL for both on-premises and cloud)
Single tool to manage cross-premises Exchange functions (including migrations)
Mailbox moves support both onboarding and offboarding
No outlook reconfiguration or OST resync required after mailbox migration
Preserve auth header (ensure internal email is not spam, resolve against GAL, etc.)
Centralized mail flow , ensures that all email routes inbound/outbound via on-prem
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
5
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
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
8
Hybrid Improvements
Flexible EOP Connection and Internet Mail Routing
Improved Centralized Mail Transport
Integrated Mailbox Migration and Move Wizard
Adaptive HCW
Integrated Support for Edge
Enhanced Secure Mail
Deployment
Sign up for
Office 365
Register
your
domains
with Office
365
Deploy
Office 365
Directory
Sync
General Office 365 deployment
tasks
Install
Exchange
2013 CAS
& MBX
Servers
(Edge opt)
Publish the
CAS Server
(Assign SSL
certificate,
firewall
rules)
Exchange specific deployment
tasks
Run the
Hybrid
Wizard
Demo
Clients
5
1
2
E2010 or E2010 or
2007 Hub 2007 CAS
3
E2013
CAS
SP/RU
EWS
Install Exchange SP and/or updates across the ORG
Prepare AD with E2013 schema
SMTP
2. Deploy Exchange 2013 servers
4
Install both E2013 MBX and CAS servers
Exchange 2010
or 2007 Servers
SP/RU
Intranet site
6
E2010
or 2007
MBX
1. Prepare
Office 365
autodiscover.contoso.com
mail.contoso.com
7
Internet facing site
E2013
MBX
Set an ExternalUrl and enable the MRSPRoxy on the
Exchange Web Services vdir
3. Obtain and Deploy Certificates
Obtain and deploy certificates on E2013 MBX and
CAS servers
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
7. Move mailboxes
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
[10/10/2011 2:11:49] INFO:Cmdlet: Get-WebServicesVirtualDirectory --Processing
Time: 281.2608.
[10/10/2011 2:11:49] INFO:Running command: Set-WebServicesVirtualDirectory Identity 'E14SP2-E2K10\EWS (Default Web Site)' -MRSProxyEnabled 'True'
[10/10/2011 2:11:49] INFO:Cmdlet: Set-WebServicesVirtualDirectory --Start Time:
10/9/2011 10:11:49 PM.
[10/10/2011 2:11:50] INFO:Cmdlet: Set-WebServicesVirtualDirectory --End Time:
10/9/2011 10:11:50 PM.
[10/10/2011 2:11:50] INFO:Cmdlet: Set-WebServicesVirtualDirectory --Processing
Time: 1062.5408.
[10/10/2011 2:11:50] INFO:Running command: Set-OrganizationRelationship MailboxMoveEnabled 'True' -FreeBusyAccessEnabled 'True' -FreeBusyAccessLevel
'LimitedDetails' -ArchiveAccessEnabled 'True' -MailTipsAccessEnabled 'True' MailTipsAccessLevel 'All' -DeliveryReportEnabled 'True' -TargetOwaURL
'http://outlook.com/owa/e14sp2.gtrcloudtraining.com' -Identity 'On Premises to
Exchange Online Organization Relationship'
[10/10/2011 2:11:50] INFO:Cmdlet: Set-OrganizationRelationship --Start Time:
10/9/2011 10:11:50 PM.
[10/10/2011 2:11:51] INFO:Cmdlet: Set-OrganizationRelationship --End Time:
10/9/2011 10:11:51 PM.
[10/10/2011 2:11:51] INFO:Cmdlet: Set-OrganizationRelationship --Processing
Time: 78.128.
Exchange 2007
Exchange 2003
• Not HCW Related
(NewRemoteMailbox
behavior)
• Before SP2
Exchange
Admin Group
was the LegDN
• Now the
External Admin
Group is the
LegDN for
Remote
Mailboxes by
default
http://technet.microsoft.com/enus/library/hh529921(v=exchg.150).aspx#BKMK_HybridConfigProces
s
Exchange Server 2010 Coexistence – requires External URL to be set…
Cloud FB request
Set 2010 URL to:
`mail.contoso.com
mail.contoso.com
Layer 4 LB
HTTP
PROXY
E2013 CAS
E2013 MBX
Internet facing site
E2010 CAS
Cross
site
proxy
request
E2010 MBX
Intranet site
• SOAP request will include the following element:
• <ext:RequestServerVersion Version="Exchange2012"
xmlns:ext="http://schemas.microsoft.com/exchange/services/2006/types"
/>
• 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:
• <ext:RequestServerVersion Version="Exchange2009"
xmlns:ext="http://schemas.microsoft.com/exchange/services/2006/types"
/>
Remove the TargetSharingEPR settings in the Organization Relationship
http://support.microsoft.com/kb/2838688
• Hybrid OWA redirection does not work as expected, this is being addressed in
cu3
• This is not an issue on 2010 hybrid environments
• http://support.microsoft.com/kb/2890814
• 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 email address…
• There is a new values we use with HCW
• When we run update-EmailAddressPolicy 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! Email Josh
Topal at v-joshto@Microsoft.com.
•
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.
