1. Microsoft Virtual Academy Dean Yamada | Senior Premier Field Engineer, Microsoft Stephen Hall | Cloud Solutions Specialist, District Computers

2. Course Topics Solving Office 365 Client Deployment Scenarios 01 | System Center Configuration Manager (SCCM) Deployment Best Practices 02 | Multi-language Deployment Considerations for Office 365 ProPlus 03 | Office 365 ProPlus with Azure Rights Management Services for IRM/Encryption 04 | Controlling access to Office 365 ProPlus & Services 05 | Troubleshooting Office 365 and Exchange Migration Common Gotchas 06 | New Office 365 ProPlus Customizations via Group Policy or XML 07 | New Updating and Repair Command-Line Options for Office 365 ProPlus

3. Microsoft Virtual Academy Module 5: Troubleshooting Office 365 and Exchange Migration Common Gotchas Dean Yamada | Senior Premier Field Engineer, Microsoft Stephen Hall | Cloud Solutions Specialist, District Computers

4. Solving Exchange Autodiscover service problems following an Exchange cutover migration Troubleshooting Outlook profile connectivity problems when using Office 365 mailboxes Fixing the Outlook Auto-Complete entry problem following an Exchange cutover migration Module Overview

5. Solving Exchange Autodiscover service problems following an Exchange cutover migration

6. The importance of Autodiscover with Office 365 Microsoft supports using Autodiscover to create Outlook profiles for Office 365 Microsoft doesn't support manually setting up a profile in Outlook for connectivity to mailboxes in Exchange Online in Office 365

7. Verify proper operation of Exchange Autodiscover Verify the proper DNS CNAME record is set in DNS Use Microsoft Remote Connectivity Analyzer https://www.testconnectivity.microsoft.com/?testid=O365EasAutoDiscover

8. Your users cannot automatically setup Outlook profiles on their domain-joined computers using their Office 365 mailboxes –Users profiles are automatically created using their legacy mailboxes on the domain Exchange server NOT their active Office 365 Exchange Online mailboxes –Users would need to know how to manually create their Office 365 Outlook profile, but that is not supported –The default Autodiscover behavior MUST be modified Scenario

9. Outlook IS behaving properly A valid Exchange Server is on the domain, so there is a Service Connection Point (SCP) for that Exchange Server in AD The SCP is the Exchange Server with the CAS role The SCP is the first place Outlook looks for the user’s mailbox Outlook “sees” the users mailbox on the domain Exchange server and configures the profile with the legacy mailbox

10. Three phases of the Autodiscover process

11. Outlook’s methods to locate Autodiscover service Last known good URLOutlook uses the last known good AutoDiscover URL SCP lookupOutlook performs Active Directory queries for Service Connection Point (SCP) objects that have AutoDiscover information. HTTPS root domain query Outlook uses the root domain of your primary SMTP address to try to locate the AutoDiscover service. Outlook tries to connect to the following URL: https://autodiscover. /autodiscover/autodiscover.xml HTTPS AutoDiscover domain query Outlook uses the AutoDiscover domain to try to locate the AutoDiscover service. Outlook tries to connect to: https://autodiscover. /autodiscover/autodiscover.xml HTTP redirect method Outlook uses HTTP redirection if Outlook cannot reach the AutoDiscover service through either of the secure HTTPS URLS: https:// /autodiscover/autodiscover.xml https://autodiscover. /autodiscover/autodiscover.xml SRV record query Outlook uses an SRV record lookup in DNS to try to locate the AutoDiscover service

12. Fix the “problem” without modifying Exchange or AD What to do –Enable ONLY the HTTP redirect method to locate Autodiscover service thru DNS (use the autodiscover CNAME DNS records created for Exchange Online) –Disable all other Outlook Autodiscover location methods How to do it –Edit the registry manually on each PC –Create a registry file and import it on each PC –Use Group Policy to change settings on all PC

13. Change Outlook AutoDiscover manually in registry Open Registry Editor (regedit.exe) Browse to or create the following registry key HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\AutoDiscover Create or set the following registry DWORD VALUES: NameTypeValue (Hex) ExcludeScpLookupREG_DWORD0 ExcludeHttpsAutoDiscoverDomainREG_DWORD1 ExcludeHttpsRootDomainREG_DWORD1 ExcludeScpLookupREG_DWORD1 ExcludeSrvRecordREG_DWORD1

14. Create a registry file to change Outlook AutoDiscover Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\AutoDiscover] "ExcludeScpLookup"=dword:00000001 "ExcludeHttpsRootDomain"=dword:00000001 "ExcludeHttpsAutoDiscoverDomain"=dword:00000001 "ExcludeHttpRedirect"=dword:00000000 "ExcludeSrvRecord"=dword:00000001

15. Change Outlook AutoDiscover in Group Policy

16. CREATING A REGISTRY FILE TO SET THE OUTLOOK AUTODISCOVER SETTINGS ON A SINGLE PC demo

17. Additional Resources http://technet.microsoft.com/en- us/library/cc179176(v=office.15).aspxhttp://technet.microsoft.com/en- us/library/cc179176(v=office.15).aspx http://technet.microsoft.com/en- us/library/bb124251(v=exchg.150).aspxhttp://technet.microsoft.com/en- us/library/bb124251(v=exchg.150).aspx http://msdn.microsoft.com/en- us/library/office/jj900169(v=exchg.150).aspxhttp://msdn.microsoft.com/en- us/library/office/jj900169(v=exchg.150).aspx http://msdn.microsoft.com/en- us/library/office/dn467395(v=exchg.150).aspxhttp://msdn.microsoft.com/en- us/library/office/dn467395(v=exchg.150).aspx

18. Troubleshooting Outlook profile connectivity problems when using Office 365 mailboxes

19. A Common Outlook Connectivity Problem When creating Outlook profiles or connecting to an Office 365 mailbox, you are continually prompted for credentials while the client displays "trying to connect..." –If you cancel the credentials prompt, you receive the following error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action How to troubleshoot this: –Verify the server name and username are correct for the mail account –Verify Anonymous Authentication is configured for the mail account

20. Outlook Mail Account Exchange Server Settings

21. Identifying a User’s Unique Server Name The server is the user’s unique ExchangeGUID followed by “@” and the users domain name –Example: Steve’s GUID is “p754367n-r356-6692-xt82-l2k53246qv78” Steve’s domain is “contoso.com” Steve’s Exchange Server Name would be: p754367n-r356-6692-xt82-l2k53246qv78@contoso.com

22. Gathering a User’s ExchangeGUID Use Microsoft Remote Connectivity Analyzer User PowerShell

23. How to Gather ExchangeGUID using the Microsoft Remote Connectivity Analyzer

25. Expand All Find

26. Copy the entire MailboxID value... https://outlook.office365.com/mapi/emsmdb/?MailboxId=p 754367n-r356-6692-xt82-l2k53246qv78@contoso.com......

27. COLLECTING USERS’ EXCHANGEGUID FROM THE MICROSOFT REMOTE CONNECTIVITY ANALYZER demo

28. How to Gather ExchangeGUID via PowerShell Get a single ExchangeGUID Get-Mailbox | select ExchangeGUID Get all users ExchangeGUID Get-Mailbox | select DisplayName, ExchangeGUID |export-csv c:\exchangeinfo.csv

29. COLLECTING USERS’ EXCHANGEGUID WITH POWERSHELL demo

30. Verify Anonymous Authentication for the mail account in Outlook

31. Additional Resources https://testconnectivity.microsoft.com http://community.office365.com/en-us/f/148/t/203053.aspx http://support.microsoft.com/kb/2984912

32. Fixing the Outlook Auto- Complete entry problem following an Exchange cutover migration

33. About Outlook Auto-complete The Auto-Complete List is a feature which displays suggestions for names and e-mail addresses as you begin to type them These suggestions are possible matches from a list of names and e-mail addresses from the e-mail messages previously have sent

34. You recently cutover from your Exchange server to Office 365 Your users are getting bounces when sending messages to internal users from their Auto-complete entries in Outlook. Scenario Overview

35. What’s The Problem? Your senders that send messages to internal users from Outlook auto-complete entries receive an IMCEAEX non- delivery report (NDR) because of a bad LegacyExchangeDN reference. –The IMCEAEX NDR indicates that the user no longer exists in the environment. The recipient's smtp email address is the same, but other internal identifiers for the recipient have changed Users’ preserved Outlook auto-complete entries for internal users don’t work anymore

36. Non-Deliverable Report (NDR) Message Content Delivery has failed to these recipients or groups: User Name(user@contoso.com) User Name(user@contoso.com) The email address you specified couldn't be found or is invalid. It may be due to a bad entry in your Outlook or Outlook Web App recipient AutoComplete cache. Use the steps below to delete the entry from the cache: 1.Click New mail. 2.In the To field start typing the recipient's name or email address until the recipient appears in the drop- down list. 3.Use the DOWN ARROW and UP ARROW keys to select the recipient, and then press the DELETE key. Then resend your message – delete and retype the recipient’s name or e-mail address before sending it. For more tips on how to resolve this issue see DSN 5.1.x Errors in Exchange Online and Office 365.DSN 5.1.x Errors in Exchange Online and Office 365 Diagnostic information for administrators: Generating server: CO1PR06MB032.namprd06.prod.outlook.com IMCEAEX- _o=OEXCH030_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipi ents_cn=user+40Contoso21@namprd06.prod.outlook.com Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'

37. How to Fix the Problem Clear the auto-complete cache file for each user –Note The procedure has to be performed by each user individually OR Modify each user’s auto-complete or NK2 (if legacy) file –Change the all of the email entries to valid SMTP email addresses NOTE – this can be tedious and may require third party tools OR Add the failing “bad address” as an alternate (proxy) address to the user's EmailAddresses in Exchange Online

38. Collect the failing address from the NDR Message Review the NDR to analyze the address to which the users are trying to send email messages. The address will be similar in format to the following: IMCEAEX- _O=MMS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+2 8FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=user1@xxx00.pro d.outlook.com Note This format indicates that the legacyExchangeDN attribute is translated by Exchange to an SMTP address.

39. Translate the address into the legacyExchangeDN format Remove IMCEAEX- Remove @_____.prod.outlook.com Replace any underscore (_) with a forward slash (/) Replace +20 with a blank space Replace +28 with an opening parenthesis Replace +29 with a closing parenthesis “Bad Address” (from NDR) IMCEAEX- _O=MMS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIE NTS_CN=user1@xxx00.prod.outlook.com Translated legacyExchangeDN /O=MMS/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS_CN=user1

40. Add the LegacyExchangeDN as an X500 Address to the user’s Email Addresses in Exchange Online

41. CREATING AN X500 EMAIL ADDRESS FROM AN INVALID EMAIL ADDRESS FROM ANOTHER EXCHANGE ENVIRONMENT IN OFFICE 365 demo

42. Additional Resources http://support.microsoft.com/kb/2807779 http://technet.microsoft.com/en- us/library/dn479208(v=exchg.150).aspxhttp://technet.microsoft.com/en- us/library/dn479208(v=exchg.150).aspx http://support.microsoft.com/kb/2005644/EN-US https://support.office.com/en-ie/article/The-Auto-Complete-list-doesn- t-remember-names-or-email-addresses-19ba9a7d-e37a-4220-97c1- 40499bc2f357https://support.office.com/en-ie/article/The-Auto-Complete-list-doesn- t-remember-names-or-email-addresses-19ba9a7d-e37a-4220-97c1- 40499bc2f357 https://support.office.com/en-us/article/Import-AutoComplete-List- from-another-computer-3092ee65-be1b-4d18-b903-4bb84c9932d0https://support.office.com/en-us/article/Import-AutoComplete-List- from-another-computer-3092ee65-be1b-4d18-b903-4bb84c9932d0

43. ©2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. 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 provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.