Adam Jacobs Lync MVP

2. Introduction to Lync Server Adam Jacobs Lync MVP @adamjacobs http://imaucblog.com adam@imaucblog.com

3. Agenda • What is Lync Server? • History • Industry recognition • Implementation approaches • Technical differentiators from Office Communications Server (OCS) • Setup and deployment • Introducing: • The Central Management Store (CMS) • Call Admission Control (CAC) • Media Bypass • Futures

4. What is Lync Server?

5. What is Lync Server? • Lync not LINQ • The new name for OCS • An IP-PBX or traditional PBX replacement • A new breed of software-based telephony • Fully immersed within your PC (or Mac) desktop user experience – Office, SharePoint & Lync Client • The heart of Microsoft’s UC stack

6. Future of Communications Communications Today InstantMessaging (IM) Video Conferencing Web Conferencing E-mail and Calendaring AudioConferencing Voice Mail Telephony Telephony and Voice Mail InstantMessaging Unified Conferencing: Audio, Video, Web E-mail andCalendaring User Experience User Experience User Experience User Experience User Experience User Experience User Experience Unified Inbox & Presence Authentication Administration Storage Compliance Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage Authentication Administration Storage

7. Then… Microsoft® Office Communications Server • A PBX companion – high level deliverables include: • Voice calls via existing handsets (RCC) and Communicator/“Optimised Devices” (EV) • Video calls • IM and presence • Mobility (including IM, presence and single-number reach) • Collaboration (desktop/file sharing, group chat and *dial-in conferencing) *Office Communications 2007 R2

8. And now… Microsoft ® Lync TM • A PBX replacement – via added functionality: • Enhanced resilience - without the need for h/w load balancing (web workloads still require HLBs) • Survivable Branch Appliance – a purpose-built appliance for branch deployments • Call Admission Control (CAC) – for the prevention of VoIP over subscription • Enhanced 9-1-1 (NA only) – CU1 delivers location functionality • Superior conferencing - voice announcements and an integrated client! (no Live Meeting client or Outlook Conferencing add-in)

9. Industry recognition “OCS…is certainly going to shake up the market.” 36% companies surveyed are already using OCS as UC client, more than IBM, Cisco and Public IM clients. “If you didn’t think Microsoft was serious about voice communications before, you better believe it now.” “Magic Quadrant for Unified Communications,” July 28, 2010.

10. Implementation approaches Identify PBX integration opportunities – software upgrades and/or a vendor application gateway. Consult your PBX vendor and visit the *UCOIP Introduce Conferencing functionality and cut existing costs (measure telephony capacity first) – my workplace saved £60k per annum! Leverage existing PBX investment and introduce Communicator concepts via RCC Consult your PBX vendor and visit the *UCOIP, identify integration opportunities. Alternatively you can deploy a side-by-side voice gateway Telephony growth supported by EV with Lync chosen as standard for strategic replacement Initially choose mix legacy, RCC and EV for agile workers (project teams, senior executives and IT) Alternatively it could be the right time to replace your existing PBX for Lync – how many times has this asset been written off?  For greenfield deployments a voice gateway could be used, consult the *UCOIP for supported hardware *Unified Communications Open Interoperability Program - here

11. Technical differentiators from OCS

12. Key Lync Roles and Servers • *Central Management Store (CMS) • covered in subsequent slide Back End Server Lync database Archiving Server collects IM and Meeting content Monitoring Server collects call quality and CDR related information Director Internally, routes clients to corresponding home server Externally, reverse proxies authentication requests Front End Server Handles authentication/registration, address book, IM, Conferencing & Response Groups Mediation Server translates signalling and media (where bypass is not used) and routes to PSTN via gateway, IP-PBX or SIP trunk Edge Server used for external Communication & Collaboration (without the need for VPN) *Survivable Branch Appliance (SBA) a purpose-built Lync appliance, typically utilised for branch deployment A/V Conferencing Server as the name suggests (can be collocated with Front End server or deployed separately) *Introduced with Lync

13. Setup and deployment changes worth mentioning • Planning Tool • Export to Topology Builder (.tbxml) • Topology Builder • Tool used for .tbxml import, topology setup, modification and validation prior to deploying first server and publishing within the Central Management Store (CMS) • Mediation role can now be collocated with front end role = minus 1 server • Essentially one Standard Edition Server could support Enterprise Voice, IM, Presence and Conferencing for up to 5000 users! • 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)

14. Central Management Store (CMS) • Replaces Active Directory for most configuration storage (phone numbers still held within AD) • The CMS data is held within a SQL database • Centralises the administration of all Lync Server roles (including Edge servers) • There is a minimum requirement of 2 x CMS databases - 1 x master (RTC) and 1 x replica (RTCLOCAL) • RTC and RTCLOCAL databases are replicated • Resilient architecture – Front End Server CMS (replica) will continue to function where connectivity is lost to the master

15. Call Admission Control (CAC) • Put simply CAC is the bandwidth management service built into Lync Server • CAC bandwidth policies can be set to control • Audio - max bandwidth (kbps) assigned for all/individual sessions • Video - max bandwidth (kbps) assigned for all/individual sessions • Policies are applied between sites, where multiple network subnets can be associated • 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

16. Media Bypass • Media bypass reduces the load on your Mediation servers (allowing support for up to 5000 users, where Front End and Mediation roles are collocated) • This is achieved by negating the need for transcoding between the Lync client or phone and the voice gateway • In this scenario the G.711 voice codec is used, instead of RTAudio • Recommended gateway vendors include AudioCodes, Dialogic, NET and Ferrari

17. Futures

18. Lync Mobile • Mobile clients are expected for: • *iPhone aka “iLync” • *Windows Phone 7 • BlackBerry – now available BES v.5.0 SP3 • Nokia • Android • *NB • Functionality will include: • One-click to join conference • Single number reach • ETA late 2011

19. Lync for XBOX “videoKINECT” ETA late 2011

20. Lync Server + Skype = ? Jamie Stark Lync Server Product Manager

21. Resources

22. © 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.