Deployment checklist for Archiving in Lync Server 2013
Topic Last Modified: 2012-10-18
Archiving is automatically installed on each Front End Server in your Lync Server 2013 deployment, but you still need to set it up before you can use it. The steps required to set it up, as summarized in this section, constitute the deployment of Archiving.
Deployment Sequence
How you set up Archiving depends on which storage option you choose:
If you use Microsoft Exchange integration for all users in your deployment, you don’t need to configure Lync Server 2013 Archiving policies for your users. Instead, configure your Exchange In-Place Hold policies to support archiving for users homed on Exchange 2013, with their mailboxes put on In-Place Hold. For details about configuring these policies, see the Exchange 2013 product documentation.
If you do not use Microsoft Exchange integration for all users in your deployment, you need to add Lync Server Archiving databases (SQL Server databases) to your topology and then publish it, as well as configure policies and settings for your users, before you can archive data for those users. You can deploy Archiving databases at the same time that you deploy your initial topology or after you have deployed at least one Front End pool or Standard Edition server. This document describes how to deploy Archiving databases by adding them to an existing deployment.
If you enable archiving in one Front End pool or Standard Edition server, you should enable it for all other Front End pools and Standard Edition servers in your deployment. This is because users whose communications are required to be archived can be invited to a group IM conversation or meetings hosted on a different pool. If archiving is not enabled on the pool where the conversation or meeting is hosted, the complete session may not be archived. In these cases, IMs with archiving-enabled users still can be archived, but not for conferencing content files, and conference join or leave events.
Important
If archiving is critical in your organization for compliance reasons, be sure to deploy Archiving, configure policies and other options at the appropriate level, and enable it for all appropriate users, before you enable those users for Lync Server 2013.
Archiving Deployment Process
The following table provides an overview of the steps required to deploy archiving in an existing topology.
| Phase | Steps | Roles and group memberships | Documentation |
|---|---|---|---|
Install prerequisite hardware and software |
Note Archiving runs on Front End Servers of an Enterprise pool and Standard Edition servers. It has no additional hardware or software requirements beyond what is required to install those servers. |
Domain user who is a member of the local administrators group. |
Supported hardware for Lync Server 2013 in the Supportability documentation. Server software and infrastructure support in Lync Server 2013 in the Supportability documentation. Technical requirements for Archiving in Lync Server 2013 in the Planning documentation. Setting up systems and infrastructure for Archiving in Lync Server 2013 in the Deployment documentation. Exchange Server and SharePoint integration support in Lync Server 2013 in the Supportability documentation. |
Create the appropriate internal topology to support archiving (only if not using Microsoft Exchange integration for all users in your deployment) |
Run Topology Builder to add Lync Server 2013 Archiving databases (SQL Server databases) to the topology, and then publish the topology. |
To define a topology to incorporate Archiving databases, an account that is a member of the local users group. To publish the topology, an account that is a member of the domain admins group and RTCUniversalServerAdmins group, and that has full control permissions (read/write/modify) on the file share to be used for the Lync Server 2013 file store (so that Topology Builder can configure the required DACLs). |
Adding Archiving databases to an existing Lync Server 2013 Deployment in the Deployment documentation. |
Configure server-to-server authentication (only if using Microsoft Exchange integration) |
Configure servers to enable authentication between Lync Server 2013 and Exchange 2013. We recommend running Test-CsExchangeStorageConnectivity testuser_sipUri –Folder Dumpster to validate Exchange Archiving storage connectivity before enabling archiving. |
An account with the appropriate permissions for managing certificates on the servers. |
Managing server-to-server authentication (OAuth) and partner applications in Lync Server 2013 in the Deployment documentation or the Operations documentation. |
Configure archiving policies and configurations |
Configure archiving, including whether to use Microsoft Exchange integration, the global policy and any site and user policies (when not using Microsoft Exchange integration for all data storage), and specific archiving options, such as critical mode and data export and purging. If using Microsoft Exchange integration, configure Exchange In-Place Hold policies as appropriate. |
RTCUniversalServerAdmins group (Windows PowerShell only) or assign users to the CSArchivingAdministrator or CSAdministrator role. |
Configuring support for Archiving in Lync Server 2013 in the Deployment documentation. Exchange product documentation (if using Microsoft Exchange integration). |
Deploying Lync Server and Microsoft Exchange in Different Forests
If Microsoft Exchange Server is not deployed in the same forest as Lync Server, you must make sure that the following Exchange Active Directory attributes are synchronized to the forest where Lync Server is deployed:
msExchUserHoldPolicies
proxyAddresses
This is a multi-value attribute. When synchronizing this attribute, you need to merge the values, not replace them to ensure the existing values are not lost.