Microsoft Lync Configuration Trainer Handbook

7/22/2019 Microsoft Lync Configuration Trainer Handbook

1/774

O F F I C I A L M I C R O S O F T L E A R N I N G P R O D U C T

10533A

Deploying, Configuring, and AdministeringMicrosoft Lync Server 2010


2/774

ii Deploying, Configuring, and Administering Microsoft Lync Server 2010

Information in this document, including URL and other Internet Web site references, is subject to change

without notice. 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, e-mail address, logo, person, place or event is

intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the

user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in

or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical,

photocopying, recording, or otherwise), or for any purpose, without the express written permission of

Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property

rights covering subject matter in this document. Except as expressly provided in any written license

agreement from Microsoft, the furnishing of this document does not give you any license to these

patents, trademarks, copyrights, or other intellectual property.

The names of manufacturers, products, or URLs are provided for informational purposes only and

Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding

these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a

manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links

may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not

responsible for the contents of any linked site or any link contained in a linked site, or any changes or

updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission

received from any linked site. Microsoft is providing these links to you only as a convenience, and the

inclusion of any link does not imply endorsement of Microsoft of the site or the products contained

therein.

2011 Microsoft Corporation. All rights reserved.

Microsoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

All other trademarks are property of their respective owners.

Product Number: 10533A

Part Number: X17-52341

Released: 5/2011


3/774

Deploying, Configuring, and Administering Microsoft Lync Server 2010 iii


4/774

iv Deploying, Configuring, and Administering Microsoft Lync Server 2010


5/774

Deploying, Configuring, and Administering Microsoft Lync Server 2010 v


6/774

vi Deploying, Configuring, and Administering Microsoft Lync Server 2010


7/774

Deploying, Configuring, and Administering Microsoft Lync Server 2010 vii


8/774

viii Deploying, Configuring, and Administering Microsoft Lync Server 2010


9/774


10/774

x Deploying, Configuring, and Administering Microsoft Lync Server 2010

AcknowledgementsMicrosoft Learning would like to acknowledge and thank the following for their contribution towards

developing this title. Their effort at various stages in the development has ensured that you have a good

classroom experience.

Kelly McMahon Content DeveloperFor the past 10 years Kelly has been designing courseware and other technical communications for

Microsoft. She has developed training materials for a broad range of Microsoft technologies including

Microsoft Exchange, Microsoft Windows, Microsoft Dynamics, Microsoft SharePoint, and others. Her

focus is on creating comprehensive learning experiences for the IT Professional and Developer audiences.

In her spare time, Kelly is also pursuing an MBA with an expected graduation date of June 2011.

Anne Bockman Hansen Content DeveloperAnne has 15 years of experience in instructional design, technical writing, and project management. She is

experienced in designing curriculum for a wide variety of content areas, including

Microsoft Exchange Server, Microsoft SQL Server, Microsoft Windows Server, Microsoft SharePoint,

and Microsoft Office. Anne received a Masters of Science degree in Technical Communication from the

University of Washington College of Engineering in 1996. She lives in the country with her husband Barryand their 9-month-old twins, Anne and Barry.

Thom Foreman Subject Matter ExpertThom Foreman is an Infrastructure Consultant and Technical Trainer for Wadeware, based in Kirkland, WA,

with more than 12 years of experience in the IT industry. Thom performs real-world IT consulting

throughout the Puget Sound region and uses this experience to create Microsoft courseware and

instructional content, specializing in Microsoft Lync Server 2010, Microsoft Office

Communications Server 2007 R2, Microsoft Exchange Server 2007, and Exchange Server 2010. Thom has

worked on numerous Microsoft courses and training materials, including creating the Lync Server 2010

Ignite, Office Communications Server Ignite, and Office Communications Server R2 Voice Ignite labs, as

well as contributing to numerous other courses for the Unified Communications Team.

Brian Ricks Subject Matter ExpertSince 1993, Brian has been working in the IT field implementing Microsoft solutions. In 1999 he obtained

his first Microsoft Certified Professional (MCP) certification and in 2006 received the MVP award from

Microsoft in what is now Lync Server 2010. In 2009 Brian started BriComp Computers, LLC, where he

provides consulting services to companies large and small as an Architect and Subject Matter Expert for

infrastructure and Unified Communications. Brian holds many credentials, including MCP, Microsoft

Certified Systems Engineer (MCSE), MVP, and MBA. He resides in Gilbert, Arizona, with his wife and two

young boys ages 11 and 14.

Mark Stafford Technical ReviewerMark has been working in IT for well over a decade and has significant real-world experience running a

contact center on several different releases of the Lync Server 2010 product family. He has been awardeda Microsoft Certified Masters in Office Communications Server 2007 and Lync Server 2010. Mark has

varied professional interests including Unified Communications, application development, and business

intelligence. In his spare time, he helps raise his son Caelan and daughters Mia and Calista with his wife,

Janet.


11/774

Deploying, Configuring, and Administering Microsoft Lync Server 2010 xi

Contents

Module 1: Features and Architecture of Microsoft Lync Server 2010

Lesson 1: Features of Lync Server 2010 1-3

Lesson 2: Architecture and Server Roles 1-15Lesson 3: New Management Tools 1-24

Module 2: Deploying Microsoft Lync Server 2010

Lesson 1: Preparing for Deployment 2-3

Lesson 2: Reviewing the Design Process 2-18

Lesson 3: Deploying Lync Server 2010 2-21

Lab: Preparing the Environment and Deploying a

Lync Server 2010 Pool 2-31

Module 3: Configuring Users and Rights in Microsoft

Lync

Server 2010Lesson 1: Managing Lync Server 2010 3-3

Lesson 2: Role-Based Access Control 3-10

Lab: Configuring Users and Rights in Lync Server 2010 3-15

Module 4: Client and Device Deployment and Management

Lesson 1: Preparing for Client Deployment 4-3

Lesson 2: Deploying and Managing Lync 2010 Clients 4-8

Lesson 3: Preparing for Device Deployment 4-17

Lesson 4: Deploying and Managing IP Phones 4-24

Lab: Client and Device Management 4-32

Module 5: External User Access

Lesson 1: Edge Server Role 5-3

Lesson 2: Topologies for External User Access 5-7

Lesson 3: Preparing for External User Access 5-11

Lesson 4: Edge Server Deployment Process 5-22

Lab: Deploying External User Access 5-30

Module 6: Configuring Basic Enterprise Voice Functionality

Lesson 1: Features of Lync Server 2010 Enterprise Voice 6-3

Lesson 2: Preparing for Enterprise Voice 6-10

Lesson 3: Deploying Enterprise Voice 6-19

Lab: Configuring Basic Enterprise Voice Functionality 6-29


12/774

xii Deploying, Configuring, and Administering Microsoft Lync Server 2010

Module 7: Extending Enterprise Voice Functionality

Lesson 1: Configuring Enterprise Voice 7-3

Lesson 2: Introducing Call Park 7-9

Lesson 3: Introducing the Announcement Service 7-16

Lab: Implementing Enterprise Voice 7-22

Module 8: Microsoft Exchange Server 2010 SP1 Unified Messaging Integration

Lesson 1: Overview of Exchange Server 2010 SP1 Unified Messaging 8-3

Lesson 2: Prerequisites for Integrating Exchange

Server 2010 SP1 UM with Lync Server 2010 8-8

Lesson 3: Integrating Exchange Server 2010 SP1 UM

with Lync Server 2010 8-16

Lab: Integrating Exchange Server 2010 SP1 Unified

Messaging Integration with Lync Server 2010 8-25

Module 9: Implementing Response GroupsLesson 1: Overview of the Response Group Service and Its Application 9-3

Lesson 2: Response Group Service Components 9-8

Lesson 3: Response Group Service Management Tools 9-23

Lab: Configuring the Lync Server 2010 Response Group Service 9-29

Module 10: Conferencing in Lync Server 2010

Lesson 1: Introduction to Conferencing in Lync Server 2010 10-3

Lesson 2: Dial-In Conferencing in Lync Server 2010 10-14

Lesson 3: Managing and Administering Conferencing Policies 10-25

Lab: Conferencing Configuration and Deployment 10-32

Module 11: Monitoring and Archiving

Lesson 1: Describing the Archiving Service 11-3

Lesson 2: Describing the Monitoring Service 11-11

Lesson 3: Configuring Archiving and Monitoring 11-19

Lab: Configuring and Using Archiving and Monitoring

in Lync Server 2010 11-27

Module 12: High Availability and Disaster Recovery in Lync Server 2010Lesson 1: High Availability Options 12-3

Lesson 2: Tools for Backing Up and Restoring Lync Server 2010 12-14

Lesson 3: Critical Lync Server Data to Export and Import 12-18

Lesson 4: Critical Lync Server 2010 Data to Export and Import 12-23

Lab: Preparing for and Recovering from a Disaster 12-28


13/774

Deploying, Configuring, and Administering Microsoft Lync Server 2010 xiii

Module 13: Call Admission Control

Lesson 1: Overview of Call Admission Control 13-3

Lesson 2: Implementing Call Admission Control 13-14

Lab: Implementing Call Admission Control 13-22

Module 14: Deploying and Configuring Enhanced 9-1-1

Lesson 1: Overview of E9-1-1 14-3

Lesson 2: Deploying and Configuring E9-1-1 14-12

Lab: Configuring the Lync Server 2010 Location

Information Service for E9-1-1 Calling 14-24

Module 15: Voice Resiliency Features of Lync Server 2010

Lesson 1: Voice Resiliency in Lync Server 2010 15-3

Lesson 2: Features Available During Various Outage Scenarios 15-14

Lab: Implementing Voice Resiliency in Lync Server 2010 15-21

Lab Answer Keys


14/774


15/774

About This Course i

About This CourseThis section provides you with a brief description of the course, audience, suggested prerequisites, and

course objectives.

Course Description

This five-day instructor-led course teaches IT professionals how to deploy, configure, and administer a

Microsoft Lync Server 2010 solution. The course emphasizes Lync Server 2010 Enterprise Voice

features from a deployment and configuration perspective. The labs in this course build on each other to

create a solution that includes IM and Presence, Conferencing, and Enterprise Voice. This course helps the

student prepare for Exam 70-664.

Audience

This course is intended for IT professionals and telecommunications professionals, who want to learn how

to install, configure, manage, and maintain a Lync Server 2010 environment.

Student Prerequisites

Students should have at least three years experience working with unified communications (UC) software,

including knowledge of and experience with Microsoft Office Communications Server 2007 R2.

In addition to their professional experience, students who attend this training should have an

understanding of the following telecommunications concepts:

The difference between time-division multiplexing (TDM) and Voice over Internet Protocol (VoIP) Gateways and Private Branch Exchange (PBX) systems Session Initiation Protocol (SIP) Codecs Dialing plansStudents should also understand the following general concepts:

Networking fundamentals, including Transmission Control Protocol (TCP), IP, User Datagram Protocol(UDP), Domain Name System (DNS)

Active Directory Domain Services (AD DS) principles and management Microsoft Windows Server 2008 fundamentals Public Key Infrastructure (PKI) Microsoft Exchange messaging concepts Microsoft Windows PowerShell basics Microsoft SQL Server concepts and operationsCourse Objectives

After completing this course, students will be able to:

Describe how the features and architecture of Lync Server 2010 enable real-time communication andcollaboration.

Deploy Lync Server 2010. Configure users and rights using Role-Based Access Control (RBAC).


16/774


17/774

About This Course iii

Module 6, Configuring Basic Enterprise Voice Functionality, provides an overview of the major

components, features and topology requirements of Lync Server 2010 Enterprise Voice. It explains the

capabilities and components that are new or enhanced in Lync Server 2010. It also describes how to

prepare, configure, and deploy basic Enterprise Voice functionality.

Module 7, Extending Enterprise Voice Functionality, explains how to configure policies, routes, and

usage records. It also describes how to implement the call park and unassigned number features.

Module 8, Microsoft Exchange Server 2010 SP1 Unified Messaging (UM) Integration, describes

the prerequisites for integrating Exchange Server 2010 UM with Lync Server 2010. It also explains how to

create and configure a UM dial plan. Additionally, it covers how to use the tools and services needed to

integrate Exchange Server 2010 UM with Lync Server 2010. Finally, it explains how to enable a user for UM

integration with Lync Server 2010.

Module 9, Implementing Response Groups, introduces the Response Group Service (RGS) and the

changes that have been implemented with Lync Server 2010. It describes RGS components, including

queues, agent groups, workflows, and interactive workflows. It also explains how to use tools such as

Lync Server Control Panel, Lync Server Management Shell, and Response Group Configuration Tool to

manage workflows.

Module 10,Conferencing in Microsoft Lync Server 2010, introduces the conferencing abilities

provided by Lync Server 2010. It also explains dial-in conferencing in Lync Server 2010 and how to

manage and administer conferencing policies.

Module 11, Monitoring and Archiving, describes the features and configuration of the Monitoring

and Archiving services. It also explains how to interpret the Quality of Experience (QoE) reports and use

this information to better manage and deliver a high-quality user experience for Lync Server 2010.

Module 12, High Availability and Disaster Recovery in Microsoft Lync Server 2010, explains the

requirements for high availability and the requirements for the DNS Load Balancing feature. It also

describes the tools and methods for successfully backing up and restoring a Lync Server 2010

environment. Additionally, it explains how to back up, restore, export, and import critical Lync Server 2010

data.Module 13, Call Admission Control, introduces Call Admission Control (CAC) in Lync Server 2010 and

describes the various CAC components. It explains how to deploy and use CAC bandwidth management

to help prioritize and control allocation of network resources to real-time communications sessions.

Module 14,Deploying and Configuring Enhanced 9-1-1, introduces the Location Information Server

(LIS), which builds on Enhanced 9-1-1 (E9-1-1) technology to provide location information to users of a

network. It explains how to deploy and configure LIS for use with or without E9-1-1.

Module 15,Voice Resiliency Features of Lync Server 2010, describes the features of

Lync Server 2010 that ensure voice resiliency. It explains how voice resiliency is used to provide

continuous Enterprise Voice service so that users can continue making and receiving calls, even if the

central site or the WAN link from a branch to its central site becomes unavailable. It also explores multiple

failure scenarios such as central site failover, branch site failover, and WAN failover.


18/774

iv About This Course

Course MaterialsThe following materials are included with your kit:

Course Handbook A succinct classroom learning guide that provides all the critical technicalinformation in a crisp, tightly-focused format, which is just right for an effective in-class learning

experience.

Lessons: Guide you through the learning objectives and provide the key points that are critical tothe success of the in-class learning experience.

Labs: Provide a real-world, hands-on platform for you to apply the knowledge and skills learnedin the module.

Module Reviews and Takeaways: Provide improved on-the-job reference material to boostknowledge and skills retention.

Lab Answer Keys: Provide step-by-step lab solution guidance at your finger tips when itsneeded.

Course Companion Content on the http://www.microsoft.com/learning/companionmoc/Site:Searchable, easy-to-navigate digital content with integrated premiumon-line resources designed to

supplement the Course Handbook.

Modules: Include companion content, such as questions and answers, detailed demo steps andadditional reading links, for each lesson. Additionally, they include Lab Review questions and answers

and Module Reviews and Takeaways sections, which contain the review questions and answers, best

practices, common issues and troubleshooting tips with answers, and real-world issues and scenarios

with answers.

Resources: Include well-categorized additional resources that give you immediate access to the mostup-to-date premium content on TechNet, MSDN, Microsoft Press

Student Course files on the http://www.microsoft.com/learning/companionmoc/Site: Includes the

Allfiles.exe, a self-extracting executable file that contains all the files required for the labs anddemonstrations.

Course evaluation At the end of the course, you will have the opportunity to complete an onlineevaluation to provide feedback on the course, training facility, and instructor.

To provide additional comments or feedback on the course, send e-mail [email protected]. To inquire about the Microsoft Certification Program, send e-mail

to [email protected].


19/774


20/774

vi About This Course

Virtual machine Role

RRAS server and External DNS Miami

10533A-MIA-ED1.2 Stand-alone server

Lync Server 2010 Edge Server Miami

10533A-MIA-CL1.2 Internal Client MiamiPBX Emulator Host

10533A-RED-CL2.2 Member server in the fabrikam.com domain

Internal Client Redmond

10533A-ROM-CL3.2 Member server in the fabrikam.com domain

Internal Client Rome

10533A-INT-CL4.2 Member server in the fabrikam.com domain

Internet Client External

Course FilesThe course files needed for this class are located on the various virtual machines in C:\LabFiles.

Classroom SetupRefer to the Setup Guide for instructions on setting up the classroom.

Course Hardware Level

To ensure a satisfactory student experience, Microsoft Learning requires a minimum equipment

configuration for trainer and student computers in all Microsoft Certified Partner for Learning Solutions

(CPLS) classrooms in which Official Microsoft Learning Product courseware is taught. Hardware level 6 is

required for this course. Refer to the Setup Guide for more information.


21/774

Features and Architecture of MicrosoftLync Server 2010 1-1

Module 1

Features and Architecture of Microsoft Lync Server 2010

Contents:Lesson 1: Features of Lync Server 2010 1-3

Lesson 2: Architecture and Server Roles 1-15

Lesson 3: New Management Tools 1-24


22/774

1-2 Deploying, Configuring, and Administering Microsoft Lync Server 2010

Module Overview

The Microsoft Lync Server 2010 communications software introduces many new features beyond what

was available in previous versions of Microsoft communications solutions. Lync Server 2010 has a

completely redesigned and streamlined management infrastructure. It supports security, compliance, and

extensibility for a true enterprise-grade unified communications (UC) platform. It also offers the resiliency,

scalability, and critical features necessary to enhance or replace traditional Private Branch eXchange (PBX)

systems.

Lync Server 2010 provides new ways for users to connect, share information, and collaborate. Byestablishing a single solution that integrates voice, Instant Messaging (IM), and Web conferencing within

familiar Microsoft Office applications, Lync Server 2010 delivers a streamlined solution for todays busy

information workers.

In this module, you will learn about the architecture and topology of Lync Server 2010. You will also learn

about the high-level features, the enhanced social networking capabilities, and the improved

administrative experience provided by the new Central Management Store and the Lync Server Control

Panel. This module also provides an overview of the new Topology Builder tool, which enables you to

implement an appropriate architecture based on your organizations specifications.

Objectives

After completing this module, you will be able to:

Describe the features and capabilities of Lync Server 2010. Describe the new architecture and server roles of Lync Server 2010. Describe the new management tools of Lync Server 2010.


23/774


Lesson 1

Features of Lync Server 2010

This lesson provides you with an overview of the features and capabilities of Lync Server 2010. It also

introduces the new client-side communication and collaboration capabilities provided by the social

networking enhancements of Lync Server 2010. In addition, you will learn about the new Lync Server 2010

management tools, including the Lync Server Control Panel, Lync Server Management Shell, and Topology

Builder.

Objectives

After completing this lesson, you will be able to:

Describe the key Lync Server 2010 feature areas. Explain Converge Communications. Explore the social-networking additions. Describe the new Enterprise Voice features. Explore the Lync Server 2010 tools. Describe the Microsoft Lync 2010 clients.


24/774


Overview of Lync Server 2010

The overarching goal of Lync Server 2010 is to provide customers with an experience that unifies real-time

communication and collaboration in a holistic manner, while being a solution that is easy to deploy and

administer. Based on customer feedback, Lync Server 2010 has been redesigned to provide significant

architectural improvements, as well as enhancements to several features that increase the reliability, voice

quality, and manageability of the system.

New Management and Administrative Features

Several management, monitoring, and archiving enhancements are provided that help administratorsmanage and monitor the system more quickly and easily.

Central Management Server or Central Management Store

In Lync Server 2010, all configuration data about servers, services, and user policy is moved to the Central

Management Server (or the Central Management Store (CMS), whichever you are using). The CMS

provides robust storage of the data needed to define, set up, and maintain a Lync Server 2010

deployment. It also validates the data to ensure configuration consistency, and then replicates read-only

copies to all servers in the topology, including Edge servers. This eliminates the out-of-sync problems

experienced with earlier versions.

For more information about Central Management Server or Central Management Store, see Lesson 2,

Architecture and Server Roles, in this module.

Role-Based Access Control (RBAC)

Lync Server 2010 uses RBAC, providing administrators with access rights that are specific to their job

function. Following the principle of least privilege, the predefined roles in Lync Server 2010 enhance

system-wide security and help to ease the learning curve for new administrators. Administrators can also

create custom roles.

For more information about Role-based Access Control, see Module 3, Configuring Users and Rights in

Lync Server 2010.


25/774


New Features for Managing Edge Servers

In Lync Server 2010, you manage Edge servers from the internal network. Becauseallconfiguration data

for servers and services resides in the CMS, Edge Server management is simplified through use of internal

administrative tools. After you deploy Edge servers and configure the required ports, configuration data is

automatically pushed from the CMS to each Edge server. This strategy offers the following advantages:

Simplified installation. You do not have to install administrative tools on Edge servers. Streamlined management of Lync Server 2010 components. You can now configure Edge servers from

a centralized location with a single user interface.

Consistent synchronization of internal and external Lync Server 2010 configuration changes. Serverconfiguration changes are pushed out to Edge servers as they are made.

Improved security. You do not need to log on to Edge servers to perform administrative tasks.For more information on managing Edge Servers, see Module 4, Client and Device Deployment and

Management.

New Client Features

Lync 2010, formerly known as Microsoft Communicator 2007, has a redesigned user interface thatprovides an enhanced and more intuitive way for users to communicate using voice and video. New

calling features include:

Click to Call from Contacts In-call quality information Separate phone environment with a familiar dual-tone multi-frequency (DTMF) dial padThese features help to increase overall discoverability and user confidence. With one click, users can easily

share video in calls and conferences. A new panoramic video feature enables users to see the entire room

in multiparty conferences. A separate video window allows the use of dual monitors, enabling users to

watch video on one monitor while doing full-screen application or desktop sharing on another monitor.

New Enterprise Voice Features

Lync Server 2010 introduces several new features that enhance Enterprise Voice, including:

Enhanced voice resiliency in central sites and branch offices. Lync Server 2010 introduces the newBackup Registrar feature for enhanced voice resiliency.

Call Admission Control (CAC) for bandwidth management. This new feature provides functionality fordetermining optimal routing and managing available bandwidth by redirecting calls to an alternate

gateway, as needed.

Hosted Exchange Unified Messaging (UM). Full support for hosted Exchange UM integration isprovided.

Media bypass. This new feature for media path optimization provides bandwidth savings andimproved call quality.

Emergency dialing (Enhanced 9-1-1 [E-9-1-1]). Enhanced location information is provided forimproving the response time of emergency services.

New Mediation server and gateway topologies. New for the Mediation server is the ability for a singleMediation server to control multiple gateways. The Mediation server can now be collocated with the

Front End server.

Each of these topics will be discussed in more detail later in this module.


26/774


What Is Converge Communications?

Converge Communications is the ability to connect people and teams by sharing presence information

and enabling communication through short voice and instant messaging (IM) conversations, ad-hoc

meetings, structured team meetings, and presentations. The combination of these features can greatly

enhance an organizations collaboration and productivity. IM, presence, and conferencing are the core

capabilities of Lync Server 2010 communications software, and are automatically deployed and enabled in

every Lync Server 2010 installation.

Instant MessagingIM enables employees to communicate with each other in real time on their computers by using text-

based messages. If you deploy Edge servers, you can also enable your users to exchange instant messages

with users of public IM services, including any or all of the following: Microsoft Windows Live, AOL, and

Yahoo!, as well as Extensible Messaging and Presence Protocol (XMPP)based providers and servers, such

as Google Talk and Jabber. Note that a separate license is required for public IM connectivity with AOL

and Yahoo!.

Based on customer feedback, many IM components have been enhanced to increase reliability and the

overall user experience. For example, the client now automatically rejoins IM conferences in case of a

transient network drop-off. Enhanced privacy features provide users with more control over the

publishing of their location data and photo. The timeout for users has also been reduced to ensure that

fresh presence information is always displayed, and half-states have been removed from a usersavailability status.

Presence

Presence provides information to users about the status and availability of others on the network. A users

presence status provides information to help others decide the best way to contact the user: by means of

IM, telephone, or email. A users presence status is exposed as an icon in Lync 2010 and other presence-

aware applications, including the Microsoft Office 2010 Suite and Microsoft SharePoint technologies.


27/774


28/774


29/774


Enterprise Voice Features

This section describes Enterprise Voice functionality that is new or has been enhanced for

Lync Server 2010. Each feature has its own set of planning considerations, deployment requirements, and

configuration steps, which will be discussed in more detail later in this course.

Bandwidth Management Feature

Real-time communications are sensitive to the latency and packet loss that can occur on congested

networks. Call Admission Control (CAC) functionality has been added in Lync Server 2010 to help prevent

poor quality of experience for users on congested networks. CAC determines, based on available networkbandwidth, whether to allow real-time communications sessions to be established. CAC can also provide

an alternative route for calls when the preferred route does not have the required bandwidth. The

alternative route could be by way of the public switched telephone network (PSTN), or via the Internet

over the Edge servers.

Enhanced Emergency Dialing

Lync Server 2010 supports Enhanced 9-1-1 (E9-1-1) as part of an Enterprise Voice deployment. E9-1-1 is

an emergency notification feature that includes detailed physical address information when contacting

emergency services (in North America). By deploying an E9-1-1 system, an organization can provide the

exact location of the emergency call such as the phone number, building, floor, and conference room

to the closest Public Safety Answering Point (PSAP), enabling the dispatch of emergency services to the

exact location of the caller in distress. Currently, this enhanced feature is supported only for sites in NorthAmerica. However, basic location information services (LIS) functions are available with or without E9-1-1.

Media Bypass

In Lync Server 2010, the flow of media can now be configured to bypass the Mediation server when

possible. This capability improves call quality by optimizing the media path, reducing latency, minimizing

unnecessary transcoding, limiting packet loss, and eliminating potential points of failure.


30/774


31/774


Hosted Exchange Unified Messaging (UM)

In addition to the support that previous releases have provided for integration with on-premise

deployments of Exchange Unified Messaging (UM), Lync Server 2010 introduces support for integration

with hosted Exchange UM. This enables you to provide voice messaging to your users if you migrate some

or all of the users to a hosted Exchange service provider, such as Microsoft Exchange Online.

Call Park

The new Call Park application in Lync Server 2010 makes it possible for Enterprise Voice users to put a call

on hold and then retrieve it later from any phone. When a user parks a call, Call Park provides an orbit

number that identifies where the call is temporarily held. The user who parked the call can either dial the

orbit number to retrieve the parked call, or use an external mechanism, such as IM or a paging system, to

notify someone else of the number for retrieval. Call Park is useful for continuing a call from a different

location and for transferring a call when the final recipient is unknown.

Note: The Call Park feature is not available for analog devices.


32/774


Lync Server 2010 Tools

Lync Server 2010 includes new management and administrative tools that help simplify the planning and

validation of your deployment. Each of these tools is discussed in more detail in later modules.

Microsoft Lync Server 2010 Planning Tool. This planning wizard asks a series of questions about yourorganization, including the features you want to enable and your capacity-planning needs, and then

creates a recommended deployment topology based on your answers.

Microsoft Lync Server 2010 Topology Builder. This installation component is used to create, adjust, andpublish your planned topology. When you install Lync Server 2010 on individual servers, the servers

read the published topology as part of the installation process, and the installation program deploysthe server as directed in the topology.

New Microsoft Lync Server Control Panel. The Lync Server Control Panel uses Microsoft Silverlight topresent a Web-based graphical user interface (GUI). The new Lync Server Control Panel enables

administrators to manage their systems from anywhere on the corporate network without needing to

have specialized management software installed on the computer.

New Microsoft Lync Server 2010 Management Shell. Built upon the Microsoft Windows PowerShellcommand-line interface, the Lync Server 2010 Management Shell includes a comprehensive set of

cmdlets (commandlets) for all Lync Server 2010 administrative tasks. Lync Server 2010 is governed

through RBAC, and each role is associated with a specific list of Lync Server 2010 Management Shell

cmdlets that users in that role are allowed to run.


33/774


34/774


Microsoft Lync Web App

Microsoft Lync Web App is a web-based conferencing client that supports most Lync 2010 collaboration

and sharing features, as well as presenter meeting controls and dial-in and dial-out voice conferencing.

For users who do not have Lync 2010 installed, you can offer this conferencing option when it is not

practical or possible to install Lync Attendee.

Microsoft Lync Mobile for Windows Mobile

Microsoft Lync 2010 Mobile provides IM, enhanced presence, and telephony for users in your

organization who are connecting from a Smartphone or Windows Professional mobile device.


35/774


Lesson 2

Architecture and Server Roles

This lesson provides you with an introduction to the architecture and server roles of Lync Server 2010,

including supported topologies, the new CMS, Mediation server capabilities, DNS and hardware load

balancing, and virtualization support.

Objectives


Describe the new CMS. Describe the supported topologies. Define the server roles. Explore the new Mediation server capabilities. Explain the DNS load-balancing features. Explore virtualization support in Lync Server 2010.


36/774


Central Management Store

Earlier versions of Microsoft Office Communications Server stored configuration data within Active

Directory, Microsoft SQL Server, and Windows Management Instrumentation (WMI). One impact of this

design is that making even a small setting change requires changing the schema in Active Directory. This

is not a process undertaken lightly, particularly in large organizations.

CMS Storage

In Lync Server 2010, all topology, policy, and configuration data are stored in the CMS. The CMS database

provides storage for all data about servers, services, and users in the system. CMS validates the data toensure configuration consistency. Read-only copies are then replicated to all servers in your deployment

by the CMS, which runs on one Front End pool or one Standard Edition server in your deployment. This

replication eliminates the out-of-sync errors that would sometimes occur with the Edge servers, and

adds system-wide resiliency in the event of CMS outage.

Active Directory Storage

For backward compatibility purposes, a subset of information is still stored within Active Directory,

enabling pools from previous Office Communications Server versions to reference and route traffic.

Storing basic user information such as the users SIP URI and phone number within Active Directory may

also enable some third-party applications that were developed for previous versions of Lync Server 2010

to continue to function.

Administering CMS

To administer and manage the servers, services, and user policies stored within CMS, you can use

Lync Server Management Shell or Lync Server Control Panel, which then makes the setting changes in

CMS.


37/774


Supported Topologies

Lync Server 2010 is available in two editions: Standard and Enterprise. The Enterprise Edition server

requires a minimum of two servers in the deployment a Front End and a Back End server. The Front End

server is the core server role and the Back End server provides the database. The Standard Edition server

combines the Front End and Back End roles onto a single server. This topology is easy to deploy, and it

enables IM, presence, conferencing, and Enterprise Voice for smaller organizations (or pilot projects) that

do not require a high-availability solution.

Front End Pools

A Front End pool is a set of Front End servers, configured identically, that work together to provide

services for a common group of users, with full scalability and failover capabilities. A Front End server (or

Front End pool) provides the following functionality:

User authentication and registration Presence information and contact card exchange Address book services and distribution list expansion IM functionality, including multi-party IM conferences Web conferencing and application sharing (if deployed) Application hosting services Application services for application hosting and host applications (for example, Response Group

Application)

Additionally, one Front End pool in the deployment also runs the CMS.

Back End Servers

The Back End servers are database servers running Microsoft SQL Server that provide the database

services for the Front End pool. You can have a single Back End server, or a cluster for failover. Back End


38/774


servers do not run any Lync Server 2010 software. If you already have a SQL Server cluster that you are

using for other applications, you can also use this cluster for Lync Server 2010, if performance allows.

Information stored in the Back End server databases includes presence information, users contact lists,

conferencing data (including persistent data about the state of all current conferences), and conference

scheduling data.

The following are three reference topologies to help you envision the different scenarios where a

Standard Edition versus an Enterprise Edition should be deployed.

Single Server Standard Edition Reference Topology

For a smaller Enterprise or pilot implementations with fewer than 5,000 users, you can deploy

Lync Server 2010 Standard Edition with the following recommendations:

Deploy an Edge server and reverse proxy for remote access/external conferencing and federation. Use PSTN or SIP trunks to provide telephony integration.

Note: PSTN may require additional gateways.

Deploy Exchange UM for voice mail integration. Use Active Directory/DNS Services and internalPKI for certificate management. Use Survivable Branch Appliances (SBAs) for resiliency in remote locations. Deploy Standard Edition in a Paired solution (Primary and Secondary) for inexpensive failover and

for redundancy.

Medium to Large Deployment Reference Topology

For single datacenter deployments with up to 80,000 users (which is the single pool limit), or a single

datacenter with branch offices, you can deploy Lync Server 2010 Enterprise Edition with the following

recommendations:

Use DNS load balancing for SIP on Front End servers, Edge servers, and the Directory server. Use a Hardware Load Balancer (HLB) for Secure HTTP (HTTPS), Distributed Component Object Model

(DCOM), Reverse Proxy, and Edge Pool for Remote Access, External Conferencing, and Federation.

Deploy a Monitoring server to record call quality. Deploy an A/V Conferencing Pool for scalability, collocated on the Front End servers. Deploy a Director Pool, which is a dedicated server role. You can use Standard Edition for the Director

Pool, which can be DNS load-balanced, providing cost savings by not requiring additional SQL Server

computers.

Use PSTN or SIP Trunks to provide telephony integration. Note that PSTN may require additionalgateways.

Deploy Exchange UM for voice-mail integration. Use AD/DNS Services and Internal public key infrastructure (PKI) for certificate management. Deploy SBAs for voice resiliency in each of the remote locations.


39/774


Defining the Server Roles

In addition to the Front End and Back End server roles, Lync Server 2010 includes the following server

roles:

Director. When deployed in the internal network, the Director acts as a next-hop server. This optionalrole offers an additional layer of security, and in a deployment with multiple internal pools, offloads

the distribution of users to their home pools.

Edge server. Deployed in the perimeter network, the Edge server enables communication withexternal participants, including remote users, federated users (using Public Internet Connectivity

[PIC]), and anonymous users. The Edge server can be deployed as a single server or as a pool. TheEdge server role runs three services: Access Edge, Web Conferencing Edge, and A/V Edge.

Additionally, there is a Reverse Proxy, which publishes meeting content, address book, and group

expansion.

Archiving server. The Archiving server enables support for archiving Lync 2010 IM and webconferencing for companies that must follow compliance regulations. The Archiving server can be

collocated with the Monitoring server.

Monitoring server. The Monitoring server is useful for monitoring and troubleshooting issues relatedto user activity and media quality. It contains a Quality of Experience (QoE) report for user activity

that searches for Call Detail Records (CDRs) based on user alias, and another report for media quality

that searches individual detail records for signal values captured from the users device microphone

or speaker.

Survivable Branch Appliance. The Survivable Branch Appliance (SBA) is a server appliance with anembedded PSTN gateway running Microsoft Windows Server 2008 R2 and Lync Server 2010. It is

designed for branch sites that host between 25 and 1,000 users, when the return on investment does

not support a full deployment, or where local administrative support is not available. The SBA can

provide basic phone services to users at the branch site when the wide area network (WAN) link to

the Lync Server 2010 central site is down.


40/774


Survivable Branch Server. The Survivable Branch Server is a Windows server that has Lync Server 2010Registrar and Mediation server software installed. It is designed for branch sites that host between

1,000 and 5,000 users who lack a resilient WAN connection and have trained Lync Server 2010

administrators available. It must be configured to connect to either an IP/PSTN gateway or a SIP trunk

to a telephone service provider.

A/V MCU. This is an optional role that can be either collocated or stand-alone, as needed for scale. Animprovement to previous versions is that this server role can now be shared across multiple pools inthe same site.

Mediation server. This is an optional role that can be collocated on the Front End servers. New for theMediation server in Lync Server 2010 is the ability for a single Mediation server to control multiple

gateways.

Each of these server roles are discussed in more detail in the lessons and modules that follow.


41/774


Mediation Server Capabilities

In Lync Server 2010, the Mediation server is the central component for Enterprise Voice and dial-in

conferencing. The Mediation server translates signaling and (in some configurations) media between your

internal Lync Server 2010 infrastructure and an IP-PBX gateway or IP-PSTN gateway, or a SIP trunk.

In Lync Server 2010, the Mediation server now provides mapping with multiple gateways. The flow of

media can also be configured to bypass the Mediation server when possible and flow directly to a

gateway. This capability improves call quality by optimizing the media path, reducing latency, minimizing

unnecessary transcoding, limiting packet loss, and eliminating potential points of failure.

Media Bypass

Media Bypass is a feature that provides bandwidth savings in configurations where a Mediation server and

a PSTN gateway/IP-PBX/SIP trunk are at different sites connected by WAN links with constrained

bandwidth. Additionally, you no longer need a Mediation server in most local sites.

When you enable Media Bypass, a globally unique bypass ID is generated for all network sites. When a

user makes a PSTN call, the Mediation server compares the bypass ID of the client subnet with the bypass

ID of the gateway subnet. If the two bypass IDs match, Media Bypass is used for the call. If the bypass IDs

do not match, media for the call flows through the Mediation server at the central site.

When a user receives a call from the PSTN, the users client compares its bypass ID to that of the PSTN

gateway. If the two bypass IDs match, media flows directly from the gateway to the client, bypassing the

Mediation server.

Offloading the media processing from the Mediation server to pool servers for bypassed calls also

improves scalability and the quality of the call.


42/774


43/774


Virtualization Support

Lync Server 2010 supports all workloads and server roles, including Enterprise Voice, in both physical and

virtualized topologies. However, scalability and user capacity in a virtualized topology is reduced by

roughly 50 percent of what is offered by a Lync Server 2010 topology running only on physical servers. In

a virtualized deployment, CPU usage has a direct correlation to voice quality, especially at the beginning

of the hour when many new conferences typically begin.

Lync Server 2010 supports virtualization of the following servers:

Front End servers. If you virtualize a Front End server, you can also virtualize some or all of the otherserver roles of that site.

Standard Edition servers. When deploying a virtualized Standard Edition server, the only server rolesthat can be deployed with it are the Director, Monitoring server, Archiving server, and Edge server.

Edge servers. Virtualization is supported for Front End pools and Standard Edition servers.Support is included for both of the following virtualization technologies:

Microsoft Windows Server 2008 R2 Hyper-V VMWareTo run Windows Server on a virtualization technology other than Hyper-V or Virtual Server, the

virtualization product should be one that is validated by the Server Virtualization Validation Program

(SVVP), which is available at http://go.microsoft.com/fwlink/?LinkID=209686&clcid=0x409.


44/774


Lesson 3

New Management Tools

This lesson provides you with an introduction to the new management tools of Lync Server 2010,

including; RBAC, Lync Server Control Panel, and the Management Shell. All administrative functionality is

available through both the Lync Server Control Panel and the Management Shell, so the choice is

completely up to you.

Objectives


Explain Role-based Access Control. Explore the Lync Server Control Panel. Explore the Lync Server Management Shell.


45/774


Role-Based Access Control

The new administrative model for Lync Server 2010 involves Role-Based Access Control (RBAC). RBAC

enables administrators to delegate control of specific management tasks using the security best practice

of least privilege.

RBAC Example

For example, instead of granting Help desk and support personnel full administrator privileges, you can

give these employees very specific rights, such as:

Manage user accounts, and only user accounts. Manage Enterprise Voice components. Manage archiving and Archiving Server, and so on.In addition, these rights can be limited in scope; for example, someone can be given the right to manage

Enterprise Voice, but in the Redmond site only, while someone else can be given the right to manage

users, but only those user accounts in the Finance organizational unit (OU).

Benefit of RBAC

One benefit of RBAC is that as an administrator, you will not have to learn the entire management

interface and all of its functionsyou can focus specifically on your areas of expertise. You can create

custom RBAC roles by combining one or more of the predefined roles to create a superset role.

For more information on RBAC, see Module 3, Configuring Users and Rights.


46/774


Lync Server Control Panel

Lync Server Control Panel replaces the multiple administrative tools from previous releases, such as

Microsoft Management Console (MMC), Active Directory Users and Computers, Response Group tools,

WMI, Group Policy objects (GPOs), and local registry settings. Lync Server Control Panel provides you with

a single web-based tool with a graphical user interface (GUI) where all policies are reflected. This makes it

easier for you to understand the policy that is in effect for a given user. Intuitive navigation makes

identifying the proper location for setting configuration straightforward. Another time-saving advantage

of the Lync Server Control Panel is that your queries can now be saved and reused.

Policy Management

Policies allow you to define the features and functionality for which a user or a set of users are enabled.

Policies can be applied at each of four levels: Global, Site, Pool, and User.

Lync Server 2010 supports the universal groups in the Windows Server 2008 and Windows Server 2003

operating systems and follows the same inheritance methodology as Active Directory Group Policies.

More information on this topic will be provided in Module 3, Configuring Users and Rights in

Lync Server 2010.


47/774


Lync Server Management Shell

The Lync Server Management Shell is a new method of system administration and management. In

previous versions, the supported automation application programming interface (API) was WMI. Because

of customer feedback that WMI was difficult to use for automating tasks such as managing user policies

and entitlements in a consistent way, Lync Server Management Shell has been built on the

Windows PowerShell command-line interface. This improvement provides consistency among the

administration of other Microsoft products, such as Exchange, Active Directory, and SQL Server, and allows

you to accomplish administrative tasks using simple one-line commands or complex scripts.

Lync Server 2010 cmdlets encompass the full scope of management functions, allowing you to configureand test every aspect of the environment from within PowerShell 2.0, including:

User management. You can search for users and enable, disable, and assign Lync Server policies. Configuration management. You can define server roles and configure policies at the Global/Site level. Device management. You can configure and test devices, common area phones, and analog devices. Policy management. You can set archiving policies, configure external access, and manage voice

policies.

Deployment management. You can manage certificates, review setup steps, and manage yourtopology.

Voice applications. You can configure and modify response groups, configure the conferencingattendant, manage bandwidth, and manage external applications.

Synthetic transactions. You can test phone calls, perform SIP registrations, and set up simpleconferencing.


48/774


Module Review and Takeaways

Review Questions

1. What are some of the new management and administrative features in Lync Server 2010?2. What sort of functionality does a Front End server or Front End pool provide?3. What are the four levels at which policies can be applied in Lync Server 2010?


49/774

Deploying Microsoft Lync Server 2010 2-1

Module 2

Deploying Microsoft Lync Server 2010

Contents:Lesson 1: Preparing for Deployment 2-3

Lesson 2: Reviewing the Design Process 2-18

Lesson 3: Deploying Lync Server 2010 2-21

Lab: Preparing the Environment and Deploying a Lync Server 2010 Pool 2-31


50/774

2-2 Deploying, Configuring, and Administering MicrosoftLync Server 2010

Module Overview

This module presents you with the planning and implementation tasks that are necessary for the

deployment of Microsoft Lync Server 2010 Enterprise Edition. Your specific deployment process is

determined by the Lync Server 2010 topology and components that you decide to install, including

whether you want to deploy an Enterprise Edition pool or a Standard Edition server. The lessons in this

module cover the Lync Server 2010 infrastructure requirements, the topology design and publishing

process, and the steps required to prepare Microsoft Active Directory Domain Services (AD DS), deploy a

Front End server and pool, and prepare for the deployment of the remaining server roles.

After completing this module, you will be able to:

Prepare for the deployment of Lync Server 2010. Review the design process. Deploy Lync Server 2010.


51/774


Lesson 1

Preparing for Deployment

In this lesson, you will review the necessary steps for preparing for a Lync Server 2010 deployment. This

includes preparing the infrastructure, ensuring that the appropriate software and hardware components

are in place, planning for certificates, and considering the client, device, and network requirements.


Inspect the Active Directory infrastructure. Assess load-balancing options. Validate the required operating system and Microsoft Windows components. Consider an internal versus an external public key infrastructure (PKI) solution. Examine the client requirements. Examine the device requirements. Describe the physical network and file share requirements.


52/774


Active Directory Infrastructure Requirements

Lync Server 2010 communications software supports the same AD DS topologies as

Microsoft Office Communications Server 2007 R2 and Microsoft Office Communications Server 2007. The

following topologies are supported:

Single forest with single domain. This is a common and simple topology. Single forest with multiple domains. In this topology, the domain where you create users can be

different from the domain where you deploy Lync Server 2010. However, you must deploy anEnterprise pool within a single domain. Lync Server 2010 contains support for Windows universal

administrator groups, which enables cross-domain administration.

Single forest with multiple trees. This topology consists of two or more domains that defineindependent tree structures and separate Active Directory namespaces.

Multiple forests in a central forest topology. This topology uses contact objects to represent users inother forests. The central forest hosts user accounts for any users in the forest. A directorysynchronization product, such as Microsoft Identity Integration Server (MIIS),Microsoft Forefront Identity Manager (FIM) 2010, orMicrosoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1) is used to synchronize thecreation or deletion of user accounts within the organization.

Multiple forests in a resource forest topology. In this topology, one forest is dedicated to runningserver applications, such as Microsoft Exchange Server and Lync Server 2010. The resource forest

hosts the server applications and a synchronized representation of the active user object, but it doesnot contain logon-enabled user accounts. When you deploy Lync Server 2010 in this type oftopology, you create one disabled user object in the resource forest for every user account in the userforests. If Microsoft Exchange is already deployed in the resource forest, the disabled user accountsmay already exist. A directory synchronization product manages the life cycle of user accounts.

Active Directory Requirements

Before you start the process of preparing AD DS for Lync Server 2010, you must ensure that all domain

controllers (including global catalog servers) meet the following prerequisites:


53/774


Microsoft Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, orWindows Server 2003 must be installed.

All domains must be raised to Windows Server 2003 domain functional level. The forest must be raised to a Windows Server 2003 forest functional level.Lync Server 2010 supports AD DS deployments that include read-only domain controllers or read-only

global catalog servers, as long as there are writable domain controllers available.


54/774


Load Balancing Options

Lync Server 2010 supports Domain Name System (DNS) load balancing for many features of Front End

pools, Edge server pools, Director pools, and stand-alone Mediation server pools.

DNS Load Balancing on Front End Pools and Director Pools

DNS load balancing is supported only by servers running Lync Server 2010 and Lync Server 2010 clients.

You cannot achieve load balancing of connections from older clients and servers by implementing DNS

round robin on the DNS servera hardware load balancer is required. Additionally, if you are using

Exchange Unified Messaging (UM), only Exchange Server 2010 SP1 interoperates with Lync Server 2010DNS load balancing.

To deploy DNS load balancing on Front End pools and Director pools, you must:

Create two fully qualified domain names (FQDNs). A regular pool FQDN is required on the DNS serverfor resolving the physical Internet Protocol (IP) addresses of the servers in the pool, and anotherFQDN is required on the hardware load balancer for web services to resolve the virtual IP address ofthe pool. You create this extra FQDN for the pools web services by using Topology Builder.

Provision DNS. Provision the DNSserverto resolve the pool FQDN to the IP addresses of all servers inthe pool.

DNS Load Balancing on Edge Server Pools

We recommend that you deploy DNS load balancing on the external interface of your Edge servers. Youcan also deploy load balancing on the internal interface; however, when an Edge server has failed, failover

is lost and some users might experience a denial of request.

To deploy DNS load balancing on the external interface of your Edge server pool, you must create the

following DNS entries:

Lync Server Access Edge service. Create one entry for each server in the pool. Each entry must resolvethe FQDN of the Lync Server Access Edge service to the IP address of the Lync Server Access Edgeservice on one of the Edge servers in the pool.


55/774


Lync Server web Conferencing Edge service. Create one entry for each server in the pool. Each entrymust resolve the FQDN of the Lync Server web Conferencing Edge service to the IP address of the

Lync Server web Conferencing Edge service on one of the Edge servers in the pool.

Lync Server Audio/Video Edge service. Create one entry for each server in the pool. Each entry mustresolve the FQDN of the Lync Server Audio/Video (A/V) Edge service to the IP address of the Lync

Server A/V Conferencing Edge service on one of the Edge servers in the pool.

Using DNS Load Balancing on Stand-Alone Mediation Server Pools

You can use DNS load balancing on stand-alone Mediation server pools without the need for a hardware

load balancer. All Session Initiation Protocol (SIP) and media traffic is balanced by DNS load balancing.

To deploy DNS load balancing on a Mediation server pool, you must provision DNS to resolve the pool

FQDN to the IP addresses of all servers in the pool.


56/774


Operating System and Windows Component Requirements

In addition to the hardware and operating system requirements for server platforms, Lync Server 2010

may require the installation of additional software on the servers that you deploy. Some of the software

requirements only apply to specific server roles or components, so they may not be required for your

particular deployment. The slide lists all of the software components that may be required for

Lync Server 2010. However, this topic covers only those software components that you may need to

download, enable, or install that are not automatically installed during the Lync Server 2010 setup

process.

Before deploying Lync Server 2010, you must install the following operating system updates:

Microsoft Knowledge Base article 968929, Windows Management Framework (WindowsPowerShell 2.0, WinRM 2.0, and BITS 4.0), at http://go.microsoft.com/fwlink/?linkid=197390

For each server that has Microsoft Internet Information Services (IIS) installed, you must install thefollowing updates:

o IIS URL Rewrite module at http://go.microsoft.com/fwlink/?linkid=197391o IIS Application Request Routing module at http://go.microsoft.com/fwlink/?linkid=197392

Windows PowerShell Version 2.0

Lync Server 2010 Management Shell requires Microsoft Windows PowerShell command-line interface

version 2.0. You must remove previous versions of Windows PowerShell prior to installingWindows PowerShell version 2.0.

For details about downloading Windows PowerShell version 2.0, see Knowledge Base article 968929,

Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0), which is

available at http://go.microsoft.com/fwlink/?linkid=197390.


57/774


Microsoft .NET Framework Requirements

The 64-bit edition of Microsoft .NET Framework 3.5 with SP1 is required for Lync Server 2010. The setup

process of Lync Server 2010 prompts you to install this prerequisite, and it automatically installs it if it is

not already installed on the computer. However, if you install Lync Server 2010 by using the command

line, you need to manually install .NET Framework 3.5 SP1 on the server, which is available at

http://go.microsoft.com/fwlink/?linkid=197398.

Microsoft Visual C++ 2008 Redistributable Package Requirements

The Microsoft Visual C++ 2008 redistributable package is required for Lync Server 2010. If you install

Lync Server 2010 by using the Lync Server Deployment Wizard, setup prompts you to install this

prerequisite. However, if you install Lync Server 2010 by using the command line, you need to manually

install this prerequisite on the server, which is available at http://go.microsoft.com/fwlink/?linkid=197399.

Message Queuing

Lync Server 2010 uses the Microsoft Message Queuing (MSMQ) technology with the following server

roles:

Front End server Mediation server Archiving server Monitoring server A/V Conferencing serverThe Message Queuing service must be enabled on all servers prior to deploying any of the above listed

server roles. Message Queuing can be installed as an optional feature in Windows Server 2008.

Windows Installer Version 4.5

Lync Server 2010 uses Windows Installer technology to install, uninstall, and maintain various server roles.

Windows Installer version 4.5 is available as a redistributable component for the Windows Server

operating system, which is available at http://go.microsoft.com/fwlink/?linkid=197395.

Windows Media Format Runtime Requirements

To use the Call Park, Announcement, and Response Group applications, you must install Windows Media

Format Runtime on Front End servers. We recommend that you install Windows Media Format Runtime

before installing Lync Server 2010. If Lync Server 2010 does not find this software on the server, it will

prompt you to install it; you must then restart the server to complete the installation.


58/774


Certificate Infrastructure Requirements

Lync Server 2010 requires a PKI to support Transport Layer Security (TLS) and mutual TLS (MTLS)

connections, as well as other services. If you are allowing external access, a PKI infrastructure must be in

place. We recommend that you use certificates issued from a public certification authority (CA).

Additional requirements for certificates include:

All server certificates must support server authentication (Server EKU). Auto-enrollment is supported for internally facing servers, but it is not supported for Edge servers.Internally Facing Servers

The internal servers that require certificates include:

Standard Edition server Enterprise Edition Front End server Stand-alone A/V Conferencing server Mediation server Director serverYou can use the Lync Server 2010 Certificate Wizard to request these certificates. Although using

certificates from an internal CA is recommended for internal servers, you can also obtain certificates for

internal servers from a public CA.

External User Access

Lync Server 2010 supports the use of a single certificate for Access and web Conferencing Edge external

interfaces, and the internal interface of the A/V Edge. The Edge internal interface can use either a private

or a public certificate.

Requirements for the private (or public) certificate used for the Edge internal interface are as follows:


59/774


60/774


Client Requirements

Before deploying Lync 2010 clients, you must configure several essential policies and settings. These

include client bootstrapping policies, client version policy, and key in-band provisioning settings.

Client Bootstrapping Policies

Client bootstrapping policies specify, for example, the default servers and security mode that the client

should use until sign-in is complete. Because client bootstrapping policies take effect before the client

signs in and begins receiving in-band provisioning settings from the server, you use Group Policy to

configure them.

Client Version Policy

The default Client Version Policy requires that all clients are running a minimum of

Microsoft Office Communicator 2007 R2. If clients in your environment are running earlier versions of

Communicator, you might need to reconfigure the Client Version rules to prevent clients and devices

from being unexpectedly blocked or updated when connecting to Lync Server 2010. You can modify the

default rule, or you can add a rule higher in the Client Version Policy list to override the default rule.

Additionally, as cumulative updates are released, you should configure the Client Version Policy to require

the latest updates. The following options are available when editing the client version policy:

Allow the client to log on. Allow the client to log on and receive updates from Windows Server Update Service or MicrosoftUpdate. Allow the client to log on and display a message about where to download another client version. Block the client from logging on. Block the client from logging on and allow the client to receive updates from Windows Server Update

Service or Microsoft Update.


61/774


Block the client from logging on and display a message about where to download another clientversion.

Key In-Band Settings

Most of the Group Policy settings in Lync Server 2010 are controlled by server-based client policies, also

known as in-band provisioning. In-band provisioning settings can significantly impact the user experience

and therefore should be configured before client deployment. In Lync Server 2010, client policies (exceptfor those required for bootstrapping) are configured by using the Windows PowerShell cmdlets New-

CsClientPolicy or Set-CsClientPolicy.

For more information about client requirements, see Module 4, Client and Device Deployment.


62/774


Device Requirements

Lync Server 2010 expands the line of available unified communications (UC) devices to include a new line

of IP phones. Before you deploy UC phones, ensure that the following recommended Lync Server 2010

communications software components are in place.

Device Update Service

The Device Update service, which is an automated way to update your IP phones, is installed with web

services on the Front End server.

Important: In Lync Server 2010 Enterprise Edition, you may have multiple servers in the pool. Foreach instance of web services running on servers in a pool, there is a separate instance of the DeviceUpdate service running in the pool. When you make a configuration change to the Device Updateservice, the changes are propagated to all servers in that pool, but not to servers in any other pool.

Enterprise Voice

Enterprise Voice is the voice over Internet Protocol (VoIP) solution in Lync Server 2010 that allows users to

make calls and use rich communication and collaboration features, such as viewing enhanced presence

information or location information for contacts in your organizations address book.

Enterprise Voice must be enabled for each device user. To check whether Enterprise Voice is enabled for auser, in Lync Server Control Panel, find the user and then view the users details. If the user is enabled for

Enterprise Voice, the check box Enabled for Lync Server will be selected, and the Telephony drop-down

list will show Enterprise Voice as selected.

Contact Objects for Common Area Phones and Analog Devices

You must associate all phones with a specific user or an Active Directory contact object. With contact

objects, as with user accounts, you can assign policies and voice plans for managing the device.


63/774


Important: When you create a contact object for an analog device (for example, by using the New-CSAnalogDevice command), you must specify the correct categorization of the analog device aseither a fax machine (such as fax, modem, Teletype-33 (TTY), or a voice device. The designation of fax

affects how the call will be routed.

Dial Plans, Voice Polices, and Outbound Call RoutesBefore deploying Lync Server 2010, you must set up the following rules for users:

Dial plans. Dial plans are sets of normalization rules that translate phone numbers for a givenlocation, user, or contact object into a single standard (E.164) format. This allows UC device users to

make calls to the public switched telephone network (PSTN).

Voice policies. Voice policies are records that define call permissions for users, sites, or an entireorganization, and include various calling features that can be enabled or disabled as appropriate.

Voice policies must be set up for device users.

Call routes. Call routes are rules that specify how Lync Server 2010 handles outbound calls from UCdevices. Lync Server 2010 uses routes to associate a target phone number with one or more media

gateways or SIP trunks and one or more PSTN usage records.

Least-Cost Routing

Lync Server 2010 enables you to specify the PSTN gateways through which you want to route numbers.

The recommended best practice is to select routes that incur the lowest costs and implement them

accordingly. When selecting a gateway, choose the one closest to the destination location to minimize

long-distance charges. For example, if you are in New York and calling a number in Rome, you should

carry the call over the IP network to the gateway in your Rome office, thereby incurring a charge only for

a local call.

You use Lync Server Control Panel to verify whether dial plans, voice policies, and call routes are set up for

users, and to set up or modify these user policies.

Note: If your organization has Microsoft Exchange Server deployed, you can also configure ExchangeUM and Lync Server 2010 to work together.

For more information about Exchange Unified Messaging, see Module 8, Exchange 2010 SP1 UM

Integration.

PIN Authentication and Policy

If you are deploying the new line of IP phonesAastra 6721ip, Polycom CX600, Polycom CX500, or

Polycom CX3000you must enable personal identification number (PIN) authentication on

Lync Server 2010, and set the appropriate PIN policy. This allows automatic authentication when a user

signs in. You set the PIN policy on the PIN Policy page of the Security group in Lync Server Control Panel.

Also in Security, you should click web Service and verify that PIN authentication is enabled in the Globalpolicy.


64/774


Physical Network and File Share Requirements

The proper network infrastructure for your Lync Server 2010 deployment is vital to both user adoption

and the overall success of your communication system. Inadequate network throughput increases

response times and can result in a solution that fails to achieve the goals of enhanced collaboration and

connectivity. The network adapter card of each server in the Lync Server 2010 topology must support at

least 1 gigabit per second (Gbps). In general, you should connect all server roles by using a low-latency

and high-bandwidth local area network (LAN). The size of the LAN is dependent on the size of the

topology:

Standard Edition topologies. Servers should be in a network that supports 1 Gbps Ethernet orequivalent.

Front End pool topologies. Most servers should be in a network that supports more than 1 Gbps,especially when supporting A/V conferencing and application sharing.

PSTN integration can be achieved with a supported PSTN Gateway, IP-PBX, or SIP trunk.

Media Requirements

Follow these recommendations for optimized A/V in a Lync Server 2010 deployment:

Configure the external firewall as a NAT (whether the site has only a single Edge server or multipleEdge servers deployed).

Deploy the media subsystem within an existing Quality of Service (QoS) infrastructure that prioritizescapacity for PSTN data flows.

Disable Internet Protocol security (IPsec) over the port ranges used for A/V traffic.Ensuring Media Quality

For optimal media quality, you must ensure that proper network provisioning and capacity planning has

been performed:


65/774


Lync Server 2010 media endpoints can adapt to varying network conditions. However, in an under-provisioned network, the ability of the Lync Server 2010 media endpoints to dynamically deal with

varying network conditions (for example, temporary high packet loss) is reduced.

Networks must be provisioned to support throughput of 45 kilobits per second (Kbps) per audiostream and 300 Kbps per video stream, if enabled, during peak usage periods.

For network links where provisioning is extremely costly and difficult, you might need to considerprovisioning for a lower volume of traffic. In this scenario, you let the elasticity of theLync Server 2010 media endpoints absorb the difference between that traffic volume and the peak

traffic level, at the cost of some reduction in quality. However, in this case, there is a decrease in the

systems ability to absorb sudden peaks in traffic.

For links that cannot be correctly provisioned in the short term (for example, a site with very poorwide area network [WAN] links), consider disabling video for certain users.

Provision your network to ensure a maximum end-to-end delay (latency) of 150 milliseconds (ms)under peak load. Latency is the one network impairment that Lync Server 2010 media components

cannot reduce, and it is important to find and eliminate the weak points.


66/774


Lesson 2

Reviewing the Design Process

The design process for a Lync Server 2010 communications system has been greatly aided by the

introduction of the Lync Server Planning Tool, which is used by systems architects to design the

communications system topology. The Planning Tool creates an .xml file, which you then use in the

Topology Builder to configure and publish your topology.

In this lesson, you will learn about the Microsoft Lync Server 2010 Planning Tool, and how the topology

design and the components have been chosen for installation.


Describe the purpose of the Planning Tool. List the requirements of the Planning Tool.


67/774


68/774


Requirements of the Planning Tool

The Planning Tool is an x86 application that can run on x86-based or x64-based computers.

To install the Planning Tool, your computer must be running the following:

Microsoft Windows 7, Windows Server 2008 R2, Windows Server 2008 with Service Pack 2 (SP2), orMicrosoft Windows Vista with SP2 (64-bit or 32-bit)

Microsoft .NET Framework 3.5 with SP1(or later)

Note: After you import your Planning Tool results into Topology Builder and start the deployment,any changes that you make by using the Planning Tool cannot be imported into Topology Builder.Therefore, any server roles that you add later must be configured manually in Topology Builder.


69/774


Lesson 3

Deploying Lync Server 2010

The deployment process for Lync Server 2010 is determined by the Lync Server 2010 topology and the

components you want to install, including whether you want to deploy an Enterprise Edition pool or a

Standard Edition server. This lesson covers the steps for deploying Lync Server 2010 Enterprise Edition

server. You will learn how to prepare Active Directory, deploy a Front End server pool, and deploy

additional server roles.

After completing this lesson, you will be able to: Identify

Microsoft Lync Configuration Trainer Handbook

Documents

Transcript of Microsoft Lync Configuration Trainer Handbook