how to connect outlook 2016 to exchange 2007

Since from exchange 2016 the default connections are mapi/http this command has been depreciated and hence can skip this step. Set-OrganizationConfig -MapiHttpEnabled $true If we could recollect for Exchange 2013 users we need to run this command to enable MAPIHTTP for end users Set-MapiVirtualDirectory -Identity “mapi (Default Web Site)” -InternalUrl -IISAuthenticationMethods Negotiate,NTLM,OAuthīetter to keep the authentication negotiate for the legacy clients till the migration gets completed from Exchange 2010 Run the Command Set-MapiVirtualDirectory and set the external URL of MAPI virtual directory.

Now lets see the steps that we need to do to accomplish this task: So basically the connections will go like the belowįrom internet (RPC/HTTP) – Firewall receives/RPC requests – The request is forwarded to Exchange 2016 CAS services – Connections are proxied back to Exchange 2010 CAS serverįrom Internet (MAPI/HTTP) – Firewall received /MAPI requests – The request is forwarded to Exchange 2016 CAS services – Connections are directed to Exchange 2016 Mailbox server. In-order to accomplish this task you need to make few changes in exchange, firewall as well as DNS side. But from Exchange 2016 Microsoft has totally retired the legacy RPC protocol and wrapped them via MAPI/HTTP through which all the connections will be only via mapi/http. Exchange 2016 users will be getting only MAPI/HTTP connections on their outlook.įrom Exchange 2013 we had an option to choose either RPC/HTTP or MAPI/HTTP.Exchange 2010 users will be getting the RPC/HTTP connections on their outlook.Since the MAPI/HTTP protocol is supported only from the Exchange 2013 with exchange 2016 & Exchange 2010 coexistence the behavior will be : We need to understand this point very clearly. In this article we will have a look at the steps to configure MAPI/HTTP for all users in Exchange 2016 server.

How to connect outlook 2016 to exchange 2007