Enabling and disabling MAPI and/or non-Cached access per user in Exchange 2003 SP2

Enabling and disabling MAPI access

Exchange Security — Wed, 27 Jul 2005 22:42:32 GMT

<p>
In related news, the Exchange team blog has a great post today explaining how Exchange 2003 SP2 gives us the ability to block individual users from using MAPI. The good news: because the MAPI blocking is added to the existing ProtocolSettings mechanism for blocking other protocols, you can use the same script to block or allow multiple protocols at once.
</p>

Habilitando y deshabilitando acceso MAPI por usuario en Exchange 2003 SP2

Exchange Blog Latino — Thu, 28 Jul 2005 00:17:41 GMT

Turn on MAPI on Exchange, good news for hosters, but....

Marcus Hass' Blog — Thu, 28 Jul 2005 00:50:07 GMT

I just saw this post from the Exchange team.&nbsp; This is great news for hosters that want to offer...

Turn off MAPI on Exchange, good news for hosters, but....

Marcus Hass' Blog — Thu, 28 Jul 2005 01:02:47 GMT

I just saw this post from the Exchange team.&nbsp; This is great news for hosters that want to offer...

And what 'bout cached clients

Radovan Vojtek — Thu, 28 Jul 2005 09:25:03 GMT

Hi, is there any possibility to block cached-mode clients? Blocking noncached clients could be good, however I'd appreciate the ability to block cached-mode outlook (security reason, etc.) Is there any way to block it? (yeah, I could set up an "DisableCacheMode" Group Policy, but what 'bout non-domain users?

Thanx,
R.V.

Exchange 2003 SP2 controlling MAPI Access

ExchangeIS — Fri, 29 Jul 2005 04:53:01 GMT

Exchange 2003 SP2 will implement a new feature where by an administrator can control MAPI access to the...

Toggling Client MAPI Access to Exchange 2003 SP2

Doug's Weblog — Fri, 29 Jul 2005 07:26:12 GMT

There's an interesting new feature in Exchange 2003 as of SP2 that the Exchange Team&nbsp;posted about...

Toggeling Client MAPI Access to Exchange 2003 SP2

Doug's Weblog — Fri, 29 Jul 2005 07:28:10 GMT

There's an interesting new feature in Exchange 2003 as of SP2 that the Exchange Team&nbsp;posted about...

Weekend reading

subject: exchange — Fri, 29 Jul 2005 09:58:16 GMT

Weekend reading

subject: exchange — Fri, 29 Jul 2005 09:59:16 GMT

Weekend reading

subject: exchange — Fri, 29 Jul 2005 10:42:02 GMT

Windows, XP, Exchange, ISA, SMS, IE, Security, LCS, Misc.

Windows Server Clustering — Mon, 01 Aug 2005 21:03:20 GMT

re: Enabling and disabling MAPI and/or non-Cached access per user in Exchange 2003 SP2

Alex — Wed, 03 Aug 2005 04:33:08 GMT

Will there ever be support to require encrypted sessions? Right now, the CLIENT checks a box in their outlook profile to "Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server." It seems like this no-brainer setting should be an option the server can require. Why can't we?

re: Enabling and disabling MAPI and/or non-Cached access per user in Exchange 2003 SP2

Frank Carius — Mon, 22 Aug 2005 16:09:47 GMT

Great stuff and thank you for that early information, how to disable MAPI per user.
Unfortunaly the Exchange 2003 SP2 CTP does not expose that settings in the GUI.
And on the other side it's not really a fun to maintain hundreds or thousand of users manually. And i have not found a way to control access by group member ships. So i have written a small VBScript earlier to set the POP3, IMAP4, OWA, OMA-Permissions using security groups.
I have added the MAPI-Properties with the current version. So i have to create group to allow POP3, IMAP4, OMA, OWA and to disallow MAPI and to enforce "cached mode". and start that vbscript once a day.

Unfortunaly the web page itself is german.So use google to translate. But VBscript is "universal" :-)

http://www.msxfaq.de/tools/grp2exinet.htm

FYI: ProtocolSettings and MAPI client restrictions affect MAPI and CDO 1.21

The CDOs and CDONTS of Messaging Development — Tue, 02 May 2006 00:06:47 GMT

There are several options for configuring restrictions on MAPI client access to Exchange 2003 SP 2. ...