SOLVED
Home

MapiHttpEnabled = False

%3CLINGO-SUB%20id%3D%22lingo-sub-307092%22%20slang%3D%22en-US%22%3EMapiHttpEnabled%20%3D%20False%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307092%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20collecting%20some%20information%20for%20an%20unrelated%20bug%20we've%20found%2C%20and%20my%20eye%20happened%20to%20catch%20that%26nbsp%3B%3CFONT%3EMapiHttpEnabled%3C%2FFONT%3E%20was%20set%20to%20False%20for%20our%20org.%3C%2FP%3E%3CP%3EI%20was%20surprised%20to%20see%20that%20we%20were%20set%20this%20way%20since%20this%20protocol%20was%20launched%20eons%20ago%20and%20it%20%22%3CSPAN%3EMAPI%20over%20HTTP%20improves%20the%20reliability%20and%20stability%20of%20the%20Outlook%20and%20Exchange%20connections%3C%2FSPAN%3E%22.%3C%2FP%3E%3CP%3EAfter%20reading%20the%20online%20docs%20a%20little%20further%2C%20I%20can%20see%20how%20companies%20with%20legacy%20Exchange%20may%20have%20ended%20up%20in%20this%20state.%26nbsp%3B%20But%20my%20question%20is%20-%20does%20anyone%20know%20if%20MapiEnabled%20%3D%20True%20for%20each%20new%20mailbox%20created%20as%20the%20default%3F%3C%2FP%3E%3CP%3EAt%20some%20point%20I'll%20run%20a%20script%20to%20look%20at%20all%20of%20our%20mailboxes%20to%20see%20if%20any%20of%20them%20have%20it%20disabled%20-%20but%20for%20now%20I%20was%20hoping%20someone%20here%20may%20know%20if%20enabling%20this%20at%20the%20mailbox%20level%20was%20really%20what%20MS%20intended%20versus%20at%20the%20tenant.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-307092%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMapiHttpEnabled%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307143%22%20slang%3D%22en-US%22%3ERe%3A%20MapiHttpEnabled%20%3D%20False%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307143%22%20slang%3D%22en-US%22%3EOK%20thanks....wanted%20to%20make%20sure!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-307098%22%20slang%3D%22en-US%22%3ERe%3A%20MapiHttpEnabled%20%3D%20False%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307098%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20are%20referring%20to%20the%20output%20of%20Get-OrganizationConfig%2C%20you%20can%20ignore%20it.%20The%20value%20simply%20doesn't%20matter%20in%20ExO.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Adrian Hyde
Regular Contributor

I've been collecting some information for an unrelated bug we've found, and my eye happened to catch that MapiHttpEnabled was set to False for our org.

I was surprised to see that we were set this way since this protocol was launched eons ago and it "MAPI over HTTP improves the reliability and stability of the Outlook and Exchange connections".

After reading the online docs a little further, I can see how companies with legacy Exchange may have ended up in this state.  But my question is - does anyone know if MapiEnabled = True for each new mailbox created as the default?

At some point I'll run a script to look at all of our mailboxes to see if any of them have it disabled - but for now I was hoping someone here may know if enabling this at the mailbox level was really what MS intended versus at the tenant.

2 Replies
Solution

If you are referring to the output of Get-OrganizationConfig, you can ignore it. The value simply doesn't matter in ExO.

OK thanks....wanted to make sure!