Set-CsConversationHistor圜onfiguration -EnableServerConversationHistory $true -verboseĢ. Test-CsExStorageConnectivity –SipUri -Verboseġ. Verify OAuth setup between Skype for Business and Exchange Verify the configuration for Exchange 2013Ĥ. Verify Exchange Server 2013 is configured to use OAuth with Skype for Business Server 2015.ģ.
Get-CsCertificate -Type OAuthTokenIssuer.Ģ. Verify OAuth is configured on Skype for Business Server
The server-side conversation history make use of LYSS (Lync Storage Services) to process and then store conversation histories directly to Exchange using EWS. So basically when this feature is enabled for desktop clients, the consumer of UCWA is no longer limited to mobile clients. However this time irrespective of the device from where you are having an IM conversation, everything is saved to a centralized location.Īs soon as you enable server side conversation history, the entry point to server-side conversation history from the clients will be UCWA. It was EWS which was responsible for writing the Lync conversation history to Outlook. However Microsoft had gone a step ahead and fixed this component in Skype for Business. In previous versions, it was more like a device based archiving, which means the same conversation cannot be found in the Outlook conversation history and phone. Skype for Business Server side Conversation Historyīack in my Microsoft Support engineer life with Lync 2013 and previous versions, I used to come across a lot of compliance issues, related to missed IM conversation history on mobile devices. Anoop karikuzhiyil babu, EnableServerConversationHistory, Get-CsConversationHistor圜onfiguration, MaxContinuedConversationRetry, Set-CsConversationHistor圜onfiguration, Skype for Business Server side Conversation History
0 kommentar(er)
