September 2010

September 2010
Component
User Identities
Enable and configure multitenant
logic, organizations
Service provisioning and
configuration
Delegation and roles
Multiservice orchestration
Service plans management
Resource Management
Monitoring, reporting, and health
Control Panel
Deployment documentation
HMC 4.5 Exchange Server 2010 SP1
Active Directory Active Directory
MPS Exchange Server 2010
Configure with MPS Configure with Windows
Stored in AD/SQL database PowerShell™
Stored in AD
MPS Exchange Server 2010
MPS Exchange Server 2010 RBAC
MPS Third-party or Hoster solution
MPS Third-party or Hoster solution
MPS Third-party or Hoster solution
MPS + System Center + SQL System Center + third-party or
reporting + third-party solution Hoster solution
Third-party or Hoster solution Third-party or Hoster solution
HMC documentation Product documentation
 Current Migration Activity Future

Exchange Server 2007 Migrate User Mailboxes Exchange Server 2010

Active Directory Active Directory

Migrate User IDs
Identity & Authentication Identity & Authentication

Hosting Third-party Control

Scenario 1 Panel Third-party
(Third-party Upgrade Control Panel
Control Panel
CP) HMC /MPS

Custom Control Third-party

Hosting Option 1: Migrate to third-party CP
Panel Control Panel
Scenario 2 Option 2: Update your control panel:
New AD tenant structure Or
(Custom CP) HMC /MPS Use new Exchange cmdlets Custom Control Panel

Exchange Server Exchange Server

2007 2010
Client Protocol End Point / Namespace
Customers who maintain their own DNS records for IMAP (imap.customer.com) must update DNS
records to point to Exchange 2010. Customers who connect to a generic platform URL
IMAP (imap.hoster.com) will need to update their IMAP client settings to point to Exchange 2010 Servers.*

Customers who maintain their own DNS records for POP (pop.customer.com) must update DNS
records to point to Exchange 2010. Customers who connect to a generic platform URL
POP (pop.hoster.com) will need to update their POP client settings to point to Exchange 2010 Servers.*

Customers must update their MX record to point to Exchange 2010 platform. They must also
SMTP modify their SMTP client settings for outbound SMTP server.

Customers who maintain their own DNS records for OWA (webmail.customer.com) must update
Outlook Web DNS records to point to Exchange 2010. Customers who connect to a generic platform URL
Access (webmail.hoster.com) will need to connect to a new URL for the Exchange 2010 Servers.*

ActiveSync® ActiveSync uses AutoDiscover. Update customer DNS AutoDiscover CNAME records as soon as they
have been migrated to Exchange 2010.
mobile clients

Outlook 2007 and Update customer DNS AutoDiscover CNAME records as soon as they have been migrated to
Exchange Server 2010.
2010
Entourage 2008, Web Services Edition uses AutoDiscover. Update customer DNS autodiscover
Entourage® 2008 CNAME records as soon as they have been migrated to Exchange 2010.
*Exchange Product Group is investigating a coexistence migration scenario in which Exchange 2010 forwards
POP/IMAP/OWA connections back to Exchange 2007 for users who have not had their mailboxes migrated yet.
 © 2010 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, ActiveSync, Entourage, Outlook, Windows, Windows PowerShell, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in
the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. 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 presented after the date of publication. Schedules and features contained in this
document are subject to change.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.
The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization,
product, domain name, e-mail address, logo, person, places, or events is intended or should be inferred.