Microsoft Lync Server 2010: Administering Lync Server Deployment

1. EXL321 Microsoft Lync Server 2010: Administering Lync Server Deployment Anand Lakshminarayanan Cezar Ungureanasu Microsoft

2. Session Objectives and Takeaways • Session Objectives: • Dive into the new Lync Manageability architecture, supported topologies and key pain points addressed • Walk through the Lync Server 2010 administration tools with demos. • Key Takeaways: • I understand the Topology options available • I understand the key issues addressed by the Lync Server 2010 manageability architecture. • I have seen the new Lync admin tools in action • I have pointers to more information via related sessions & content online

3. Lync Server 2010 Manageability Lifecycle Lync 2010 Planning tool+ Planning guides+ SCOM 2007 R2 pack+ Monitoring server+ Synthetic transactions* Topology Builder* Setup (Local)* Migration tools Lync Server 2010 Control Panel* Lync Server 2010 PowerShell* * new in LS 2010 + significant enhancements in LS 2010

4. Lync Server 2010 Topologies & Manageability Architecture

5. Feedback on OCS 2007/R2 Topologies • Topology: complex esp. with deploying multiple workloads • Servers: too many stand-alone server roles: Communicator Web Access, mediation servers, web components • Virtualization: too limited in its constraint to IM/presence • Hardware load balancer: acquisition cost too high; hard and expensive to deploy, configure, and manage • Multi-site deployments: esp. geo-dispersed data centers • Traffic: difficult to separate internal and external traffic • Certificates: difficult to configure and manage

6. Supported Topologies in Lync Server 2010 Servers Optional Servers Topologies Front end Mediation Standard Edition Back end Director Archiving Monitoring Enterprise Edition SBA Group Chat SCOM Exchange UM Edge AV Conf > 10,000

7. Enterprise Edition Reference Topology Single Datacenter upto 100,000 users This example 20,000 users, HA, 14 servers 1429 users/server

8. Virtualization • Server - What’s supported? • Virtualization of all Lync Server roles • SQL, Exchange, Active Directory virtualization (as per product guidelines) • Hyper-V 2008 R2 (2008 not supported), VMWare • Standard Edition server • Server - Not Supported • Branch office/Gateway only/Mediation server+gateway • Live migration of VMs via SCVMM (ongoing calls/sessions will be dropped) • Mixed environments (some roles virtualized and others not) • Clients • App-V supports all client modalities except RCC • VDI supports IM, presence, desktop sharing; No softphone audio/video support. Use IP Phones. • Other • Pilot has no HLB or DNS LB. Production – Needs HLB. • Perf reduction (around 50%) compared to non-virtualized topology

9. Central Management • Top customer issues before Lync Server 2010 • Configuration was spread across Active Directory, SQL, local store • No Edge access to Active Directory, manual configuration needed • No way to validate planned changes before they were deployed • Configuration out-of-sync over multiple stores, sites, geographies • With Central Management in Lync Server 2010 • Schematized definitions (XSDs) of topology and configuration • All configuration documents managed by central SQL database • All changes (writes) happen to the central management store • Read-only copies are replicated to all topology notes (incl. Edge) • Validate changes before commit, eliminate misconfiguration

10. Central Management Store (CMS) Configuration Change - Workflow CMS LS 14 server1 2 4 1 3 5 Administrator makes changes through Lync Server PowerShell/UI Interfaces. Master Replicator generates a snapshot of the new configuration. File Transfer Agent replicates the snapshot to all computers in the deployment . Local Replicator Agent notified of new snapshot available. Loads it into the database and reports back status. Status is transferred back to master and replication status is updated.

11. Topology Model • Deployment is a collection of Sites • Sites are a collection of Pools • Pools host Services (ex: IM, conferencing, voice workloads) • Pools home Users

12. Policy Scopes and Resolution • Configuration • Data and settings needed by a component or service • Applies to all requests equally • “Knobs” to tune • Ex: AddressBook Configuration • Policy • Data needed to process a request • Implies lookup and resolution • Ex: VoicePolicy, ArchivingPolicy • Policy Scopes: • Global • Site • Pool • User • Policy Resolution Order • Closest policy to the user wins • User > Pool > Site > Global • Examples • New-CsVoicePolicy –Identity “site:redmond” –AllowCallForwarding $false • New-CsExternalAccessPolicy –Identity “Global”–EnablePublicCloudAccess $true

13. Lync Server 2010 Administration tools

14. Feedback on OCS 2007/R2 Administration • MMC UI – pop-up property dialogs to configure. Nested pages and detailed settings. • Automation - make it simpler to manage users, policies and entitlements through automation interfaces. • Multiple places and levels to configure settings was confusing, need more config validation • Need better delegation model for administration tasks

15. Lync Server Control Panel (LSCP): What is it? • A web-based, scenario-driven management GUI • Based on Silverlight 4 and PowerShell • Target most relevant PowerShell delivered features / settings • GUI tool includes • Easy Navigation • Easy searches (Save & reuse queries) • Effective policy view • Voice Routing support built-in • No cascading property sheets • Role based access support • And more… • Replaces MMC-based snap-in used in previous releases

16. Voice Configuration management with Lync Server 2010 demo

17. Lync Server 2010 PowerShell • New automation interface for Lync Server 2010 • Easily manage Lync Server 2010 users and entitlements • Script your bulk changes • Automate regular system maintenance • Familiar admin experience • Active Directory, Exchange, SQL Server, all provide PowerShell for administration • Leverage scripting knowledge across Microsoft stack • Implement cross-product scripts/processes • RBAC (Role based access control) • Delegate administration tasks • Out-of-box set of roles (fixed)

18. Managing Users with Lync Server 2010 demo

19. PowerShell Features Configuration Management Server Roles Global/Site level Devices Device updates Common Area Phones Analog Devices User Management Search for users Enable/Disable for Lync Server Assign Lync Server policies Policy Management Voice, IM/P Conferencing Federation/PIC Synthetic Transactions Test Phone Calls SIP activity Simple Conferencing Deployment Certificates management Setup steps Topology Management Clients Client Versions management In-band settings Voice Apps Response Group Conferencing Attendant Bandwidth Management Partner Apps Trusted Connectivity Contact Objects Lifecycle management

20. End-to-end Scenario Validation with Lync Server 2010 demo

21. Delegation of Administration 1 Management Web Service 2 Authorization 4 3 5 Administrator is authenticated – PowerShell 2.0 fan in remoting Restricted PowerShell session created for the user. It contains a subset of the CS cmdlets, calculated based on the roles the user is a member of. Administrator executes a management task. Authorization checks - cmdlet and target of the operation are within scope. CS Management Web Service executes the call.

22. WHO can do WHAT and WHERE What Who Where AD Group ConfigurationWrite Scope User Write Scope Role Admin Role <Task List> -CsCmdlet1 -CsCmdlet2 -CsCmdlet3 Role Entry Cmdlet: Param1 Param2 Param3 Role Entry Cmdlet: Param1 Param2 Param3

23. Role Based Access Control with Lync Server 2010 demo

24. Putting it all together • Central Configuration Management • PowerShell with Delegation • Control Panel UI CMS LS 14 server1 2 4 3 5 Management Web Service 1 1 Authorization

25. Central Configuration management with Lync Server 2010 demo

26. Session Objectives and Takeaways • Session Objectives: • Dive into the new Lync Manageability architecture, supported topologies and key pain points addressed • Walk through the Lync Server 2010 administration tools with demos. • Key Takeaways: • I understand the key issues addressed by the Lync Server 2010 manageability architecture. • I understand the Topology options available • I have seen the new Lync admin tools in action • I have pointers to more information via related sessions & content online

27. Required Slide Speakers, please list the Breakout Sessions, Interactive Discussions, Labs, Demo Stations and Certification Exam that relate to your session. Also indicate when they can find you staffing in the TLC. Related Content • EXL 319 Microsoft Lync 2010 – Setup, Deployment, Upgrade & Coexistence • EXL323 Setting Up and Deploying Microsoft Lync Server 2010 Edge Servers • EXL318 Monitoring Microsoft Lync 2010 Deployments • EXL315 Microsoft Lync 2010: Core Voice Planning and Deployment • EXL372-INT What do you want to know about Management and Administration of Lync Server 2010? • EXL371-HOL Deploying a Microsoft Lync 2010 Architecture • EXL372-HOL Managing Migration and Co-Existence between Microsoft Lync Server 2010 and Microsoft Office Communications Server 2007 R2 • EXL377-HOL Managing Microsoft Lync Server 2010 Using Windows PowerShell and the Lync Server Control Panel • C4E254 Exam Cram on Microsoft Lync Server 2010 IT Professional Series: Exam 70-665 • Find Me Later At… Exchange and Lync Booth

28. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Links • Microsoft Lync 2010 Administration guide • Microsoft Lync 2010 Enterprise Edition Deployment guide • Microsoft Lync Server 2010 Planning Guide • Microsoft Lync Server 2010 TechNet Videos

29. Resources • Connect. Share. Discuss. http://northamerica.msteched.com Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn

30. Complete an evaluation on CommNet and enter to win!

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