Your SlideShare is downloading. ×
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Introduction to Lync Server 2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Introduction to Lync Server 2010

5,521

Published on

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

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

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
5,521
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
333
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1.
  • 2. Introduction to Lync Server
    Adam Jacobs
    Lync MVP
    @adamjacobs
    http://imaucblog.com
    adam@imaucblog.com
  • 3. Agenda
    • What is Lync Server?
    • 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
    • 13. Futures
  • What is Lync Server?
  • 14. What is Lync Server?
    • Lync not LINQ
    • 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
    • 19. The heart of Microsoft’s UC stack
  • Future of Communications
    Communications Today
    E-mail and
    Calendaring
    Web
    Conferencing
    Video
    Conferencing
    InstantMessaging (IM)
    AudioConferencing
    Telephony
    Voice Mail
    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
  • 20. Then…
    Microsoft®
    Office Communications
    Server
    A PBX companion – high level deliverables include:
    • Voice calls via existing handsets (RCC) and Communicator/“Optimised Devices” (EV)
    • 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
  • 25. 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)
    • 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
    • 29. Superior conferencing - voice announcements and an integrated client! (no Live Meeting client or Outlook Conferencing add-in)
  • 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.
  • 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
  • 33. Setup and deployment changes worth mentioning
    • Planning Tool
    • 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)
  • 38. Central Management Store (CMS)
    • Replaces Active Directory for most configuration storage (phone numbers still held within AD)
    • 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
    • 43. Resilient architecture – Front End Server CMS (replica) will continue to function where connectivity is lost to the master
  • Call Admission Control (CAC)
    • Put simply CAC is the bandwidth management service built into Lync Server
    • 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
    • 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
  • 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)
    • 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
    • 51. Recommended gateway vendors include AudioCodes, Dialogic, NET and Ferrari
  • Futures
  • 52. Lync Mobile
    • Mobile clients are expected for:
    • 53. *iPhone aka “iLync”
    • 54. *Windows Phone 7
    • 55. BlackBerry – now available BES v.5.0 SP3
    • 56. Nokia
    • 57. Android
    *NB
    Functionality will include:
    • One-click to join conference
    • 58. Single number reach
    ETA 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.

×