Introduction to Lync Server 2010


Published on

Introduction to Lync Server 2010, Presented by Adam Jacobs at Microsoft Tech.Days UK 2011 at Fulham Broadway Vue Cinemas

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Introduction to Lync Server 2010

  1. 1.
  2. 2. Introduction to Lync Server<br />Adam Jacobs<br />Lync MVP<br />@adamjacobs<br /><br /><br />
  3. 3. Agenda<br /><ul><li>What is Lync Server?
  4. 4. History
  5. 5. Industry recognition
  6. 6. Implementation approaches
  7. 7. Technical differentiators from Office Communications Server (OCS)
  8. 8. Setup and deployment
  9. 9. Introducing:
  10. 10. The Central Management Store (CMS)
  11. 11. Call Admission Control (CAC)
  12. 12. Media Bypass
  13. 13. Futures</li></li></ul><li>What is Lync Server?<br />
  14. 14. What is Lync Server?<br /><ul><li>Lync not LINQ
  15. 15. The new name for OCS
  16. 16. An IP-PBX or traditional PBX replacement
  17. 17. A new breed of software-based telephony
  18. 18. Fully immersed within your PC (or Mac) desktop user experience – Office, SharePoint & Lync Client
  19. 19. The heart of Microsoft’s UC stack</li></li></ul><li>Future of Communications<br />Communications Today<br />E-mail and<br />Calendaring<br />Web<br />Conferencing <br />Video<br />Conferencing <br />InstantMessaging (IM)<br />AudioConferencing<br />Telephony<br />Voice Mail<br />Telephony and<br />Voice Mail<br />InstantMessaging<br />Unified Conferencing: Audio, Video, Web<br />E-mail andCalendaring<br />User Experience<br />User<br />Experience<br />User Experience<br />User<br />Experience<br />User Experience<br />User<br />Experience<br />User Experience<br />Unified Inbox <br />& Presence<br />Authentication<br />Administration<br />Storage<br />Compliance<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />Authentication<br />Administration<br />Storage<br />
  20. 20. Then…<br />Microsoft®<br />Office Communications <br />Server<br />A PBX companion – high level deliverables include:<br /><ul><li>Voice calls via existing handsets (RCC) and Communicator/“Optimised Devices” (EV)
  21. 21. Video calls
  22. 22. IM and presence
  23. 23. Mobility (including IM, presence and single-number reach)
  24. 24. Collaboration (desktop/file sharing, group chat and *dial-in conferencing)</li></ul>*Office Communications 2007 R2<br />
  25. 25. And now…<br />Microsoft<br />®<br />Lync<br />TM<br />A PBX replacement – via added functionality:<br /><ul><li>Enhanced resilience - without the need for h/w load balancing (web workloads still require HLBs)
  26. 26. Survivable Branch Appliance – a purpose-built appliance for branch deployments
  27. 27. Call Admission Control (CAC) – for the prevention of VoIP over subscription
  28. 28. Enhanced 9-1-1 (NA only) – CU1 delivers location functionality
  29. 29. Superior conferencing - voice announcements and an integrated client! (no Live Meeting client or Outlook Conferencing add-in)</li></li></ul><li>Industry recognition<br />“OCS…is certainly going to shake up the market.”<br />36% companies surveyed are already using OCS as UC client, more than IBM, Cisco and Public IM clients.<br />“If you didn’t think Microsoft was serious about voice communications before, you better believe it now.”<br />“Magic Quadrant for Unified Communications,” July 28, 2010.<br />
  30. 30. Implementation approaches<br />Identify PBX integration opportunities – software upgrades and/or a vendor application gateway. Consult your PBX vendor and visit the *UCOIP<br />Introduce Conferencing functionality and cut existing costs (measure telephony capacity first) – my workplace saved £60k per annum!<br />Leverage existing PBX investment and introduce Communicator concepts via RCC<br />Consult your PBX vendor and visit the *UCOIP, identify integration opportunities. Alternatively you can deploy a side-by-side voice gateway<br />Telephony growth supported by EV with Lync chosen as standard for strategic replacement<br />Initially choose mix legacy, RCC and EV for agile workers (project teams, senior executives and IT)<br />Alternatively it could be the right time to replace your existing PBX for Lync – how many times has this asset been written off? <br />For greenfield deployments a voice gateway could be used, consult the *UCOIP for supported hardware<br />*Unified Communications Open Interoperability Program - here<br />
  31. 31. Technical differentiators from OCS<br />
  32. 32. Key Lync Roles and Servers<br />*Central Management Store (CMS)<br />covered in subsequent slide<br />Back End Server<br />Lync database<br />Archiving Server<br />collects IM and Meeting content<br />Monitoring Server<br />collects call quality and CDR related information<br />Director<br />Internally, routes clients to corresponding home server<br />Externally, reverse proxies authentication requests<br />Front End Server<br />Handles authentication/registration, address book, IM, Conferencing & Response Groups<br />Mediation Server<br />translates signalling and media (where bypass is not used) and routes to PSTN via gateway, IP-PBX or SIP trunk<br />Edge Server<br />used for external Communication & Collaboration (without the need for VPN)<br />*Survivable Branch Appliance (SBA)<br />a purpose-built Lync appliance, typically utilised for branch deployment<br />A/V Conferencing Server<br />as the name suggests (can be collocated with Front End server or deployed separately)<br />*Introduced with Lync<br />
  33. 33. Setup and deployment changes worth mentioning<br /><ul><li>Planning Tool
  34. 34. Export to Topology Builder (.tbxml)
  35. 35. Topology Builder
  36. 36. Tool used for .tbxml import, topology setup, modification and validation prior to deploying first server and publishing within the Central Management Store (CMS)
  37. 37. Mediation role can now be collocated with front end role = minus 1 server </li></ul>Essentially one Standard Edition Server could support Enterprise Voice, IM, Presence and Conferencing for up to 5000 users!<br />For more information on planning and designing your Lync topology, I’d suggest you watch Lync Server Planning Tool: Design a Site and Create a Topology via TechNet NextHop (see resources slide)<br />
  38. 38. Central Management Store (CMS)<br /><ul><li>Replaces Active Directory for most configuration storage (phone numbers still held within AD)
  39. 39. The CMS data is held within a SQL database
  40. 40. Centralises the administration of all Lync Server roles (including Edge servers)
  41. 41. There is a minimum requirement of 2 x CMS databases - 1 x master (RTC) and 1 x replica (RTCLOCAL)
  42. 42. RTC and RTCLOCAL databases are replicated
  43. 43. Resilient architecture – Front End Server CMS (replica) will continue to function where connectivity is lost to the master</li></li></ul><li>Call Admission Control (CAC)<br /><ul><li>Put simply CAC is the bandwidth management service built into Lync Server
  44. 44. CAC bandwidth policies can be set to control
  45. 45. Audio - max bandwidth (kbps) assigned for all/individual sessions
  46. 46. Video - max bandwidth (kbps) assigned for all/individual sessions
  47. 47. Policies are applied between sites, where multiple network subnets can be associated
  48. 48. Alternate routes can be utilised where over-subscription occurs, i.e. when local ISDN is at capacity then a route to PSTN over an Internet based SIP trunk could apply</li></li></ul><li>Media Bypass<br /><ul><li>Media bypass reduces the load on your Mediation servers (allowing support for up to 5000 users, where Front End and Mediation roles are collocated)
  49. 49. This is achieved by negating the need for transcoding between the Lync client or phone and the voice gateway
  50. 50. In this scenario the G.711 voice codec is used, instead of RTAudio
  51. 51. Recommended gateway vendors include AudioCodes, Dialogic, NET and Ferrari</li></li></ul><li>Futures<br />
  52. 52. Lync Mobile<br /><ul><li>Mobile clients are expected for:
  53. 53. *iPhone aka “iLync”
  54. 54. *Windows Phone 7
  55. 55. BlackBerry – now available BES v.5.0 SP3
  56. 56. Nokia
  57. 57. Android</li></ul>*NB<br />Functionality will include:<br /><ul><li>One-click to join conference
  58. 58. Single number reach</li></ul>ETA late 2011<br />
  59. 59. Lync for XBOX “videoKINECT”<br />ETA late 2011<br />
  60. 60. Lync Server + Skype = ?<br />Jamie Stark <br />Lync Server Product Manager<br />
  61. 61. Resources<br />
  62. 62. © 2008 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.<br />