Collect Needed Information for an Exchange 2007 Hybrid Deployment
Applies to: Exchange Server 2010 SP1
To configure a hybrid deployment between your on-premises Exchange organization and the cloud-based organization, you're going to need information about your current deployment. You might want to print this step so you can record your organization's information and have easy access to it as you go through the checklist.
Learn more at: Understanding Hybrid Deployment
Warning
This topic is meant to be read as part of the Microsoft Exchange Server 2007 and Office 365 Hybrid Deployment checklist. Information or procedures in this topic may depend on prerequisites configured in topics earlier in the checklist. To view the checklist, see Checklist - Exchange 2007 and Office 365 Hybrid Deployment
We recommend using the Microsoft Office 365 Deployment Readiness Tool to analyze your existing Exchange organization and confirm that the prerequisites for a hybrid deployment are met. The readiness tool is integrated with the guidance provided in the Microsoft Office 365 Beta Deployment Guide and provides detailed assessments for Exchange Online, user identity and account provisioning, client and end-user experience, and many other areas.
Learn more at: Microsoft Office 365 Deployment Readiness Tool
You can use the following table to gather information about your existing organization that you're going to need before you get started with the deployment. When you're working through your checklist, replace the example information that you see in the checklist with the information you've provided in this table. For example, if the external fully qualified domain name (FQDN) of your Exchange 2007 server is exchange.adatum.com, enter that FQDN in the "Value in your organization" field.
| Description | Example value in checklist | Value in your organization |
|---|---|---|
Active Directory forest root |
Corp.contoso.com |
|
Internal Exchange 2007 Client Access/Hub Transport server host name |
EX2007 |
|
External Exchange 2007 Client Access/Hub Transport server FQDN |
mail1.contoso.com |
|
Proposed internal hybrid server host name |
EX2010 |
|
Proposed external hybrid server FQDN |
mail2.contoso.com |
|
Outlook Web App URL |
Owa.contoso.com |
|
Primary SMTP namespace |
Contoso.com |
|
User principal name domain Microsoft Online ID domain |
Contoso.com |
|
The following table lists new services that you configure as part of the hybrid deployment. For the values you provide in the table below, we recommend that you replace contoso.com with your domain name and use the example subdomains provided below. For example, if your domain is adatum.com, we recommend that you enter service.adatum.com in the "Value in your organization" field for the service SMTP namespace.
| Description | Example value in checklist | Value in your organization |
|---|---|---|
Service SMTP namespace Important You must not use the service tenant FQDN, specified below, as the service SMTP namespace. We recommend that you use service.<your domain>. |
Service.contoso.com |
|
Internal Active Directory Federation Services (AD FS) server hostname |
ADFS |
|
External AD FS server FQDN |
Sts.contoso.com |
|
Internal Active Directory synchronization server host name |
DirSync |
|
Exchange federation trust namespace |
Exchangedelegation.contoso.com |
|
On-premises Autodiscover FQDN |
Autodiscover.contoso.com |
|
Service Autodiscover FQDN |
Autodiscover.service.contoso.com |
|
Service tenant FQDN Note You can only choose the subdomain portion of this FQDN. The domain portion must be "onmicrosoft.com". |
Contoso.onmicrosoft.com |
|
Having problems? Ask for help in the Office 365 forums. To access the forums, you'll need to sign in using an account that's granted administrator access to your cloud-based service. Visit the forums at: Office 365 Forums
© 2010 Microsoft Corporation. All rights reserved.