Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

Deployment Checklist for Persistent Chat Server

 

Topic Last Modified: 2012-10-16

Deployment of Lync Server 2013, Persistent Chat Server requires that you deploy it in the correct sequence and that you complete all required deployment steps.

You can deploy Persistent Chat Server after you deploy your initial topology, including at least one Lync Server 2013, Front End pool or one Lync Server 2013, Standard Edition server. This topic describes how to deploy Persistent Chat Server by adding it to an existing deployment.

The following table lists the basic steps to deploy Persistent Chat Server and provides links for more details.

Persistent Chat Server Deployment Process

Task Steps Required roles and group memberships Related topics

Install prerequisite hardware and software

On hardware that meets system requirements, install the following:

  • On the Persistent Chat Server Front End Servers:
  • An operating system that meets system requirements
  • Software prerequisites for computers running Lync Server 2013
  • SQL Server on the server that will host Persistent Chat Server database

If Persistent Chat Server compliance is required:

  • SQL Server on the server that will host Persistent Chat Server compliance database

Any 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

Technical Requirements for Persistent Chat Server

Create the appropriate internal topology to support Persistent Chat Server (and optionally, Persistent Chat compliance)

Run Topology Builder to add a Persistent Chat Server pool to your topology:

  • Add Persistent Chat Server components to the topology
  • Create a SQL Server database for the Persistent Chat Server store (and a backup SQL Server for disaster recovery)
  • Define a new Lync File Store or use an existing Lync File Store for Persistent Chat Server files
  • Associate the Lync Server 2013 pool that can route requests to this Persistent Chat Server pool

If Persistent Chat compliance is required:

  • Add Persistent Chat Compliance Store
  • Click the Persistent Chat Server pool definition check box for enabling compliance
  • Publish the topology

If you install Persistent Chat Server on Standard Edition, the fully qualified domain name (FQDN) of the Persistent Chat Server pool must match the Standard Edition server, and the SQL Server databases are collocated on the SQL Server Express instance on the Standard Edition 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 the user should also have full control permissions (read/write/modify) on the Lync File Store for Persistent Chat Server files (so that Topology Builder can configure the required DACLs).

Adding Persistent Chat Server to Your Deployment in the Deployment documentation

Deploy Persistent Chat Server

Run the Lync Server setup on all the computers running Persistent Chat Server. The Persistent Chat Server setup is integrated into the Lync Server 2013 Deployment wizard that provides the following instructions:

  • Deploy local management store
  • Install Persistent Chat Server services
  • Request and assign certificates
  • Run and start the services

Any user who is a member of the local Administrators group.

Deploying Persistent Chat Server in the Deployment documentation

Create a Persistent Chat administrator

Add users to the CsPersistentChatAdministrator security group.

Any user who is a member of domain administrators.

Adding a Persistent Chat Administrator in the Deployment documentation

Configure Persistent Chat Server

Configure users:

  • User has to be enabled by policy to access Persistent Chat Server. By default, the policy is turned off for all users and can be defined at global/site/pool/user scopes.
  • Configure settings

User must be a member of CsPersistentChatAdministrator. To change policy, user must be in CsUserAdministrator, at a minimum.

Configuring Persistent Chat Server in the Deployment documentation

importantImportant:
You can deploy one or more Persistent Chat Server pools. We support multiple Persistent Chat Server pools for regulatory reasons whereby data generated in a given region is required to stay in that region. For example, if you deploy a Persistent Chat Server pool in Chicago, and another in Zurich to comply with regulations for data in Switzerland, users can connect to rooms in both the Persistent Chat Server pools, provided they have access.
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.