guideflow.blogg.se - Lync for mac 2011 conversation history

#LYNC FOR MAC 2011 CONVERSATION HISTORY INSTALL#

Write contacts (on demand) (EWS and Exchange Server 2010 SP1 only).

Handle missed Conversation notifications.

Read Out ofCreate the Conversation History folder.

Read or delete Conversation History itemsīut the clients will still be able to do the following:.

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.

If the customer has deployed EWS but the EWS is unreachable, the client defaults to MAPI.

Except for some missing features (I will get back to), “all” is well.

If the customer has not deployed EWS, the Lync client will not find any EWS and default to MAPI.

Or if you also host Exchange services (in the same forest) for the customer, you should not run into any issues.īut, if for some reason you cannot set up the Lync forest as a resource forest for the customer/user, and you do not host the customers Exchange as described, you might run into some challenges with the Exchange integration. I have personally run into these scenarios a couple of times, and have been faced the following client side challenges: “All” you have to do, is to follow the following for the users in the separate forest. If you can set up a trust and federation between the two forests, then all is well. Key: autoAcceptTimeout | Type: Number | Value: The timeout value in seconds.Ĭhange value using defaults terminal application:Ĭhange the key using defaults: 'defaults write autoAcceptTimeout 360'.There are certain scenarios where I would like to provide Lync for users who belong to a different forest than the Lync installation is in. Creating and installing configuration profiles is out of the scope of these steps see Configuration Profile Reference.

#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?