Archiving Deployment Overview
Topic Last Modified: 2011-02-23
As with deployment of your other Microsoft Lync Server 2010 components, deployment of Archiving Server requires that you use Topology Builder to create and publish a topology that incorporates the necessary components, prior to installing Lync Server 2010 on an Archiving Server.
You can deploy Archiving Server 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 Server by adding it to an existing deployment. If you incorporate the Archiving Server in your initial topology instead, the information required to deploy it as part of the initial topology is the same, but you do not run Topology Builder again to add the Archiving Server.
If you enable archiving in one Front End pool or Standard Edition server, you should then 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 session cannot be archived.
If archiving is critical in your organization for compliance reasons, be sure to deploy an Archiving Server and enable archiving for all appropriate users before you enable those users for Lync Server 2010.
The following table provides an overview of the steps required to deploy archiving support in an existing topology.
Archiving Server Deployment Process
|Phase||Steps||Roles and group memberships||Documentation|
Install prerequisite hardware and software
On hardware that meets system requirements, install the following:
Also set up file storage to be used for the archiving file share.
Domain user who is a member of the local Administrators group
Supported Hardware in the Supportability documentation
Server Software and Infrastructure Support in the Supportability documentation
Determining Your System Requirements in the Planning documentation.
Technical Requirements for Archiving in the Planning documentation
Create the appropriate internal topology to support archiving
Run Topology Builder to add archiving components to the topology, and then publish the topology, which must be done prior to installation of the Archiving Server.
To define a topology, 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 archiving file store (so that Topology Builder can configure the required DACLs)
Adding an Archiving Server to an Existing Deployment in the Deployment documentation
Install Archiving Server and start the Lync Server Archiving service
| || |
User account that is a member of the Local Administrators group, is a domain user account that is a member of the RTCUniversalServerAdmins group, and has access permission for the SQL instance for the Archiving database.
Install an Archiving Server in the Deployment documentation
Configure archiving policies and support
Configure archiving, including the global policy and any site and user policies, and specific archiving options, such as critical mode and data export and purging.
RTCUniversalServerAdmins group (Windows PowerShell only)or assign users to the CSArchivingAdministrator or CSAdministrator role
Configuring Support for Archiving in the Deployment documentation