230 likes | 460 Views
Microsoft ® Lync™ Server 2010 Management and Admin Experience Module 05. Microsoft Corporation. Session Objectives and Takeaways. Session Objectives:
E N D
Microsoft® Lync™ Server 2010Management and Admin Experience Module 05 Microsoft Corporation
Session Objectives and Takeaways • Session Objectives: • Describe the implications of our investments in Microsoft® PowerShell™ and delegation (Role-based Access Control (RBAC)) for Lync Server 2010 • Navigate the Lync Server 2010 Control Panel, the graphical administrative tool for this release • Takeaways: • Understand our management experience investments in Lync Server 2010 • Describe the Lync Server 2010 management experience
Agenda • Experience: Lync Server Control Panel and PowerShell • Demos: Management Experience • Experience: RBAC • Demo: RBAC
Management Experience Investments • PowerShell Foundation for Administration • All management functions run in PowerShell • Full PowerShell 2.0 capabilities leveraged for Lync Server 2010 • New Silverlight®-based Graphical User Interface (GUI) tool • Lync Server Control Panel • Addresses key pain points from OCS 2007 R2 • No Microsoft Management Console (MMC) for Lync Server 2010 • RBAC • Supported throughout Lync Server Control Panel and PowerShell • Built-in and customer-defined roles available
Lync Server Control PanelWhat Is It? • A web-based, scenario-driven management GUI for Lync Server 2010 • Based on Silverlight 4 and PowerShell • Targeted to expose most relevant PowerShell delivered features and settings • GUI tool includes • Discoverable dialogs • Easy and fast searches • Effective policy view • Voice dial-plan support built-in • No cascading property sheets • And more… • Replaces MMC-based snap-in used in previous OCS releases
Why Lync Server Control Panel? Usability studies and customer feedback: • MMC UI in OCS 2007 R2 is difficult to navigate/deploy/manage • Multiple places/levels to configure the same thing • Risk of out-of-sync configurations/validation prior to changes not adequate • Management tasks spread across different tools (Active Directory® Administrative Center (ADAC), OCS, MMC, etc.)
Lync Server Control Panel Addresses Key Customer Feedback • No need for multiple tools • Response Group management integrated • Route Helper Tool (OCS 2007, OCS 2007 R2) integrated • External access management consolidated • All policies are reflected in single tool • Easy to see and understand user’s effective policy • Navigation cleaner and easier • “Bread crumbing” provides context on task • Queries can be saved and re-used • Consistent tools, look, and feel throughout UI
Topology Model Global Microsoft Lync Server 2010 Deployment is a collection of Sites • Sites are made up of Pools • Pools host: • Services (such as Instant Messaging (IM), Conferencing, and voice over internet protocol (VoIP)) • Users
Policy Scopes and Resolution • Configuration: • Data/settings needed by a component/service. Applies to all requests equally • Policy: • Data needs to process a request. Implies lookup and resolution • Policy Scopes: • Global • Site • Pool (or “service”) • User • Policy Resolution Order: • Closest policy to the user wins • User > Pool > Site > Global
Microsoft Lync Server 2010 PowerShell Key pain point: Difficult to automate tasks such as managing user policies and entitlements in a consistent way Solution: • PowerShell foundation for Administration • PowerShell eases automation for administrative tasks • Consistent PowerShell administration experience • Consistency with Exchange administration
Microsoft Lync Server 2010 PowerShell (Cont’d) Configuration Management Server Roles Global/Site level Device Management Device configuration Common Area phones Analog devices User Management Search for users Enable/Disable for OCS Assign OCS policies Policy Management ArchivingPolicy ExternalAccessPolicy VoicePolicy Synthetic Transactions Test phone calls SIP registrations Simple conferencing Deployment Management Certificates management Setup steps Topology management Voice Applications Response Group Conferencing Attendant Bandwidth management External applications
Why Role-based Access Control? • Security best practice • Enables least-privilege access for admin roles • Greater administrative productivity • Focus each organizational role on right tasks • Assigning right task to right person drives total cost of ownership (TCO) improvements across organization • Consistent with Exchange Server 2010 administration approach
How is RBAC Implemented? • User/Group from Active Directory® Domain Services (AD DS) • Role: List of cmdlets and scripts • Scope: Set of objects upon which cmdlets in role can operate • Role Assignment: Defines who can run what and where • Who: User or Group • What: Set of tasks in the role definition • Where: Scope
Delivering a Leading Communications Management Experience Summary • Administration is a major investment for Lync Server 2010 • Lync Server Control Panel streamlines and eases administration • PowerShell enables automation across entire infrastructure • RBAC supports security best practices and organizational efficiency
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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. This document may contain information related to pre-release software, which may be substantially modified before its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.