

The features you will not get when forcing MAPI, include: Well aware of the loss of functionality when forcing MAPI, I have found this a lot better than no functionality at all. And after a lot of research and quite a few emails with Microsoft support, I have finally been able to “trick” the Lync client to use MAPI. I’ve been looking far and wide for a way to force the client to use MAPI instead EWS in these scenarios. (While if EWS is not available, and MAPI is chosen you will get prompted for credentials if logon fails).

And it will not fall back to MAPI, as it sees the EWS as up and running. It will not prompt you for correct credentials if EWS authentication fails. As it turns out, when the Lync client tries to access EWS it uses the same credentials it has stored for the Lync client logon. The 3rd scenario is (in my experience) the most common scenario, and renders the Lync client without any integration at all. The two first scenarios are not too common, but would give most of the functionality for the user (The user might be prompted once for logon with MAPI credentials. If the customer has deployed EWS and it is reachable by the Lync client, the authentication fails and MAPI is not used.
#LYNC FOR MAC 2011 CONVERSATION HISTORY INSTALL#
To increase/decrease the time to auto-accept on the Mac client from the default 5 minutes, follow either of these steps:Ĭreate a configuration profile with the appropriate key and value and install it on a managed Mac. This helps ensure the sender does not get the following error: “We couldn't send this message.” After 5 minutes of any activity, the Mac client does not auto-accept the messages to ensure mobile endpoints are able to accept incoming messages as necessary. If server-side conversation history is turned off in your organization, by default, the Skype for Business on Mac client will auto-accept incoming messages if the message arrives within 5 minutes of the Mac client being active.

Admin: How do you increase the auto-accept period on Mac client?
