[Troubleshooting Case] migrate to Office 365 Outlook can not open

After the initial success of creating a profile, from the support IMAP and SMTP Web-based e-mail system migration, some users may experience problems start of Outlook. Such as DNS setup issues https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view= o365-worldwide

Because Outlook 2016 enables direct connection method, so after the initial installation profile, Outlook does not start.

However, if you manually create a new profile, you might see when creating these messages.

Error # 1:

When you start Outlook after connecting users to Office 365 mailbox configuration file, it generates an error message:

Outlook can not log on. Verify that you are connected to the network and use the proper server and mailbox name. Microsoft Exchange information services in your profile is missing information required. Modify the configuration file to make sure you use the correct Microsoft Exchange service.

Error # 2:

Serious shortage of system resources. close the window.

Error # 3:

Can not start Microsoft Outlook. Unable to open the Outlook window, set of folders could not be opened. Information Store could not be opened.

In the run support and Recovery Assistant Office 365 when, it will detect the following information (log located in% USERPROFILE% \ appdata \ local \ SaRAresults "):

Because DNS server settings contain CNAME and SRV records, there has been a problem Outlook. To resolve this issue, Office 365 administrators to change the DNS settings.

Remove the domain SRV record "_autodiscover._tcp.o365 domain .net". This SRV record and CNAME record exists, Outlook starts to block or load the user's profile

We use the following method to retrieve user settings (Auto Discovery): HttpsRootdomain

In addition, XML documents show that the non-Office 365 mailbox settings information:

To resolve this issue single client, we need to add the following entry in the user registry to prevent Outlook tries to connect to an invalid e-mail service, and to prevent erroneous update user profile, the new profile folder to re-create the user profile.

Step 1: Use ExcludeLastKnownGoodUrl, HTTPSEXCLUDEROOTDOMAIN and ExcludeSrvRecord Outlook client to try to prevent a mailbox on the mail service before connecting the user to.

Configure the following registry subkey:

HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ x.0 \ Outlook \ Autodiscover

DWORD：ExcludeLastKnownGoodUrl

Value：1HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ x.0 \ Outlook \ Autodiscover

DWORD：EXCLUDEHTTPSROOTDOMAIN

Value：1HKEY_CURRENT_USER \ Software \ Microsoft \ Office \ x.0 \ Outlook \ Autodiscover

DWORD：ExcludeSrvRecord

Value：1

 

Step 2: Rename, backup, or delete the "% USERPROFILE% \ appdata \ local \ microsoft \ outlook" folder

Step 3: Re-establish user profiles

If the administrator or the right to modify DNS tenants, follow the instructions to support and assist the recovery, remove the DNS has cited IMAP and SMTP services, including only the necessary records to allow users to connect to the new Office 365 mailboxes.

In most deployments, simply autodiscover.outlook.com CNAME record can connect users to Office 365 mailboxes.

extra information:

After Office 365 can not create a new Outlook profile, or migrate to office 365, outlook can not connect problem

https://support.microsoft.com/en-us/help/3049615/you-can-t-create-new-outlook-profiles-view-free-busy-information-or-co