Possible After Migration Issue - 2 Questions

Question asked by Doreen Jones - 8/18/2023 at 1:12 PM

Answered

1. I've migrated MS365 EM to my SmarterMail Professional. All DNS records are set and mostly working. I say "mostly" because while the client isn't accessing MS365 - they still have access to the old emails for the short term to pull over anything that got missed off their old server.

Question: Even though DNS is NOT pointing to the old EM in any way - is it possible for the old email MS365 to be causing a conflict or confusion in some cases?

2. After the migration - each user of the account got a System Manager report with a grid of the

number of emails migrated, failed, etc. But no idea WHY some of the emails didn't come over or which ones they were in case I want to go into their old system and check for those emails.

Question: If I migrate again for a specific user - will it duplicate everything? Or should I set up a redundant email box in their account and migrate one more time and compare the two boxes?

I appreciate all help!

7 Replies

Reply to Thread

Andrew Barker Replied

8/21/2023 at 7:26 AM

Employee Post

Microsoft maintains an autodiscover endpoint for all domains they host. Unfortunately, they don't tend to clean up their database when a domain stops using their email service. This can cause some clients, especially Outlook, to continue trying to connect to accounts on M365, even though they are no longer in that system. Here is a knowledgebase article That goes into detail about the situation: Outlook for Windows Always Attempts to Connect to Microsoft 365 (Office).

As for the migration reports, the details of what went wrong should be available in the relevant retrieval log. Since you are migrating from M365, you likely need to review the EWS retrieval log. One of the more common reasons for items to not be migrated has to do with size limits, such as the limits on message and attachment size.

If you want to try migrating a user again, there is the "Delete existing SmarterMail mailbox items" option. This option deletes custom folders and items from the account before beginning the migration. This deletion process is limited to the item types that are being migrated. This can be useful if, for example, you only want to try migrating calendar data again. The user can continue using the other data in their account, while only having the calendar data re-migrated. If this is not a viable option for you, then the redundant email box idea you proposed is a reasonable approach.

Andrew Barker
Lead Software Developer
SmarterTools Inc.
www.smartertools.com

Gabriele Maoret - SERSIS Replied

8/21/2023 at 7:34 AM

Hi Andrew!

In the article "Outlook for Windows Always Attempts to Connect to Microsoft 365 (Office)" there's a precompiled .REG file to download, but it has more entries than those described in the article itself.

Can you please explain those entries?

And possibly update the article properly so that everything is explained correctly?

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS

Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)

Brian Replied

8/21/2023 at 7:48 AM

Marked As Answer

We use a .reg key to make outlook look away from Office365 when migrating them.

I have posted the contents somewhere in here.

Gabriele Maoret - SERSIS Replied

8/21/2023 at 7:55 AM

Hi Brian, is your REG file very different from the one posted in the KB or is it similar?

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS

Brian Replied

8/21/2023 at 8:05 AM

We use this

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover]
"ExcludeExplicitO365Endpoint"=dword:00000001
"ExcludeHttpRedirect"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeScpLookup"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\RedirectServers]
"smartermail.cloudpros.dk"=hex(0):

Andrew Barker Replied

8/21/2023 at 12:07 PM

Employee Post

Just to keep everyone here updated: Derek has responded to Gabriele's comment on the KB article. Essentially, the original registry file included some local-specific URLs and some of our internal testing domains. The registry file currently included in the KB has been updated to remove our testing domains as well as the locale-specific domains.

Andrew Barker
Lead Software Developer
SmarterTools Inc.
www.smartertools.com

Gabriele Maoret - SERSIS Replied

8/21/2023 at 12:21 PM

Thx Andrew!

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS

Back to Community Threads

Reply to Thread

Enter the verification text