Exchange 2016 migration

before migrating mail flow from exchange 2010 to 2016 does outlook connectivity
on clients in local domain should be RPC/HTTP?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ajit SinghCommented:
Get complete overview of client connectivity in an Exchange 2016 coexistence environment with Exchange 2010:

Exchange 2010 to Exchange 2016 migration using Exchange Admin Center:

Hope this helps!
AndyAuthor Commented:
22.pngOutlook anywhere(rpc/http) is enabled on exchange 2010 server
but clients(outlook 2016) connect to exchange via RPC/TCP(outlook connection status)
I need to redirect clients to connect via rpc/http before migrating mail flow?
CESNetwork AdministratorCommented:
You don't need to worry about changing this setting.  Once the mailbox has been moved to the new server, the user will need to restart Outlook and the new connection methos (RPC/HTTP) will be used automatically

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
As soon as you installed Exchange 2016 and right after finishing configuring virtual directories, you should have switched client access to Exchange 2016. The protocol should be either Outlook Anywhere or MAPI which is preferable. All the access to Exchange 2010 will be proxied from Exchange 2016. Outlook Anywhere is enabled by installing a corresponding (probably the same) SSL certificate on Exchange 2016 as you had on 2010. For MAPI - confirm
Get-OrganizationConfig | fl *mapi*

Open in new window

returns True, as well it will require configuration of the corresponding MAPI virtual directory, confirm by
Get-MapiVirtualDirectory | fl server, Name,ExternalURL,InternalURL

Open in new window

That would be MAPI/HTTP, not RPC/HTTP.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.