skype for business save conversation history outlook

This ensures that EWS is not resolved and only MAPI will be used. In this case we populate the Lync users Active Directory “Email” address field with an email address which has a domain name not associated to an Exchange autodiscover service.

The “Email” address field is displayed on the Lync contact card (see workaround here).

Users may be prompted to verify the certificate used by the autodiscover service.

Lync client conversation history will not work, however it will still be stored in Outlook “conversation History” folder.

This does not stop voicemail working, and voicemail messages can still be delivered to your inbox (by way of forward), however to configure voicemail options requires login via OWA.

New Lync Meeting creation from Outlook will work.

EWS and MAPI are connected to your companies Exchange environment.

This would normally be the users actual primary SMTP address. In this case we populate the Lync users AD “Email” address field with an email address which has a domain name matching that of the Exchange autodiscover service in your local Exchange environment. Use EWS provided by an Exchange infrastructure outside where Lync resides

MAPI relies on Outlook being installed and setup with the account you want to integrate with on the computer where you are running Lync.Ģ.

This situation can normally be resolved be signing out and back in again.

Occasionally Exchange integration is slow to establish, or will not establish at all.

There is also a registry key that could be created manually, but I have not tested this (HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0LyncConfAddin). If the problem continues, please contact your support team”**If you temporarily apply option 2 below, create an Outlook Lync Online Meeting then revert back to option 1, it appears this will keep working. Make sure you are signed in to the same account you use for Microsoft Outlook.

New Lync Meeting creation from Outlook will not work, and you will receive the following error message “You cannot schedule the Lync Meeting because you are not UC enabled or there may be issues with your Communications Server account.

Lync client conversation history will work.

Provides a mixture of EWS and MAPI from both Exchange environments.

**When you enable the Lync user account for Exchange and Unified Messaging, this step is not required since the “Email” field will automatically be populated with the default SMTP address. The email address doesn’t necessarily need to be valid. In this case we populate the Lync users AD “Email” address field with an email address which has a domain name matching that of the Exchange autodiscover service in the Lync environment. Use EWS provided by the Exchange infrastructure where Lync also resides If Outlook is not installed, Lync attempts an Exchange autodiscover look-up for the email domain in the AD users “Email” attribute, in the following order:ġ. The Lync client queries Outlook for the connection address for EWS.

EWS is direct from the Lync client to the Exchange Server. The requests are made to Outlook, and then Outlook forwards the request to the mailbox server. You may be prompted for credentials, however generally if Outlook is already open, then MAPI authentication has already occurred.Īccess via MAPI is carried out locally by Lync client integration with Outlook. If EWS cannot be resolved or authentication fails, Lync will still attempt to connect to Outlook using MAPI. If it fails it will not give you the chance to enter different credentials, and as a result EWS authentication will fail. If EWS can be resolved the Lync client will attempt to authenticate using the same credentials it has stored for the Lync client logon, or NTLM authentication for the logged on user. There are 3 options available to Lync to provide Exchange/Outlook integration – Exchange Web Services (EWS), MAPI or a combination of both. I welcome your feedback and own experiences. This article details my experiences, and is by no means definitive, or even true for all circumstances. For example one company might leverage another companies Lync infrastructure, while maintaining there own Exchange infrastructure. Lync and Exchange/Outlook integration can cause a fair bit of frustration, in particular when the Lync and Exchange servers are in different AD forests.

Skype for business save conversation history outlook