Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Lync 2013: Architecture & Administration


Published on

Presented by Johan Delimon.

  • Be the first to comment

Lync 2013: Architecture & Administration

  1. 1.
  2. 2.
  3. 3. Integrated System. Connected. Enterprise voice. Skype. Audio, Video & web conferencing. Federation.Simple to manage. Mobile. Remote access. Persistent chat. Hybrid. Efficient. Reduced Modern operations. Mission critical. maintenance. High scale. Monitoring & reporting. Single System. Compliant. Secured by design. Scalable. Contact store. Easy site recovery. Flexible. Virtualization. Small footprint.
  4. 4. Lync Server HybridLync Online
  5. 5. Lync Server HybridLync Online
  6. 6. Lync Server HybridLync Online
  7. 7. • Built-in telephony features • One dial plan, CAC and location information across the enterprise.Enterprise grade telephony. • One Administration for all voice scenario, gateway, devices and phones.Built-in component, no other • Response Group Service Manager* built-in, including IVR.server required. • SIP Trunk and Inter-trunk routing*.Scale with voice like other • M:N Mediation Server to Gateway Routing*workloads • Routing resiliency* • Caller-id improvements*Centralized • Delegate handling*management, distributed. • DID on-premise, user online using hybrid cloud.* • IP phone support for Office 365.* • Lync-to-phone for Office 365.
  8. 8. AD Edge server SQL EE pool Reverse proxy WAC Voice/video traffic*New in Lync Server 2013 and Office 2013 http
  9. 9. GSM Media gateway DMZ Internet Reverse proxyMedia server Lync server Lync push notification services WiFi Media for callback SIP https (XML) Edge Push notification for server Windows Phone VOIP App notifications for iOS Voice/Video over IP
  10. 10. Mirrored SQL SQL SQL Lync persistent chat pool AD Persistent chat (XCCOS) SQLRegistration,presence (SIP) Lync edgepersistent chat(XCCOS) Lync FE pool Reverse proxy Registration, presence (SIP) persistent chat (XCCOS)
  11. 11. Front-end server runs all workloads. AD No other server required to additional Optional backup Standard edition functionalities. All in one box Standard Edition deployment. Standard edition Ideal for proof of concept, pilot, small and medium businesses. Functionality: IM, Presence, Voice, Video, Conferencing, Mobility. Highly available* when peered with another server. PSTN access with Gateway, Direct SIP or SIP Trunk. Scalability: up to 5,000 users.14
  12. 12. Similar to Standard edition architecture Enterprise edition AD front end servers No other server required to additional functionalities SQL Enterprise edition with SQL server. Ideal for large and medium size businesses, regional deployment. Functionality: IM, Presence, Voice and Video, Conferencing, mobility. Highly available, medium scale to large scale. Scalable *: Scale up by adding more FE servers: • Up to 12-20 servers per pool • Up to 200,000 active users • Up to 1 million provisioned users15
  13. 13. Flexible system AD Primary site SQL PSTN High capacity architecture Europe in each region. Distributed resources with high External access availability. SQL Allow least cost routing across the Remote site with survivability enterprise. SIP trunk Federation and remote access from SQL Directors 2 datacenters. External access PSTN Americas Secondary site16
  14. 14. Small footprint AD Front-end server Active Web access and mobile Lync endpoints directory running all workloads. FPO SQL SQL Server backend. Monitoring Edge server. SIP registrar XMPP Gw DMZ Central Mgt Voice routing Exchange UM Remote and archiving Persistent chat Server. users Mobile SQL Conferencing Monitoring database. Lync Web App Public Exchange. clouds Edge Front end Back end System server servers SQL server System Center. Center Federated SharePoint WAC*. businesses Optional persistent PSTN chat pool WAC*New in Lync Server 201317
  15. 15. Lync 2010 pool Lync 2013 pool8 Front-Ends, tightly 20 Front-Ends, looselycoupled back end coupled store SQL SQL SQL DB business logic Storage DB used for presence Dynamic data: presence updates, subscriptions updates handled on FEs 1..8 FE 1..20 FE
  16. 16. Session security: HTTPS Audio/Video: SRTP Caller always authenticated IM content filter Lync server pool Client version checkRemote users SQL SQL Authentication & Public DMZ isolation through Session security: TLS clouds Edge Anti virus. Audio/Video: SRTP Windows Server built in protections. Caller always authenticated IM filter Secure anywhere IM content filter Federated access Client version check businesses FPO Edge Message throttling PSTN GW servers Mandatory session validationPSTN
  17. 17. Shared Servers Shared ServersP1 P2 P3 P4 P5 P6 P7 P8 P9 P10
  18. 18. Fiber Channel Guest Host Guest SANHost NICs NIC NICsNIC SAN Standard Edition Front-end Host Host OS Edge OS Front-end Monitoring DB Edge SQLDASDAS DAS DAS DAS DAS DAS DAS DASDAS Host-to-Host NIC
  19. 19. Multi-party A/V, Lync PSTN access Server Signaling (e.g., IM/P, Data Collaboration, App Integration ) Peer-to-Peer A/VLync
  20. 20. MIIS, FIM or ILM Synchronization Trust Trust relationship relationship AD DSAD DS Users AD DS UsersUser forest User forest Disabled users Resource forest
  21. 21. Legacy and Legacy andlatest remote latestaccess. federation.Production Pilot Legacy edge Merge-CsLegacy Topology Legacy director Import-CsLegacy Configuration Import-CsLegacy Conference Directory Move-CsLegacy User SQL SQL AD Legacy pool Latest pool
  22. 22. Legacy and Legacy and Latest remotelatest remote latest access.access. federation.Production Pilot Legacy edge Latest edge Legacy director Latest director SQL SQL AD Legacy pool Latest pool
  23. 23. Lync 2013 previewSmartphones, slates, web browsersMulti-tenant configurations, hybrid topology, ExchangeApp Marketplace 2013 previewLync, Exchange, Microsoft Office SharePoint®, Active Directory SharePoint 2013 previewUnified Contacts, IM Archiving, OWA meeting scheduling
  24. 24. *New in Lync Server 2013
  25. 25. Unified e- SQL discovery, preservation,Contacts records management End-user access Buddy list experience to IM archivefavoritesbuddy list End-user in mailbox Lync IM and conversation Read favorites history folder R/W favorites online meeting and buddy list and buddy list experience FE EWS Outlook 2013, Lync 2013 Lync Lync rich client, OWA Mobile 2010 Lync Lync server Exchange Presence Archiving CDR QoE Web Conf server Lync Storage Service Queue Queue + task manager DB Archival processing Monitoring processing Unified contacts (IM, WebConf) (CDR/QoE) Replication Exchange 15 SQL DB for HA
  26. 26. SQL AD SIP EdgeOCS/Lync serverFederated SQL SIP SIP XMPP SIP SIP FPO
  27. 27. US East XMPP Federation Lync Pool 1 (Runs XMPP GW) Lync Edge (Runs XMPP Proxy) Outbound & InboundLync Pool 2 (Runs External XMPP XMPP GW) Fed Route US West Google Talk Lync Pool 3 Lync Edge (Runs (Runs XMPP GW) XMPP Proxy) Google Talk Servers External XMPP Fed (Direction shows TLS Connection establishment)
  28. 28. Directory Sync Lync 2013 AD Active Directory Active Directory Federation Services Microsoft Federation Gateway Lync 2013 pool SQL Lync Federation Lync edgeLync 2010 pool SQL Reverse proxy Lync online user
  29. 29. Cloud. Ready. Federation. Cloud flexible Interoperability. IT Efficiency. Deployment Option. Uptime Assurance.Modern Operations. On-premise. Integrated Admin. Hybrid.Remote PowerShell. Online.
  30. 30. Make deploymentTopology Simplify topology simplerScalability Brick Architecture Better scalability Storage Lync Storage Service Closer integration in Model (LySS) existing environment Pool- & site-levelResiliency Higher SLAs disaster recovery Online Leveraging the power Hybrid scenariosIntegration of online
  31. 31. Shared enterprise OfficeWeb App server farmOffice Web App server farmshared by SharePoint,Exchange, and Lync 2013Preview ServerOffice Web App server farmdeployed and managed bydedicated serveradministrator
  32. 32. What is the Lync 2013 HighAvailability Model? Problem: Solution: Lync 15 Bricks • Front End servers manage user state • New Lync 2013 workloads & clients • Front-end servers keep synchronous backup (multi-view copies of their data on 3 other Front-ends. video, XMPP, mobility, LWA) require • Front End servers and Back End databases more server resources per user. are “loosely” coupled • This impacts the number of users per • “Lazy writes” to the database for rehydration Front-end server. and disaster recovery • SQL backend is the bottleneck preventing Scale-out - adding more servers per Pool (> 10) • Every transaction needs to be committed to the Database. • Managing HA for DB is expensive
  33. 33. 10 FE + tightly coupled back end Lync 2013 Preview (FE s+ loosely coupled Back-end store) Blob Storage SQL® Server database DB used for storing (DB) bottleneck – “Blobs” – persisted business logic store DB used for presence updates and subscriptions Dynamic data: Presence updates handles on FEs 1-10 Front End Servers 1-N Front End Servers55
  34. 34. High Availability - Architecture • Lync Users are automatically mapped to “Groups” • Each “Group” is dynamically assigned to 3 Front-end servers within a Pool (a Primary, a Secondary and a Tertiary). • When a user logs in, the Primary server will start servicing all of the user’s requests. • Changes to the user’s data (such as Contact list changes) will be synchronously replicated to secondary/tertiary as well (3 replicas). • If a primary server dies, then this group would fail over to the secondary. (No data loss) • Writes to the back-end database occur periodically (not synchronous). • When a server dies, all the “Groups” assigned to that server as will failover to different servers (load balancing).
  35. 35. High Availability – How does it work? • Bob is homed on FE1 (primary) Pool Back-end • There are 3 copies of this user’s data: 1 primary (FE1), 2 backups (replicas in FE2, FE3) • User is signed in to primary • User’s activities, data are replicated • Primary goes down • User re-signs to one of the backups • Replicated data is available on FE2. User
  36. 36. Pool Size (Total number of Front Minimum number of Front EndEnd Servers) Servers that must be running1 12 13 24 25 36 37 48 4
  37. 37. Quick overview of mirroring Primary publisher (principal) Secondary subscriber Witness Server (optional, but enables automatic failover; this is a SQL Server High-safety mode (synchronous)Mirroring requirements Primary, mirror, and witness must have the same version of SQL Primary and mirror must have the same edition; Witness can be different edition Not required to have same instance name between primary/mirror, recommended for ease of administration/deployment
  38. 38. Manual failover (planned or no Witness)Get-CsDatabaseMirrorState -PoolFqdn <poolFQDN> -DatabaseType UserGet-CsDatabaseMirrorState -PoolFqdn <poolFQDN> -DatabaseType CMSInvoke-CsDatabaseFailover -PoolFqdn <poolFQDN> –DatabaseType User-NewPrincipal mirror –VerboseInvoke-CsDatabaseFailover -PoolFqdn <poolFQDN> –DatabaseType CMS -NewPrincipal mirror –VerboseOptional Witness Server will allow automatic failover if primary SQL Serverfails
  39. 39. What we had:Lync 2010MetropolitanSiteResiliency
  40. 40. The metropolitan site resiliency solution supported forLync Server 2010 is NOT supported for Lync Server 2013 PreviewIf you have already deployed a Lync Server 2010 metropolitan siteresiliency topology, you have two options when upgrading toLync Server 2013 Preview:
  41. 41. Shared Servers Shared ServersP1 P2 P3 P4 P5 P6 P7 P8 P9 P10
  42. 42. Lync requirementsServices for IM, presence information, andconference callingFast failover while preserving user state to Group 2 Groupmaintain in-flight user sessions 1 Windows Fabric Group Group NodeAutomatic scaling and load-balancing when new User Group 1 3 Window Windowsnodes are added to the cluster s Fabric Fabric Node 1 NodeLync failover model Group 2Users are mapped to groups Group Group 3 1Each group is a stateful service with three replicas Windows Fabric Node Group Windows 2 FabricUser calls go to the primary replica of the service Group Windows Node User Group 3 Fabric 2Resolve cross-group calls using the NodeWindows Fabric Naming service
  43. 43. Pairing RepairedUser Pool Failback Pool Failover Experience in Failover Failure Pool 1 Pool 1 Users Users Pool 2 Pool 2 Users Users Backup Pool 1 Pool 1 User Data User Data Pool 2 Pool 2 User Data User Data Pool 1 Pool 2 Data Center 1 Data Center 2
  44. 44. Feature HA DR Feature HA DRPeer-to-peer (all modalities)   Topology Builder  Presence   Lync Server Control Panel  Conferencing (all modalities)   Persistent Chat  UCWA   Planning Tool  Archiving   PSTN Voice  CDR / QoE  X CAA / CAS / PVA / GVA  Federation   RGS / CPS / E911  XPIC routing   Call Admission Control  XUnified Contact Store   XMPP  
  45. 45. Front End Server Arch CDR QoE Web Conf Lync Storage Service Replication for HA Connection Management (OAuth, Exchange , SQL) Unified Exchange 2013 Lync CDR/QoE Contacts Preview Archives Data Mailboxes
  46. 46. A single authentication mechanism in Lync 2013 Preview for Office servers and services that scales to the marketplace
  47. 47. AD FS & Directory Sync On-premises Active Directory MSODS Active Directory AD Active Directory Lync 2013 Preview Online Tenant Provisioning Lync 2013 Preview (BEC) Active Directory Office 365 SharePoint 2013 Preview Online Exchange 2013 Preview ACS Online STB Active DirectorySharePoint 2013 Preview Exchange 2013 Preview Online Provisioning Workflow Server-to-Server Authentication (Present Token) Get Token/Validate Token
  48. 48. End User Access to IM End-User Lync IM and Unified Archive in Mailbox Online Meeting eDiscovery, Preservation, Conversation History Experience Records Management Folder Experience Lync archives to Exchange E FE Exchange Hold policy To Lync W S Lync Server Exchange Archiving Policy: Lync honors mailbox hold  End user accesses IM conversations in  Meeting Archiving: Lync archives Meeting policy from Exchange Exchange Conversation History Folder content to Exchange Instant Messaging (IM )Archiving: Lync  Compliance Admin discovers and preserves  Compliance Admin discovers and preserves archives IM data to Exchange IM content using Exchange compliance tools meeting content using Exchange compliance tools
  49. 49. Lync Server 2013 Mailbox Hold Policy –> Archiving Policy Preview Exchange Server Get Mailbox Hold 2013 Preview Policy AD Lync Server Front End Session Transcripts Web Session TranscriptsConference Archives Exchange Store Lync Server Session Transcripts Mailbox Server Front End (Optional) Archiving Db for archiving users without Exchange 15 Lync Server mailboxes Front End
  50. 50. Exchange 2013 Migrate Buddy List Preview Lync 2013 Preview Pool & Read Favorites & Buddy List Unified Communications Web API Unified Contact Store Buddy List Updates Enables… ACLs Contacts (Workgroup Favorites Federated) Buddy List Read/Write Favorites & Buddy List Notifications Read Favorites & Buddy ListOutlook 2013 Preview, Lync 2013 Preview Rich Client, OWA Lync Lync 2010 Mobile  Same People card across Lync and Office  Same favorites and Buddy List across Lync, Outlook, OWA  De-duped & aggregated People search