Program Managers Microsoft Corporation Taking advantage of Persistent Chat in Lync User Experience Architecture and Deployment CLNT200 Understand Lync 2013 Persistent Chat User Experience What Lync 2013 Persistent Chat means to IT from a planning administration and management perspecti ID: 129516
Download Presentation The PPT/PDF document "Moustafa Noureddine, Jason Issa" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1Slide2
Moustafa Noureddine, Jason IssaProgram ManagersMicrosoft Corporation
Taking advantage of Persistent Chat in Lync:User Experience, Architecture and Deployment
CLNT200Slide3
Understand Lync 2013 Persistent Chat User Experience
What Lync 2013 Persistent Chat means to IT – from a planning, administration and management perspective
Session ObjectivesSlide4
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
Key TakeawaysSlide5
Lync 2013 Persistent Chat Investment Pillars
Unified Client
Easy Migration
Server Infrastructure and Manageability
Rich PlatformSlide6
Common Use Cases
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 multi-function customer communications
Better account team coordinationEnhanced customer service
Financial ServicesR&D, Support, Call Centers
Account/Project ManagementSlide7
Persistent Chat User ExperienceSlide8
Lync Persistent Chat user experience
Seamless integration with Lync Client.
Access
to all Lync communication modalities.
Notification
tools to keep you up to date.Slide9
Unified Client
Integrated chat room environment within Lync 2013 client
Two separate clients in Lync 2010Slide10
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 roomPersistent Chat main user experienceSlide11
New room appears in Lync Client
Consistent interaction
experience as Lync contacts
Persistent Chat room interactionSlide12
Chat rooms and meetingsSlide13
File transfer in chat rooms
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 memberSlide14
Search within Persistent Chat roomsSlide15
Persistent Chat Room notification settingsSlide16
Notification feeds: keywords / ego
Topic feed window makes it easy for you to find keywords of interest
Ego
feed lets you know when someone mentions your nameSlide17
Persistent Chat room creation experience
- 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 roomSlide18
A chat room has the following properties:Name, DescriptionDisabled
Visibility – Private, Hidden, OpenType – Auditorium/NormalAdd-InMembers, ChatRoomManagers, PresentersCategory
Created by users with room creation privileges on the category
Follows restrictions set by the category
Can be deleted and content can be purged
Persistent Chat RoomsSlide19
high level architectureSlide20
Inside Lync 2013 Server Persistent Chat
Persistent Chat Service Role
Persistent Chat Store
Channel Service
Persistent Chat Compliance Service
Persistent Chat Compliance Store
Compliance File Store
File Store
Lync FE
Persistent Chat File Upload/ Download Service
Room Management Web ComponentSlide21
Lync 2013 Server Persistent Chat
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
Dependent
Lync
Pool
Lync Pool A
Lync Pool B
Persistent Chat Pool
Lync 2013
client
Registration Session Initiation Protocol (SIP)
Chat communication (XCCOS over SIP)
Persistent Chat Pool
XCCOS over SIPSlide22
planning, deployment and administrationSlide23
Add (one or more) Persistent Chat pools to the topology
Depends on a Lync poolCompliance 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™
cmdletsHigh-Level Deployment and Configuration StepsSlide24
Enable users for persistent chat via policy (Set-csPersistentChatPolicy)Scope: global, site, service (Lync pool), Tag (User(s))
EnableGroupChat, false by defaultConfiguration settings (Set-csPersistentChatConfiguration)Scope: Global
applies to all
Persistent Chat pools
in the topology
Service applies to a single
Persistent Chat pool
Default persistent chat history
Participant update limit
Room management URL – custom end-user room management workflow (written using Persistent Chat Server SDK)Persistent Chat: Policy and SettingsSlide25
Unit of administrationPersistent c
hat administrator creates and manages categoriesModel “ethical walls”A
way to aggregate rooms with similar
settings
Administrator chooses who can be members of rooms that will be created; and who is allowed to create rooms in the system
A category has
the following properties:
Name,
description
AllowedMembers – including specification of a deny listCreatorsInvitationsEnabled, FileUpload, ChatHistoryPersistent Chat Categories – Key System Design ElementSlide26
Persistent Chat in Lync Server Control PanelPolicySlide27
Persistent Chat in Lync Server Control Panel Configuration SettingsSlide28
Creating and Managing a Persistent Chat CategorySlide29
Bring in contextual information to enhance the room experiencePoints to a URL
Custom Microsoft Silverlight® application authored by using a Lync client Software Development Kit (SDK)Leverages conversation window extensibility to bring in outside content and experience to the room
Can access and intercept room content
Client-side add-in but
provisioned / registered
by the administrator
Can be associated with one or more chat rooms
An add-in has the following
properties:
Name, URLPersistent Chat Add-InsSlide30
Creating and Managing a Persistent Chat Add-InSlide31
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 ?
Planning for Persistent Chat – Key QuestionsSlide32
high availability and disaster recoverySlide33
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 failoverOtherDistributed File System Replication (DFSR) for file share replicationCompliance database uses same mechanism as Persistent Chat content database
Persistent Chat Servers (Pool one)
Persistent Chat Store
NY
Persistent Chat Rooms
Lync Pool One
Principal
Mirror
SQL mirroringSlide34
Persistent Chat Pool: Disaster Recovery
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
Persistent Chat Servers (Pool One)
Persistent Chat Servers (Pool One)
Persistent Chat
SQL – Active
Persistent Chat
SQL – Backup
DC1
DC2
SQL Log
Shipping for content
and compliance
DB
Persistent Chat Clients
Persistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL
mirroring
Persistent Chat
BackEnd
SQL mirroring for high availability within a datacenter
Backup DB configured in the topology
SQL Log Shipping across data centersSlide35
Stretched Persistent Chat Pool
When Datacenters Are Geo-Distributed with Low Bandwidth/High Latency
Logical 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
Physical topology
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)
Persistent Chat Servers (Pool One)
Persistent Chat Servers (Pool One)
Persistent Chat
SQL – Active
Persistent Chat
SQL – Backup
NY
LA
SQL Log content and compliance
database shipping
Low Bandwidth
High LatencyPersistent Chat ClientsPersistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL
mirroringSlide36
Stretched Persistent Chat Pool
When Datacenters Are Geo-located with High Bandwidth/Low Latency
Logical 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
Physical topology
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)
Persistent Chat Servers (Pool 1)
Persistent Chat Servers (Pool 1)
Persistent Chat
SQL – Active
Persistent Chat
SQL – Backup
NY
NJ
SQL Log
Shipping
High Bandwidth
Low LatencyPersistent Chat ClientsPersistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL MirroringSlide37
Disaster Recovery: FailOver
– Site Failure
NY
site
fails – Lync Pool One, Persistent Chat Servers/Backend in NY down
Failover Lync pool one to Lync pool two (invoke-
csPoolFailover
) -- causes Lync Pool two to route to
PChat
pool correctlyRemove 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
Manual SQL log shipping procedure + Lync and Persistent Chat PowerShell cmdlets
Persistent Chat Servers (Pool One)
Persistent Chat Servers (Pool One)
Perspective Chat
SQL – Active
Persistent Chat SQL – Backup
NYNJ
SQL log shipping
High bandwidth
Low latency
Persistent Chat Clients
Persistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL MirroringSlide38
Disaster Recovery: FailOver
– Lync OK, Persistent Chat Fails
Manual SQL log shipping procedure + Lync and Persistent Chat PowerShell cmdlets
Persistent Chat Servers (Pool One)
Persistent Chat Servers (Pool One)
Perspective Chat
SQL – Active
Persistent Chat
SQL – Backup
NY
NJ
SQL log shipping
High bandwidth
Low latency
Persistent Chat Clients
Persistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL Mirroring
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)
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
twoSlide39
Disaster Recovery: FailOver
– Persistent Chat OK, Lync Fails
Manual SQL log shipping procedure + Lync and Persistent Chat PowerShell cmdlets
Persistent Chat Servers (Pool One)
Persistent Chat Servers (Pool One)
Perspective Chat
SQL – Active
Persistent Chat
SQL – Backup
NY
NJ
SQL log shipping
High bandwidth
Low latency
Persistent Chat Clients
Persistent Chat Clients
Lync Pool One
Lync Pool Two
Principal
Mirror
SQL Mirroring
Lync Pool One Fails, Pool Two needs to route to Persistent Chat pool
Failover Lync pool one to Lync pool two (invoke-
csPoolFailover
) -- causes Lync Pool two to route to
PChat
pool
correctlySlide40
Single Persistent Chat pool stretched across sites
that have Lync pools paired for DRAdditional cold standby servers available to take load in case of DR, four active at a time, four standby
VLAN not required
Lifetime
of Lync and
PChat
pool is not coupled
– one can fail without the other
Persistent chat failure does not impact IM/Presence and Voice workloads, and vice-versaGeo-located data centers: Active servers in both data centers at any point - active database in one data centerRequires high bandwidth and a low latency connectionClients in site one could be talking to a server in site twoPersistent Chat server in site two could be talking to the primary database in site oneGeo-distributed data centers: Active Persistent Chat servers in only one data center, Active database in the same datacenterMirroring with optional witness provides automated HA for databaseDisaster recovery scenario requires admin interventionManual SQL log shipping steps for Persistent Chat content
PowerShell cmdlets for Persistent Chat and Lync failoverStretched Persistent Chat Pool: Key TakeawaysSlide41
migration, coexistence and interopSlide42
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
Migration, Coexistence and InteropSlide43
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
Connecting Legacy ClientsSlide44
Third Party IntegrationSlide45
MindLink Extends Persistent Chat to Other Platforms
Mobile clients
iOS
, BlackBerry, Android
Web
client
MAC & LinuxSlide46
MindLink Integrates Persistent Chat into your Business Processes
Restful API for Line of Business Integration
SharePoint integration
Outlook integration
Compliance
Enhanced document management, Order Management, Trading, Incident Response, Issue Tracking…
Persistent ChatSlide47Slide48
Monday, February 17
th
Exhibit
Hall Hours 6:00pm –
8:00pm
6:00pm
– 8:00pm Welcome
Reception
Tuesday
, February
18
thExhibit Hall Hours 8:00am – 9:00am (Breakfast), 10:30am – 5:00pm
8:00am
– 9:00am Breakfast (Exhibit Hall) 9:00am –10:30am General Session10:30am – 5:00pm Expo Hall Hours11:00am
– 12:15pm Sessions & Hands-on Labs12:15pm
– 2:00pm Lunch2:00pm – 5:00pm Sessions & Hands-on Labs5:00pm – 7:00pm Ask the ExpertsWednesday, February 19
th
Exhibit Hall Hours 10:30am – 4:30pm7:30am – 8:30am Breakfast8:30am – 11:30am Sessions & Hands-on Labs10:30am – 4:30pm Expo Hall
Hours11:30am – 1:00pm Lunch
1:00pm – 5:45pm Sessions & Hands-on Labs6:30pm – 9:30pm Attendee PartyThursday, February 20
th
Exhibit Hall Hours 9:00am – 12:00pm8:00am – 9:00am Breakfast9:00am – 12:00pm Expo Hall Hours
9:00am – 12:15pm Sessions & Hands-on Labs12:15pm –
1:30pm Lunch and DeparturesSlide49
Ask the Experts
Location: Meal Hall located on Level 1 in
Pinyon
Ballroom 4-8
Tuesday, February 18
TABLE TOPICS:
Best
Practices, Business Value, Clients
&
Mobility, Lync
Meetings
and Video, Lync Online, Networking, Platform, Server & Manageability, Voice, Lync Feedback Sessions
Meet face-to-face with the
foremost
experts in the
Lync field
and ask
them the questions
that
have you stumped.Slide50
Location: Breakout rooms located on Level 1
5:00pm-7:00pm
GROUPS INCLUDE:
Manageability –
Pinyon
2
Meetings & Web Experiences –
Bluethorn
4-6
Mobility –
Bluethorn
7-9
Presence & Chat –
Pinyon
1
Voice & Video –
Bluethorn
1-3
Come participate in targeted Feedback Sessions to hear about the
high-priority feature asks and help us improve the next release!
Lync Feedback
These sessions are meant to be informational, providing an understanding of the workload and conversational, to discuss your user scenarios and desired improvements.Slide51
Birds of a Feather
Birds
of a Feather flock together! Join daily breakfast discussions of relevant topics by sitting in the separately designated areas of the Meal Hall.
Seating
will be sorted in a different way for each Birds of a Feather breakfast:
Wed
ne
sday, February 19:
Where are you from?
Asia/Pacific, Eastern & Central Europe, Latin America, Middle East & Africa, US (West, Central & East) and Canada, Western Europe
Thursday, February 20:
What is your interest?
Best Practices, Business Value, Clients & Mobility,
Lync Meetings and Video, Lync Online, Networking, Platform, Server & Manageability, VoiceSlide52
#LyncConf14
/
msftLYNC
/
microsoft-lync
/
MSFTLyncSlide53
Lync Launch Pad
You’ve
launched Lync.
Now
Launch this
.
MS Pavilion – Expo HallSlide54
Fill out evaluations
to win prizes
Fill out evaluations on
MyLync
or
MyLync
Mobile.
Prizes awarded daily.Slide55
©
2013
Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.