This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 76%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hello,
I migrated all mailboxes from my Exchange 2016 to Exchange 2019 (last CU). I haven't migrated the network stream yet. everything points to Exchange 2016.
Not one Outlook 2016 had the prompt "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"
yet, I had no error during the migration of the boxes.
when opening Outlook 2016 is connected.
Yet when I migrated from Exchange 2010 to Exchange 2016 I got the prompt.
"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook".
Has anyone encountered this problem before?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hi anonymous user-8364
Is suggestion below helpful to your question? And do you have any concern now?
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Not a problem, but expected.
When you moved the mailboxes from 2010 to 2016, you were changing how Outlook connects to the Exchange Server (2010 MAPI/RPC to 2016 MAPI over HTTP )
When the mailbox was moved, Outlook prompted to restart so it could use the new endpoint and protocol.
When you moved from 2016 to 2019, the Outlook clients used the same protocols to connect to Exchange, so no restart needed.
This breaks down the diff protocols by version
ok thank you AndyDavid for your answer.
It seems to me that (I'll tell you again in 2 weeks when the project resumes at my client) but when I do get-organizationconfig mapi is: false
but in the documentation I see that it is necessarily enable starting from a 2010 is that right?
screenshot outlook connectivity:
