Enterprise Vault.cloud™ Lync Connector Administration Guide
- About Lync Connector
- Introduction to Enterprise Vault.cloud Lync Connector
- Changes in Lync Connector version 1.2.2
- Lync Connector release history
- Lync Connector architecture
- The components of Lync Connector
- About Lync Connector synchronizations
- Conference transcript availability options
- About SIP address substitution
- About the format of the archived transcripts
- About the archiving of historical data
- Lync Connector evaluation mode
- About the Lync Connector Console
- Requirements for Lync Connector
- Steps for setting up archiving with Lync Connector
- Installing Lync Connector
- Configuring Lync Connector
- Configuring Lync Connector
- Configuration wizard page 1: Enterprise Vault.cloud credentials
- Configuration wizard page 2: Lync archiving database
- Configuration wizard page 3: Working folder
- Configuration wizard page 4: File management
- Configuration wizard page 5: Active Directory
- Configuration wizard page 6: SMTP
- Configuration wizard page 7: Sender email address
- Configuration wizard page 8: Conference transcript availability
- Configuration wizard: Configuration complete page
- Viewing or changing the credentials of the Lync Connector service account
- Managing archiving with Lync Connector
- Managing SIP address substitution
- Lync Connector workflow
- Lync Connector reports and logged events
- Lync Connector advanced settings
- Troubleshooting Lync Connector issues
- About troubleshooting Lync Connector issues
- Use of Lync 2013 clients with a Lync 2010 server
- Lync archiving database export failure errors
- Synchronization failures
- Transcript processing failures
- SMTP server issues
- Failure reason: "Message size exceeds fixed maximum message size"
- About the Lync Connector trace logs
- Accessing the trace logs
Supported Lync environments
Lync Connector supports archiving from Microsoft Lync Server 2010 and 2013, and Skype for Business Server 2015. For the latest information on the versions that Lync Connector works with, see the Enterprise Vault.cloud Compatibility List.
Note:
A known issue exists with Lync Connector in an environment that uses Lync 2013 clients with a Lync 2010 server.
For the correct functioning of Lync Connector it is essential that the latest Lync Server cumulative update is installed, and that the associated back-end database updates are applied:
For Lync Server 2010, see the following Microsoft knowledge base article: http://support2.microsoft.com/?kbid=2493736
For Lync Server 2013, see the following Microsoft knowledge base article: http://support.microsoft.com/kb/2809243/en-gb
Lync Connector's additional requirements for the Microsoft Lync environment are as follows:
The Lync server must be fully configured to archive to a SQL Server Lync archiving database. Archiving to the database must be enabled in Lync for all of the users whose Lync content you want to archive to Enterprise Vault.cloud.
Most or all of the content in the Lync archiving database should be associated with users who have Enterprise Vault.cloud archive accounts.
Lync Connector is not optimized for environments where only a small subset of the transcripts in the Lync archiving database relates to users with Enterprise Vault.cloud archive accounts. Subject only to a historical date limit, Lync Connector retrieves and processes all of the content from the Lync archiving database.
Lync Connector ignores any transcripts in the database that are marked as purgeable. When Lync Connector extracts a transcript from the Lync archiving database it marks the transcript as purgeable to indicate that the transcript has been obtained. You must ensure that no other applications such as a backup process mark any transcripts in the database as purgeable before Lync Connector has extracted them.
Note:
This restriction is essential for the successful operation of Lync Connector.
You can delete from the Lync archiving database the content that Lync Connector has exported, if you want. The benefit of deleting this content is that the database is maintained at a manageable size, and the Lync Connector takes less time to process it.
Note:
If in the Lync Server's archiving settings you enable the purging of archiving data, consider the option to purge exported archiving data only. Otherwise you may risk the deletion of content from the database before Lync Connector has exported it.