Forum Discussion
MAPI and RPC for Exchange 2016
All,
we are deploying Exchange 2016 iApp and using APM. We will have both 2016 and 2010 useres hitting the iApp but the redirect from 2016 to 2010 will be done through Exchange 2016 not LTMs. As you know 2016 uses MAPI but 2010 uses RPC. on the iApp level we choose "clients use both RPC and MAPI" but on the APM side ( Access Policy -> Application Access -> MS Exchange -> the assigned profile -> Outlook Anywhere, under URL (see attached) we can have either /mapi* or /rpc/rpcproxy.dll but the problem is we need both (mapi for 2016 and rpc for 2010 clients). I added both under URL but seems like just the first one from top takes effect and the other one fails.Do you have any idea how we can have them both at the same time?
- Stanislas_Piro2
Cumulonimbus
Hi,
Starting with TMOS 12.0, mapi is included even if not viewable in exchange profile.
Échange profile uses a hidden irule which includes mapi url.
- Hank_Moody_3649
Nimbostratus
Same Problem here. Still need help
- Viv_Richards
Cirrostratus
Dear
Please confirm what kind of authentication you have used for Outlook Anywhere ? Is it NTLM or kerberos ?
You need to do some changes in exchange side service account which will authenticate ?
Also when you are saying 2016 client and 2010 client, it means Outlook client and not exchange client . Please clarify.
- raydakis10
Cirrus
Hi guys,
i have same issue. outlook anywhere use basic frontend authentication.
i test from microsoft connectivity website.
how can we resolve this issue.
thanks
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com