Outlook 2016 Disconnected, after migration Mailbox from Exchange 2010 DB to Exchange 2106 DB
I have install a new Exchange 2016 to migrate from Exchange 2010 SP3. I have a problem is that when I migrate the Mailbox from Exchange 2010 DB to Exhange 2010 DB, the Outlook will be disconnected and the customer cann't use Outlook.
When I migaret back the mailbox to the Exchange 2010, the Outllook will connect and the customer can use it to send and receive email.
Thanks
When I migaret back the mailbox to the Exchange 2010, the Outllook will connect and the customer can use it to send and receive email.
Thanks
Last Comment
Hi,
when doing this kind of migration, you must have switched the front (CAS) used by clients to be only Exchange 2016 servers.
Exchange 2016 CAS can redirect or proxify access to Exchange 2010, but Exchange 2010 cannot do the reverse.
If you don't switch or cannot switch, you can test the connection modifying the "hosts" file on the workstation, to have the resolution pointing to your Exchange 2016 server.
Look at the part 1 : Exchange 2010 to Exchange 2016 Migration, Exchange Server 2010, Exchange Server 2016 (msexperttalk.com)
And the part 4 : EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION, Exchange 2010 Server, Exchange 2016 Server Upgrade (msexperttalk.com)
When the switchover has been done with success, Outlook can be configured correctly after move.
when doing this kind of migration, you must have switched the front (CAS) used by clients to be only Exchange 2016 servers.
Exchange 2016 CAS can redirect or proxify access to Exchange 2010, but Exchange 2010 cannot do the reverse.
If you don't switch or cannot switch, you can test the connection modifying the "hosts" file on the workstation, to have the resolution pointing to your Exchange 2016 server.
Look at the part 1 : Exchange 2010 to Exchange 2016 Migration, Exchange Server 2010, Exchange Server 2016 (msexperttalk.com)
And the part 4 : EXCHANGE 2010 TO EXCHANGE 2016 MIGRATION, Exchange 2010 Server, Exchange 2016 Server Upgrade (msexperttalk.com)
When the switchover has been done with success, Outlook can be configured correctly after move.
ASKER
Hello
I have used this tuto to make the migration. From the workstation, I can resolve autodiscover.mydomain.com to the new EX16, can ping it .
When I have make the migration and Outlook open, I have received the message to close and open Outlook. but After restart it statys disconnected.
I have used this tuto to make the migration. From the workstation, I can resolve autodiscover.mydomain.com to the new EX16, can ping it .
When I have make the migration and Outlook open, I have received the message to close and open Outlook. but After restart it statys disconnected.
It can be some time (half hour max) before DCs/Exchange are up to date.
ASKER
I have make the mirgation since 4 days. It seems that the Outlook always points to EX10 ?
ASKER
Autodiscover and the access to the messaging system ("mail.domain.extension" ?) should both point to Exchange 2016 server.
Is it the case?
Is it the case?
ASKER
they both point to the Exchange Server 2016
Outlook Anywhere is well configured on Exchange 2010 ?
How have you configured/Modified authentication on Exchange 2010 ?
Configure Exchange 2016 with Exchange 2010 coexistence - TechNet Articles - United States (English) - TechNet Wiki (microsoft.com)
How have you configured/Modified authentication on Exchange 2010 ?
Configure Exchange 2016 with Exchange 2010 coexistence - TechNet Articles - United States (English) - TechNet Wiki (microsoft.com)
Hello,
I would assume your autodiscover URL points to the EX2016 CAS.
As autodiscover just publishes the configuration, even a correct autodiscover URL means, that the client gets the correct settings. So I would check on the old as well as the new clients, what autodiscover delivers.
As the procedures are a bit different between Outlook 2010 and 2016 its possible to forgot to change a setting or the settings were never complete...
If you CTRL right click onto the Outlook tray icon, you see extended items, you can test autodicover from there to see, what the client gets.
I would assume your autodiscover URL points to the EX2016 CAS.
As autodiscover just publishes the configuration, even a correct autodiscover URL means, that the client gets the correct settings. So I would check on the old as well as the new clients, what autodiscover delivers.
As the procedures are a bit different between Outlook 2010 and 2016 its possible to forgot to change a setting or the settings were never complete...
If you CTRL right click onto the Outlook tray icon, you see extended items, you can test autodicover from there to see, what the client gets.
ASKER
Hello
I have'nt moddify the configuration of the authentication on the exchange 2010.I can share with you some screenshoot from outlook
I have'nt moddify the configuration of the authentication on the exchange 2010.I can share with you some screenshoot from outlook
The 2016 acts as proxy for the 2010