1. 05 | Planning DNS and Exchange Migration
Anthony Steven | Principal Technologist, Content Master
Martin Coetzer | Portfolio Architect, Microsoft

2. Module Overview
Recommend a Mailbox Migration Strategy

3. Add and Configure Custom Domains
Recommendations for Domain Configuration

4. DNS and Office 365 DNS maps host names to IP addresses and back again
5: Planning DNS and Exchange Migration
DNS maps host names to IP addresses and back again
DNS works on both the Internet and internal networks
Default Office 365 domain is companyname.onmicrosoft.com
Adding a domain like lucernepublishing.com enables:
A mail address of
A SharePoint site at sharepoint.lucernepublishing.com
A SIP domain for Lync Online of sip.lucernepublishing.com
An external web site of
Introduce the importance of DNS for Office 365 but do not labor the basics, as the students should already know it. Do a short PING or telnet demo if you want to.

5. DNS Record Types Type Full Name Function A (IPv4) AAAA (IPv6) Address
5: Planning DNS and Exchange Migration
Type
Full Name
Function
A (IPv4)
AAAA (IPv6)
Address
Maps a host name such as mail.lucernepublishing.com to an IP address, such as
CNAME
Canonical Name
Points one host record, such as ftp.lucernepublishing.com to another host record, such as mail.lucernepublishing.com or even another host record in another domain, such as MX
Mail Exchanger
Points to the host that will receive mail for that domain. NS
Name Server
Delegates a DNS zone to the specified authoritative name server
PTR
Pointer
Points to another record, like a CNAME.
SPF
Sender Policy Framework
SPF provides limited anti-spam services.
SRV
Service locator
Locates hosts that are providing specific services, such as the SIP endpoint in Lync Online
TXT
Text
Records a human-readable text field in DNS
Revise the DNS record types that Office 365 users.

6. Certificate CN= adfs.lucernepublishing.com
Split-Brain DNS
5: Planning DNS and Exchange Migration
lucernepublishing.com zone
A adfs
lucernepublishing.com zone
A adfs
AD FS Server Farm
AD FS Proxy Array
Explain what is happening with the name resolution from the internal and external clients. Point out the fact that the host names and certificate CNs must match. If the students ask why they don’t just use different host names for internal and external access, point out that this makes configuring the calling application more difficult. With split-brain DNS, you just need one host name for authentication from internal and external clients.
Internal DNS
External DNS
Certificate CN= adfs.lucernepublishing.com
Internal User
External User
Internal client request for adfs.lucernepublishing.com returns
External client request for adfs.lucernepublishing.com returns
Authentication mechanism host name: adfs.lucernepublishing.com

7. Planning Custom Domains
5: Planning DNS and Exchange Migration
Additional Root domains
Subdomains
Domain adding order
DNS record hosting
Domain numbers
DNS console access
Not registering DNS
Not changing all records
DNS record propagation
Take the students through the different planning factors that they may need to consider. Make sure they understand the difference between managing records in DNS and registering DNS records with Office 365.
Highlight that typically, they will be adding DNS records to their provider’s records but continuing to manage the records outside Office 365.

8. Process for Adding Domains to Office 365
5: Planning DNS and Exchange Migration
Check ownership of the domain
Check you have access to the DNS console
Check that you can make the required changes to DNS records
Log onto Admin Center in Office 365
Confirm domain ownership in Office 365 by adding an MX or TXT record to DNS
Change the default domain to the new domain
Add users and assign licenses
Set the domain purpose and finish configuring DNS
You might want to demonstrate using who.is to view the records for the contoso.com domain.

9. Generic DNS Verification Procedure
5: Planning DNS and Exchange Migration
Sign in to DNS hoster's web site
Choose option to add DNS record
Add TXT or MX record
Save changes and sign out
In Office 365, click verify now
Highlight that these are the generic steps to verify a domain.

10. Troubleshoot Domain Addition
5: Planning DNS and Exchange Migration
Incorrect DNS records
Replication delays
Domain already registered
Point the students to the URL for more information about troubleshooting domain registration.
DNS Errors

11. Recommendations for Domain Configuration
5: Planning DNS and Exchange Migration
Identify domains to register
Check none are currently registered with Office 365
Check that you can add DNS records to the domain
Complete root domain registration before registering subdomains
Use NSLOOKUP to check DNS entries
Allow for replication
Move on to configuring DNS settings
Document the changes you have made
Cover the recommendations, some of which are recaps of points from previous slides. Highlight the importance of planning and good documentation.

12. Recommend a Mailbox Migration Strategy
Migration Flowchart

13. Mail Migration and Coexistence Overview
5: Planning DNS and Exchange Migration
Migration
Coexistence
On-premises or cloud-based existing system
Cut-over or staged
Cross-premises or hybrid
This is very much an attempt to simplify the explanation and to get the students thinking about the four main options of:
Cutover migration
Staged migration
Cross-premises coexistence
Hybrid coexistence
They can then identify which of these approaches is most appropriate.

14. Migration Options Exchange 3rd Party Tools POP POP3 IMAP PST migration
5: Planning DNS and Exchange Migration
POP3
IMAP
PST migration
3rd Party tools
Simple coexistence
Cutover
Staged
Hybrid
Exchange
3rd Party Tools
POP
Take a while to explain these different options.

15. Cutover Exchange Migration
5: Planning DNS and Exchange Migration
Mailbox access
Certificates
Permissions
Domains
Unified Messaging
Highlight that even with this relatively simple migration type, there are still quite a few planning factors to consider.

16. Staged Exchange Migration
5: Planning DNS and Exchange Migration
Install and configure Directory Synchronization
Plan for user identity management
Configure Outlook Anywhere on the on-premises Exchange server
Install trusted Certificates
Prepare the CSV file
Grant permission to access mailboxes
Add the Exchange organization domain to Office 365
Verify that user mailboxes are not hidden
Disable unified messaging
Remind users that the setup for a staged migration is also the same as for cross-premises coexistence. With cross-premises coexistence, you only migrate a proportion of the users and leave the rest on the on- premises system.

17. Hybrid Exchange Feature Hybrid   Cross-Premises
5: Planning DNS and Exchange Migration
Feature
Cross-Premises
Hybrid
Mail routing between on-premises and online 
Unified global address list
Free/Busy and calendar sharing cross-premise 
Out of Office understands that cross-premises is “internal”
Mail-tips, messaging tracking, and mailbox search cross-premises
Outlook Web App redirection cross-premises (single Outlook Web App URL)
Can route outbound mail through on-premises (allows address rewrite, transport agents)
Secure mail routing (TLS plus Mutual Authentication) cross-premises
Exchange Management Console (on-premises) used to manage cross-premises mailbox migrations
Mailbox moves support for on boarding and off-boarding
No OST re-sync after mailbox migration
Highlight the difference between cross-premises (simple) coexistence and fully hybrid coexistence.

18. IMAP Migration Courier-IMAP Cyrus Dovecot UW-IMAP Exchange 2010
5: Planning DNS and Exchange Migration
Courier-IMAP
Cyrus
Dovecot
UW-IMAP
Exchange 2010
Exchange 2007
Exchange 2003
Exchange 2000
Exchange 5.5
Remind students that IMAP migration is usually for small organizations. However, it is possible to set up cross-premises coexistence with third-party or Exchange-based systems. Typically, IMAP migration with Exchange is something you would probably only want to do with Exchange 2000 or earlier.

19. PST Migration Can be manual process Automated with PST Capture
5: Planning DNS and Exchange Migration
Can be manual process
Automated with PST Capture
Preserves all mailbox information
Works with POP3 accounts
Point out that there are other PST import mechanisms and, in small organizations, the users can do it themselves.

20. Public Folder Migration
5: Planning DNS and Exchange Migration
Role groups
Exchange Online - Organization Management
Exchange Organization Management or Server Management RBAC groups
Exchange Organization Administrator or Server Administrator plus Public Folder Administrator and Local Administrator on target server
Software versions
Windows PowerShell 2.0
WinRM 2.0
Mailbox folder limits
19 GB max in any one public folder
50 public folder mailboxes, upgrade to 100
User mailboxes
Move users first
Connectivity
Outlook Anywhere required
Migration tools
Windows PowerShell scripts only – no GUI tools
Exchange Management Shell
Exchange Online PowerShell
Go through the factors that they need to plan for public folder migration. Remind them that this is a very new feature.

21. Exchange Online Migration Planning Factors
5: Planning DNS and Exchange Migration
Current system
User numbers
Access mechanism
Feature usage
Mail data volume
Internet connection
Emphasize that this deliberately simple approach is designed to provide clarity to the decision-making process and to identify the correct route for your organization without introducing too much detail at this point. Expand the points as follows:
Current system - What system do they currently use?
User numbers - Do they have over or under 2,000 users?
Access mechanism - Over what protocols do users access their ?
Feature usage - What features of the current system do users employ?
Mail data volume - How much mail data is there and how much does a typical user have?
Internet connection - What is the connection speed, latency, and reliability?

22. Email Migration Flowchart
5: Planning DNS and Exchange Migration
Take the students through some of the options and show, for example, how an organization with under 2,000 users, Exchange 2007, and no requirement for long-term coexistence would perform a cutover Exchange migration.
Point the students to the diagram in the content if the project image is too small.

23. Module Review
Recommend a Mailbox Migration Strategy