1 / 35

UNC305 Conferencing: Microsoft Lync Server 2010

UNC305 Conferencing: Microsoft Lync Server 2010 . Tim Carr Program Manager Microsoft Corporation. Made in Switzerland!. Lync Server voice-apps (dial-in conferencing, Response Group Service, Announcement Service, Call Park) & Attendant Console. 60 minutes until BBT (Berlin Beer Time).

aradia
Télécharger la présentation

UNC305 Conferencing: Microsoft Lync Server 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UNC305Conferencing: Microsoft Lync Server 2010 Tim Carr Program Manager Microsoft Corporation

  2. Made in Switzerland! • Lync Server voice-apps (dial-in conferencing, Response Group Service, Announcement Service, Call Park) & Attendant Console

  3. 60 minutes until BBT (Berlin Beer Time)

  4. What you’ll see & learn today • Demos of the new conferencing features that make conferencing easier & more reliable • Conferencing Architecture and Call Flows • Capacity, Topology, Scale, and Coexistence considerations Deployment and Migration: hopefully you attended Thomas Binder’s UNC301 demo session! If not, get the recording… Decoder-ring • W14 = Lync and Lync Server 2010 • W13 = Office Communicator and Communications Server 2007 R2 • W12 = Office Communicator and Communications Server 2007

  5. </boring Meta>

  6. Conferencing & Collaboration Roadmap • Office Communications Server 2007 R2 / “13” • Communicator • Audio Conferencing • Desktop Sharing • Live Meeting • Audio conferencing • Desktop & Application Sharing • PowerPoint Presentations • Whiteboard • Polling, Q&A, etc. • Microsoft LyncServer 2010 / “14” • Lync • Richer Audio Conferencing • Desktop & Application Sharing • PowerPoint Presentations • Whiteboard • Polling • Live Meeting • Available during migration to “14” • Use for very large meetings

  7. Design Tenets • SIMPLE “It just makes sense” • One click scheduling • One click join from meeting reminder or invite • Two click sharing • RELIABLE“It works all the time” • Strong investments in reliability for voice, video, data • Improved notifications – voice quality warnings, lobby • Improved diagnostics for admins • ESSENTIAL “It increases my productivity.” • Collaboration is a natural extension of Voice and IM • Valuable tools that make online meetings critical • Browser based client allows cross platform collaboration

  8. Web Conferencing Rich collaboration Ad-hoc conferencing Scheduled meetings demo

  9. Web Conferencing Architecture Audio Video Conferencing Server Front End Server Focus AV MCU Focus Factory Backend SQL DB Server Web Components (IIS) IM Conferencing MCU Conferencing Database Join Launcher Web Conferencing MCU Reach Server App Sharing Conferencing MCU ProcessBoundary Web Application Audio Conferencing Machine Boundary

  10. Web Conferencing Flow: Scheduling & Joining SQL Backend SQL 5 Conferencing Server Factory App Sharing Conf MCU 2 4 SQL C3P/HTTP IM Conf MCU C3P/HTTP Focus Factory Focus 6 Web Conf MCU 1 CCCP/SIP CCCP/SIP 3 7 AV Conf MCU Server-side Client-side (S)RTP Scheduling Client Lync Client PSOM 8 SIMPLE/SIP RDP/RTP

  11. Conferencing User Model • Capacity Planning Guide - http://technet.microsoft.com/lync/library • Why is the user model important to you? • …because it generates the basis for what maximums we test & therefore what maximums we support • Max numbers for Lync Server 2010 • 80,000 users max per pool; back-end (BE) is gating factor • 10,000 users max per front-end (FE) server • Max 250 participants in a conference • Updated 2010 capacity planning tool coming soon…

  12. 2 Large Scale Topologies: Enterprise Edition (EE) Audio-Video Mixing Control Units (aka AVMCUs) split out: up to 15 servers in a pool AVMCUs running on FE servers (not split out): up to 10 servers in a pool Ideal for Medium size business Regional Deployment Scalability 5,000 users per FE, max 10k per pool Up to 10 FEs per pool (8 + 2 HA) At least 2 FEs required (+1 for HA) • Ideal for • Large enterprise • Data center deployment • Scalability • 10,000 users per FE, max 80k / pool • Up to 10 FEs per pool (8 + 2 HA) • … plus, 5 AVMCUs per pool (4 + 1 HA) HA = high availability

  13. 1 Smaller Scale Topology: Standard Edition (SE) • Ideal for • Proof of concept • Large branch office • Scalability • Up to 4,000 users on a single server (no HA)

  14. For more on Voice Architecture & HA planning • … go see UNC303 session • “Voice Architecture and Planning for High Availability” • Thursday (tomorrow), 1430h, Hall 7.1c Paris 2

  15. Client-side Coexistence: 2007 R2 and 2010 • Scenario: Joining new 2010 meeting, 2007 R2 client installed • After clicking join link, users are presented with webpage, have at least two options for full web-conferencing experience: • Download & install Attendee Lync client directly from Microsoft -- no license or admin privs required! • Web-client experience (Silverlight required) – audio over 2007 R2 Thanks Dennis!

  16. Audio Conferencing Drilldown

  17. Meeting types(from Gartner report) • Reservationless calling • 25 or fewer participants • One-off or Weekly staff, ½ - 2 hrs, usually with Web attached, intl. participation by company • Operator assisted • Roll call, polling • 25-100 participants Biweekly/monthly with Web attached • Managed event, external • Transcription, high touch, large audiences • 100+ participants, Quarterly, Web attached 85% <10% <5% Our target Stay on ACPs • Features needed for small/med.meetings • Simple and reliable join • Best in class UX on both the PSTN and soft client side

  18. New Audio Conferencing Features in W14 • Provide all the features needed to handle small/mid-size meetings • DTMF controls • Entry/exit announcements • Make join simpler and more reliable • Lobby support for restricted meetings • Name recording for unauthenticated users • PIN improvements: default no expiration, e-mail notification, increased visibility • Provide a best in class UX on both the PSTN and soft client side • Control entry/exit announcements at schedule time and during conference • Recording of reservationless meetings

  19. Audio Conferencing Focused on the phone Scheduling, joining, in-conference experience demo

  20. Audio Conferencing Architecture Audio Video Conferencing Server Front End Server Focus Web Components (IIS) AV MCU Focus Factory Join Launcher Backend SQL DB Server IM Conferencing Server Reach Server Conferencing Database Web Conferencing Server Dial-in Conferencing Page App Sharing Conferencing Server Conference Auto Attendant Conference Announcement Service Personal Virtual Assistant Machine Boundary Group Virtual Assistant Process Boundary Web Application Audio Conferencing

  21. Audio Conferencing Flow CAA SQL Backend SQL Conferencing Server Factory C3P/SIP CAS SQL C3P/ HTTP 6 2 PVA/GVA C3P/SIP Focus Factory Focus C3P/SIP 5 4 7 C3P/SIP 3 AV Conf Server C3P/SIP Server-side Client-side 1 PSTN phone Scheduling Client Mediation Server (S)RTP Via PBX/GW SIP

  22. Phone Experience: Languages +1 206 … Your Conference Conference Announcement Service +1 425 ... Pick English English Pick English Group Virtual Assistant Group Virtual Assistant Conference Attendant Personal Virtual Assistant Personal Virtual Assistant Pick French +33 791 ... French Group Virtual Assistant Personal Virtual Assistant

  23. Problem: All dial-in access numbers hosted by Conference Attendant (CAA) are globally available … and a user can call 2007R2 CAA trying to join a conference hosted on W14 pool … but OCS 2007R2 CAA cannot handle the new W14 lobby feature (it disconnects the call) Solution: “Inter-pool transfer” transfers the call to W14 CAA after conference ID has been entered, preserving language selection Requires cumulative update #5 or higher on OCS 2007 R2 front-ends W14 CAA will only accept transfers from another CAA, will only transfer if meeting homed in a different W14 pool Coexistence with OCS 2007 R2: Inter-pool Transfer

  24. Top takeaways • True Unified Client – one client handles both Web and Audio Conferencing • Improved phone-conferencing experience: move 85% of your ACP conferences to Lync Server “14”, instantly save money! • Flexible topologies supported to meet your needs • Basic understanding of the components in the path of conference schedule & join, and the order of operations

  25. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

  26. © 2010 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.

  27. Conferencing User Model • Client distribution per meeting type • Scheduled (60%): 75% Lync 2010, 20% Web App, 5% Lync Attendee • Adhoc (40%): 65% Lync 2010, 30% older OC clients, 5% web app • 5% of users in conferences during working hours • 80k pool = 4k users in conferences simultaneously • “Busy Hour” – 75% of an 8-hour day’s conferences happen in 4 hours • 50% users internal & authenticated; 25% remote & authenticated; 15% anon.; 10% federated • Media mix • Audio: works out to 25% dial-in, 65% VoIP, 10% no audio • Collab: 50% have app sharing, 50% have IM, 20% have data collab (PowerPoint or whiteboard), 20% have video

  28. Conference JoiningAccess Control – Wave 14, with lobby

  29. Deploying Web Conferencing • Plan Server Roles & Capacity • Consider Voice and Web Conferencing scale as part of FE planning • 250 active users w/sharing (5 per conference) per machine • Consider Network usage • Plan/improve network capacity based on voice/video/sharing usage • Plan client features • Plan in-band settings to enable/disable features per need/capacity • Edge server required for outside users • Roll out Cumulative Updates • Apply CUs to W13 Front Ends, Communicator and Live Meeting to current desktops Deploy Servers • Step-wise “swap pool” migration from previous server version to CS “14” • Migrate Users • Users continue with current clients until ready for next step • Can migrate previous content using resource kit tools • Deploy clients • Push clients, or use version check for user-download (on-prem or WU)

  30. Deployment Considerations • Pre-requisites for migration • Users migrated to W14 pool • Users get new Communicator • Apply necessary Cumulative Update (CUs) • Latest CU for Outlook Add-In and Live Meeting to all users • Latest CU for W12 and W13 • Latest CU applied to all W13 frontend servers • Move users to W14 Pool • Users have either W12 or W13 clients • No CVC check • Communicator Attendee and Web App • Training/support when first pool rolls out • Web Access Server W13 • Leave as-is for web based IM/P support • New clients: • Users start migrating to use W14 clients and admins support them • MVMPOP • W12 and W13 clients still supported • CVC check to force upgrades

  31. Migration – Scheduling • Users migrated to CS W14 pool • Users get new Communicator client • Live Meeting • User has W13 addin only • Conferences and Meetings scheduled with W13 addin continue as normal • Existing meetings on calendar continue to work • User now has both W13 and W14 addins installed, but sees only W14 addin • New meetings use W14 HTTPS links • Can’t schedule new on-prem Live Meetings • Works as expected

  32. Migration - Join • Users migrated to W14 pool • Users get new Communicator client • Migrated meetings continue to behave like W13 meetings: • No Lobby • Federated users • Existing access numbers and conference IDs migrate and work as expected • New meetings: • Everyone joins with HTTPS link • The Launch page: • Launches Lync“14”, or Lync Attendee “14” if installed • Otherwise, auto-join using Lync Web App • Admin setting to allow CONF: join with previous client versions • Access numbers: • Anyone can call any access number to join any meeting • Users get a new conference ID

  33. Deploying PSTN Dial-in • Plan Numbers and Capacity • Add DID numbers and PSTN trunk capacity • Configure Dial Plans • Configure dial-in conferencing regions • Deploy Gateways • PSTN gateways or configure SIP trunking • Configure access numbers • Globally or per site*, order of access numbers per conference region (PowerScript cmdlet only)* • Configure DTMF commands* • Globally or per site • Configure PIN security • Complexity, expiration, etc. • Enable users for PSTN dial-in • Populate unique phone numbers for users (msRTCSIP-Line property) • Generate PIN and send welcome email via PowerShell script* * New in CS 14

  34. Migration Steps • Coexisting phase: months or years • Decommissioning W13 pools • Getting to coexistence state • Deploy latest CU to all OCS 2007R2 FEs • Move data from OCS 2007R2 WMI to W14 SQUID using PowerShell cmdlets • Move users to W14 pool (their meetings are automatically migrated also) • W13 access numbers still around • W14 access numbers starting to be added • Any user can call any access number to join any meeting(interpool transfer) • Some meetings have old invites with W13 access numbers • New meetings have W14 access numbers • Migrate COs so that they point to a W14 pool instead of the W13 pool, using PowerShell cmdlets • Meeting invites that still have W13 access numbers will now be handled by CAA14 • Decommission W13 pool

More Related