Transcript Taking advantage of Persistent Chat in Lync: User

Understand Lync 2013 Persistent Chat User Experience
What Lync 2013 Persistent Chat means to IT – from a
planning, administration and management perspective
Lync 2013 Persistent Chat can enable real-time,
persistent collaboration among global teams
Lync 2013 Persistent Chat delivers a unified client,
administration experience for Lync users and IT staff
Important considerations for an IT admin as they plan
for Persistent Chat
Unified Client
Server Infrastructure
and Manageability
Rich Platform
Easy Migration
Faster response to
market opportunities
Streamlined global
operations
Information sharing
across geographies
Improved research
distribution
Efficient escalations
Better team
information sharing
Enhanced access to
experts
Streamlined offshore
projects
Centralized multifunction customer
communications
Better account team
coordination
Enhanced customer
service
Seamless integration with Lync Client.
Access to all Lync communication modalities.
Notification tools to keep you up to date.
Integrated chat
room environment
within Lync 2013
client
Listed rooms are those you have access to
Ability to search and find rooms
Stay on top of your communication, seeing
at a glance new notifications and unread
count per room
New room
appears in Lync
Client
Consistent interaction
experience as Lync
contacts
Uploading files to the chat
room is as simple as drag and
drop
All room members have access
to all files
Ability to download files as
long as user is a room member
Topic feed window makes it easy
for you to find keywords of
interest
Ego feed lets you know when
someone mentions your name
- Set new room properties: Name, description, privacy
- Ethical walls (categories) make room management much easier
- Assign add-in to room
- Manage room access and management by separating managers/members
- Stay on top of your communication by seeing at a glance new notifications and unread
count per room
Persistent Chat Rooms
Lync FE
Persistent Chat Service Role
Registration Session
Initiation Protocol
(SIP)
Chat communication
(XCCOS over SIP)
Lync Pool A
Lync Pool B
Dependent
Lync
Pool
XCCOS
over SIP
Persistent Chat Pool
Lync 2013 client
Persistent Chat Pool
Enterprise Edition (EE) topology
Multiple Lync pools
One or more Persistent Chat pools – Each
with up to four active Persistent Chat
servers supporting 80K concurrent
endpoints
Servers can be virtualized
Recommended standalone database for
persistent chat content and compliance
database
SQL mirroring for database high availability
Stretched pool for disaster recovery, with
SQL log shipping
Add (one or more) Persistent Chat pools to the topology
Depends on a Lync pool
Compliance is optional
Deploy Persistent Chat server
Integrated into server install
Configure administrators by using the Role Based Access Control (RBAC)
role, CsPersistentChatAdministrator
Configure persistent chat
Lync Server Control Panel integration
Windows PowerShell™ cmdlets
Persistent Chat: Policy and Settings
Persistent Chat Categories – Key System Design Element
Administrator chooses who can be members of rooms that will
be created; and who is allowed to create rooms in the system
Policy
Configuration Settings
Persistent Chat Add-Ins
Name, URL
Who (user profile) and how many (scale) should be enabled for
persistent chat ?
HA-DR requirements ?
Are there regulatory requirements ?
Are there compliance requirements ?
Category design – scopes and ethical boundaries ? Who can create
rooms ?
Custom workflow and enforcement for room creation ?
What interesting AddIns should you provision ?
Are you migrating or deploying Persistent Chat for the first time ?
Persistent Chat Pool: Automated High Availability
HA for Persistent Chat within the
data center
Persistent Chat Front Ends:
Pool with up to four active Persistent Chat
Front End Servers
Persistent Chat back end:
SQL mirroring, with optional witness
provides automated failover
Other
Distributed File System Replication (DFSR) for
file share replication
Compliance database uses same mechanism as
Persistent Chat content database
NY
SQL
Mirror mirroring Principal
Lync Pool One
Persistent Chat Store
Persistent Chat Servers (Pool one)
Persistent Chat Rooms
Persistent Chat Pool: Disaster Recovery
Persistent Chat BackEnd
Using a Stretched Pool
Looks like one Pchat pool within the
topology
Physical machines in the pool span
datacenters
50% active, and 50% backup capacity to be
used in case of a disaster
DC1
Mirror
Lync Pool One
SQL
mirroring
Principal
Persistent Chat
SQL – Active
Persistent Chat Servers (Pool One)
Persistent Chat Clients
SQL Log
Shipping for
content and
compliance DB
SQL mirroring for high availability within a
datacenter
Backup DB configured in the topology
SQL Log Shipping across data centers
DC2
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Stretched Persistent Chat Pool
When Datacenters Are Geo-Distributed with Low Bandwidth/High Latency
Logical topology
Physical topology
Site one: Lync pool one, Pool (machines one through
eight)
Persistent Chat database+ mirror + witness
(optional)
Backup database (SQL log shipping target)
Site two: Lync pool two
Site one: Lync pool one, Persistent Chat pool –
machines one - four, all active, database+ mirror +
witness (optional)
Site two: Lync pool tool, Persistent Chat pool –
machines five – eight, all idle, Backup database (SQL
log shipping target)
NY
Mirror
Lync Pool One
SQL
mirroring
Principal
Persistent Chat
SQL – Active
Persistent Chat Servers (Pool One)
Persistent Chat Clients
SQL Log content
and compliance
database
shipping
Low Bandwidth
High Latency
LA
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Stretched Persistent Chat Pool
When Datacenters Are Geo-located with High Bandwidth/Low Latency
Logical topology
Physical topology
Site one: Lync pool one, Persistent Chat pool
(machines one through eight)
DB + mirror + witness (optional)
Persistent Chat backup database (SQL log
shipping target)
Site two: Lync pool two
Site one: Lync pool one, Pool – machines one - four,
two active and two idle, Persistent Chat database+
mirror + witness (optional)
Site two: Lync pool two, Pool – machines five –
eight, two active and two idle, Persistent Chat backup
database (SQL log shipping target)
NY
NJ
SQL
Mirroring
Principal
Mirror
Lync Pool One
Persistent Chat
SQL – Active
Persistent Chat Servers (Pool 1)
Persistent Chat Clients
SQL Log
Shipping
High Bandwidth
Low Latency
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool 1)
Persistent Chat Clients
Disaster Recovery: FailOver – Site Failure
NY site fails – Lync Pool One, Persistent Chat Servers/Backend in NY down
1.
2.
3.
4.
5.
Failover Lync pool one to Lync pool two (invoke-csPoolFailover) -- causes Lync Pool two to route to PChat pool correctly
Remove log shipping from PChat Backup DB, Apply unapplied transaction logs and bring backup DB online (manual)
Set Pchat pool state to be failed over (set-csPersistentChatState) – causes Pchat services to connect to backup DB
Set Pchat active servers to those in NJ (set-csPersistentChatActiveServer)
Clients connected to Persistent Chat servers in Site one reconnect to those in site two
NY
Manual SQL log
shipping procedure +
Lync and Persistent
Chat PowerShell
cmdlets
SQL log shipping
Mirror
Lync Pool One
SQL
Mirroring
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Principal
Perspective Chat
SQL – Active
High bandwidth
Low latency
NJ
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Disaster Recovery: FailOver – Lync OK, Persistent Chat Fails
Pool One is still primary, routes to Persistent Chat Pool
Remove log shipping from PChat Backup DB, Apply unapplied transaction logs and bring backup DB online
(manual)
2. Set Pchat pool state to be failed over (set-csPersistentChatState) – causes Pchat services to connect to backup DB
3. Set Pchat active servers to those in NJ (set-csPersistentChatActiveServer)
4. Clients connected to Persistent Chat servers in Site one reconnect to those in site two
1.
NY
Manual SQL log
shipping procedure +
Lync and Persistent
Chat PowerShell
cmdlets
SQL log shipping
Mirror
Lync Pool One
SQL
Mirroring
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Principal
Perspective Chat
SQL – Active
High bandwidth
Low latency
NJ
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Disaster Recovery: FailOver – Persistent Chat OK, Lync Fails
Lync Pool One Fails, Pool Two needs to route to Persistent Chat pool
1.
Failover Lync pool one to Lync pool two (invoke-csPoolFailover) -- causes Lync Pool two to route to PChat pool
correctly
NY
Manual SQL log
shipping procedure +
Lync and Persistent
Chat PowerShell
cmdlets
SQL log shipping
Mirror
Lync Pool One
SQL
Mirroring
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Principal
Perspective Chat
SQL – Active
High bandwidth
Low latency
NJ
Persistent Chat
SQL – Backup
Lync Pool Two
Persistent Chat Servers (Pool One)
Persistent Chat Clients
Stretched Persistent Chat Pool: Key Takeaways
Migration supported from Microsoft Office Communications
Server (OCS) 2007 R2 or Lync 2010 Group Chat Server
Legacy chat clients (OCS 2007 R2 and Lync 2010) can
connect to Persistent Chat Server 2013
Automatic configuration or manual configuration to
point legacy client to Persistent Chat Server 2013
PowerShell cmdlet to create a friendly Contact object
(aka friendly URIs) representing a Lync 2013
Persistent Chat pool
new-csPersistentChatEndpoint
•
•
•
•
•
•
•
•
Enhanced document management, Order
Management, Trading, Incident Response, Issue
Tracking…