MAPI over HTTP

0

In planning our Exchange upgrade from 2K10 to 2K16 where RPC/HTTP is deprecated in favor of MAPI/HTTP, and now being encrypted over 443, does the Exchange 2016 template account for this?  Our concern is breaking down proxying for clients during coexistence.

2 comments

Avatar
0
Tony Vaughan

Hello,


my understanding is that on exchange 2010 the base version it used MAPI on port 135 and on a later update changed this to MAPI/RPC over HTTPS
I don't believe there will be any issues regarding MAPI and the template but I would recommend opening a support case to make sure nothing is overlooked with the setup

Avatar
0
Tony Price

Thanks, Tony.  I'll do that.