Module 12

Integrating Exchange Server 2010 with Other

Messaging Systems

Module Overview

• Designing Exchange Server 2010 Integration with Other Messaging Systems

• Designing Exchange Server 2010 Integration with Federated Partners

• Designing Exchange Server 2010 Integration with Exchange Online

Lesson 1: Designing Exchange Server 2010 Integration with Other Messaging Systems

• Coexistence Scenarios for Exchange Server 2010

• Designing Integration with other Exchange Server Organizations

• Designing Message Routing with Unique SMTP Namespaces

• Designing Message Routing with the Same SMTP Namespace

• Designing Global Address List Synchronization

• Designing Calendar Interoperability

Coexistence Scenarios for Exchange Server 2010

Coexistence scenarios include:

• Other Exchange Server organizations

• Other SMTP messaging systems

• Non-SMTP messaging systems

Unlike upgrades, coexistence with other messaging systems requires integration of separate systemsUnlike upgrades, coexistence with other messaging systems requires integration of separate systems

Designing Integration with Other Exchange Server Organizations

When designing integration, you should determine:

• The namespace to use

• Whether to synchronize the GAL

• Whether to synchronize free/busy information

Other Exchange Server organizations do not automatically synchronize the GAL or calendarsOther Exchange Server organizations do not automatically synchronize the GAL or calendars

Reasons for integration with other Exchange Server organizations:

• Merger of two organizations

• Close partnership of two organizations

Designing Message Routing with Unique SMTP Namespaces

Each organization has a different domain nameEach organization has a different domain name

Configuration varies depending on the scenario:

• Completely separate infrastructure

• Separate infrastructure with a direct link

• Shared infrastructure

Designing Message Routing with the Same SMTP Namespace

All messages must be delivered to the Exchange 2010 organizationAll messages must be delivered to the Exchange 2010 organization

• Configure connectivity between the messaging systems

• Configure an accepted internal relay domain

• Configure a Send connector

• Configure MX records for the Exchange Server 2010 organization

Designing Global Address List Synchronization

You need to implement GAL synchronization to make external recipients available in the address bookYou need to implement GAL synchronization to make external recipients available in the address book

Considerations for synchronizing GAL:

• In a small organization, you can manually update recipients

• For large organizations, you should automate the process by using:

• LDAP replication scripts

• Forefront Identity Manager

• Use federated sharing to share contacts

Designing Calendar Interoperability

Calendar interoperability is typically used only for other Exchange Server organizationsCalendar interoperability is typically used only for other Exchange Server organizations

Options for sharing calendar data:

• Availability service in Exchange Server 2010 or Exchange Server 2007

• Federated Sharing for Exchange Server 2010

• IORepl in Exchange Server 2003

Alternatives to sharing calendar data:

• Mailboxes in both systems

• Shared calendar in SharePoint

Lesson 2: Designing Exchange Server 2010 Integration with Federated Partners

• What Is Federated Sharing?

• Considerations for Designing Federated Trusts and Certificates

• Designing Organization Relationships

• Designing Sharing Policies

What Is Federated Sharing?

Federation sharing allows Exchange Server 2010 organizations to share information such as:

• Availability

• Calendar

• Contacts

Considerations for Designing Federation Trusts and Certificates

Federated sharing requires a federation trustFederated sharing requires a federation trust

Federation trust:

• Is with the Microsoft Federation Gateway

• Is used to communicate with other organizations

• Requires a certificate

• Requires a TXT record in DNS

Certificate requirements:

• From a trusted CA

• SKI field

• Created with CryptoAPI, not Cryptography Next Generation

• RSA signature algorithm

• Exportable private key

Designing Organization Relationships

Organization relationships enable federated sharing with another organizationOrganization relationships enable federated sharing with another organization

• Add an organizational relationship for each organization that you want to share information with

• Specify the free/busy level that is appropriate

• None

• Time only

• Time, subject, and location

• Limit user participation by specifying a security distribution group

• Enable federated delivery to secure messaging

• Simplify configuration by automatically discovering configuration information

Designing Sharing Policies

Sharing policies define how users can share information with other usersSharing policies define how users can share information with other users

Default policy:

• Shares free/busy information only

• Is applied to all mailboxes

• Sharing policies are an alternative to organization relationships

• Select appropriate mailboxes

• Select appropriate domains for the policy

• Select appropriate sharing actions:

• Calendar – free/busy, subject, location, body

• Contacts

Lesson 3: Designing Exchange Server 2010 Integration with Exchange Online

• What Is Exchange Online?

• Designing Coexistence with Exchange Online

• Designing Management of Exchange Online

What Is Exchange Online?

Exchange Online is a hosted version of Exchange Server 2010Exchange Online is a hosted version of Exchange Server 2010

Features:

• Part of Microsoft Online Services

• Access e-mail from anywhere

• 5 GB-25 GB per mailbox

• Supports Outlook, Outlook Web App, Entourage, and Exchange ActiveSync

• Virus and spam filtering

• 99.9 percent uptime SLA

• Can integrate or replace local Exchange server

Designing Coexistence with Exchange Online

• Add your domain to Exchange Online

• Add Autodiscover and SPF records (optional)

• Enable external relay in Exchange Online

• Secure with TLS

• Configure directory synchronization

Designing Management of Exchange Online

You can use the:

• Exchange Management Console to manage Exchange Online

• Administration Center Web site for administration of Exchange Online

Lab: Integrating Exchange Server 2010 with Other Messaging Systems

• Exercise: Designing Exchange Server Coexistence with Another Messaging System

Estimated time: 20 minutes

Lab Scenario

You are a messaging engineer for A. Datum Corporation, an enterprise-level organization with multiple locations. A. Datum Corporation is an international corporation involved in technology research and investment, and has successfully implemented Exchange Server 2010 for messaging and collaboration.

As part of the growth strategy for A. Datum Corporation, your organization has purchased their competitor company, Northwind Traders. You must design the integration of your Exchange Server 2010 organization and the POP3 messaging system of Northwind Traders.

Lab Review

• How does your migration strategy differ for designing coexistence between two Exchange organizations and designing coexistence between Exchange and a non-Exchange organization?

• How is migration to a new messaging system simplified if you do not need the systems to coexist?

Module Review and Takeaways

• Review Questions

• Best Practices

Course Evaluation