migrating from hmc to exchange 2010 sp1 hosting
TRANSCRIPT
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 1/20
September 2010September 2010
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 2/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 3/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 4/20
Component HMC 4.5 Exchange Server 2010 SP1User Identities Active Directory Active Directory
Enable and configure multitenantlogic, organizations
MPSConfigure with MPSStored in AD/SQL database
Exchange Server 2010Configure with WindowsPowerShell™ Stored in AD
Service provisioning andconfiguration
MPS Exchange Server 2010
Delegation and roles MPS Exchange Server 2010 RBAC
Multiservice orchestration MPS Third-party or Hoster solution
Service plans management MPS Third-party or Hoster solution
Resource Management MPS Third-party or Hoster solution
Monitoring, reporting, and health MPS + System Center + SQLreporting + third-party solution
System Center + third-party orHoster solution
Control Panel Third-party or Hoster solution Third-party or Hoster solution
Deployment documentation HMC documentation Product documentation
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 5/20
HostingScenario 1(Third-partyCP)
Hosting
Scenario 2(Custom CP)
Exchange Server2007
Exchange Server2010
Third-partyControl Panel
Third-partyControl Panel
Or
Custom Control Panel
HMC /MPS
Third-party ControlPanel
HMC /MPS
Custom ControlPanel
Upgrade Control Panel
Option 1: Migrate to third-party CP
Option 2: Update your control panel:New AD tenant structureUse new Exchange cmdlets
Current Migration Activity Future
Exchange Server 2007
Active DirectoryIdentity & Authentication
Exchange Server 2010
Active DirectoryIdentity & Authentication
Migrate User IDs
Migrate User Mailboxes
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 6/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 7/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 8/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 9/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 10/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 11/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 12/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 13/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 14/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 15/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 16/20
Client Protocol End Point / Namespace IMAP
Customers who maintain their own DNS records for IMAP (imap.customer.com) must update DNSrecords to point to Exchange 2010. Customers who connect to a generic platform URL(imap.hoster.com) will need to update their IMAP client settings to point to Exchange 2010 Servers.*
POP
Customers who maintain their own DNS records for POP (pop.customer.com) must update DNSrecords to point to Exchange 2010. Customers who connect to a generic platform URL(pop.hoster.com) will need to update their POP client settings to point to Exchange 2010 Servers.*
SMTPCustomers must update their MX record to point to Exchange 2010 platform. They must alsomodify their SMTP client settings for outbound SMTP server.
Outlook Web
Access
Customers who maintain their own DNS records for OWA (webmail.customer.com) must updateDNS records to point to Exchange 2010. Customers who connect to a generic platform URL(webmail.hoster.com) will need to connect to a new URL for the Exchange 2010 Servers.*
ActiveSync®
mobile clients
ActiveSync uses AutoDiscover. Update customer DNS AutoDiscover CNAME records as soon as they
have been migrated to Exchange 2010.
Outlook 2007 and
2010
Update customer DNS AutoDiscover CNAME records as soon as they have been migrated toExchange Server 2010.
Entourage® 2008Entourage 2008, Web Services Edition uses AutoDiscover. Update customer DNS autodiscoverCNAME 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.
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 17/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 18/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 19/20
8/7/2019 Migrating from HMC to Exchange 2010 SP1 Hosting
http://slidepdf.com/reader/full/migrating-from-hmc-to-exchange-2010-sp1-hosting 20/20
© 2010 Microsoft Corporation. All rights reserved.Microsoft, Active Directory, ActiveSync, Entourage, Outlook, Windows, Windows PowerShell, Windows Server, and W indows 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 i nformation presented after the date of publication. Schedules and features contained in thisdocument 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.