This document provides an overview of Lync Server, Microsoft's unified communications platform. It discusses the history and evolution of Lync Server from its predecessor Office Communications Server. Key technical aspects of Lync Server are introduced, including the Central Management Store, Call Admission Control, and Media Bypass. The document also briefly outlines potential future directions for Lync Server, such as expanded mobile clients and integration with Skype.

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

4. History

5. Industry recognition

6. Implementation approaches

7. Technical differentiators from Office Communications Server (OCS)

8. Setup and deployment

9. Introducing:

10. The Central Management Store (CMS)

11. Call Admission Control (CAC)

12. Media Bypass

15. The new name for OCS

16. An IP-PBX or traditional PBX replacement

17. A new breed of software-based telephony

18. Fully immersed within your PC (or Mac) desktop user experience – Office, SharePoint & Lync Client

21. Video calls

22. IM and presence

23. Mobility (including IM, presence and single-number reach)

24. Collaboration (desktop/file sharing, group chat and *dial-in conferencing)*Office Communications 2007 R2

26. Survivable Branch Appliance – a purpose-built appliance for branch deployments

27. Call Admission Control (CAC) – for the prevention of VoIP over subscription

28. Enhanced 9-1-1 (NA only) – CU1 delivers location functionality

30. 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

31. Technical differentiators from OCS

32. 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

34. Export to Topology Builder (.tbxml)

35. Topology Builder

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. 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)

39. The CMS data is held within a SQL database

40. Centralises the administration of all Lync Server roles (including Edge servers)

41. There is a minimum requirement of 2 x CMS databases - 1 x master (RTC) and 1 x replica (RTCLOCAL)

42. RTC and RTCLOCAL databases are replicated

44. CAC bandwidth policies can be set to control

45. Audio - max bandwidth (kbps) assigned for all/individual sessions

46. Video - max bandwidth (kbps) assigned for all/individual sessions

47. Policies are applied between sites, where multiple network subnets can be associated

49. This is achieved by negating the need for transcoding between the Lync client or phone and the voice gateway

50. In this scenario the G.711 voice codec is used, instead of RTAudio

53. *iPhone aka “iLync”

54. *Windows Phone 7

55. BlackBerry – now available BES v.5.0 SP3

56. Nokia

58. Single number reachETA late 2011

59. Lync for XBOX “videoKINECT” ETA late 2011

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

61. Resources

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.