Beruflich Dokumente
Kultur Dokumente
Module Overview
Overview Lync Server 2013 Persistent Chat architecture
Design Lync Server 2013 Persistent Chat
Channel Service
File Store
Components and Requirements Persistent Chat Server Components include: One or more computers running Persistent Chat Server Server(s) that host the SQL Server back-end database for hosting the Persistent Chat content If compliance was enabled, a server(s) that host the SQL Server backend database.
Organizational Requirements Key pre-deployment questions: Who should be enabled, which user profiles? How many users should be enabled? Whats the migration scenario? Are there compliance or regulatory requirements? How do you want to control scopes, ethical boundaries, and access? How do you want to create rooms? What kind of add-ins do you want to provision? What kind of high availability and disaster recovery requirements do you have?
Server Infrastructure
Registration Session Initiation Protocol (SIP) Chat communication (XCCOS over SIP)
Lync Pool A Dependent Lync Pool Lync Pool B XCCOS over SIP
Each with up to four active Persistent Chat servers supporting 80K concurrent endpoints
SQL mirroring for database high Stretched pool for disaster recovery,
Designing a Persistent Chat Room Persistent Chat Room best practices Single category scope Enable users to create new chat rooms Relevant metadata Custom room creation workflow Use add-ins
Deploy Persistent Chat Persistent Chat Deployment Steps: 1. Add (one or more) Persistent Chat pools to the topology 2. Deploy Persistent Chat server 3. Configure administrators by using the Role Based Access Control (RBAC) 4. Configure persistent chat
End users
Including message authors, cannot delete content from any chat room. Can disable rooms, but cannot delete rooms. Auditorium room specific role the users that can post in these rooms, unique per room.
2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.