Outlook client Extranet unreachable through MAPI over HTTP control

Recording

Customer needs, so that some users can no longer use the public network mailbox. Exchange 2013 Environment

Mailbox user-level control via ECP or Exchange PowerShell, including mobile devices, OWA, IMAP, POP3 can be disabled (disabled after both internal and external networks are inaccessible)

The MAPI feature is reserved so that it can be used in the intranet through Outlook, but Outlook anywhere needs to be regulated, with the internal and external network restrictions of MAPI over HTTP, Later through a variety of Google found a parameter mapiblockoutlookexternalconnectivity, you can do Outlook control

650) this.width=650; "title=" clip_image001 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/M02/9D/81/ Wkiol1mbqvvilia4aae4tpztl4y304.png "height=" 236 "/>

Mapiblockoutlookexternalconnectivity parameter Introduction

650) this.width=650; "title=" clip_image002 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M00/9D/81/ Wkiol1mbqvusy6m-aai4lvecmr4949.png "height=" 266 "/>

Mapiblockoutlookexternalconnectivity need to match mapihttpenabled parameters in different scenarios, the effect is different, see the table below.

650) this.width=650; "title=" clip_image003 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image003 "src=" http://s3.51cto.com/wyfs02/M00/9D/81/ Wkiom1mbqvzdg4braajggkluf8k222.png "height=" 647 "/>

Here's how:

Change the settings to the following

650) this.width=650; "title=" clip_image004 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/M01/9D/81/ Wkiom1mbqv6h4fiyaanuneablze391.png "height=" 459 "/>

Intranet test using Normal

650) this.width=650; "title=" clip_image005 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image005 "src=" http://s3.51cto.com/wyfs02/M02/9D/81/ Wkiom1mbqv-zbq-qaafpu7n9iue718.png "height=" 546 "/>

External network configuration Prompt contact is not on the server

650) this.width=650; "title=" clip_image007 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image007 "src=" http://s3.51cto.com/wyfs02/M01/9D/81/wKiom1mBQV_ Wez9haabe5lwznd4166.jpg "height=" 431 "/>

I tested using Outlook 2016 to verify that MAPI over HTTP is not a problem, but this feature is still required for Outlook versions, at least to Outlook SP2

650) this.width=650; "title=" clip_image008 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "border=" 0 "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/M00/9D/81/ Wkiom1mbqwdbeo6aaaniwufh5wk609.png "height=" 555 "/>

This article is from the "Dream Eisenia foetida Heart" blog, please be sure to keep this source http://zmczx.blog.51cto.com/7689019/1952938

Outlook client Extranet unreachable through MAPI over HTTP control