Professional Documents
Culture Documents
20336B ENU TrainerHandbook PDF
20336B ENU TrainerHandbook PDF
20336B
Core Solutions of Microsoft® Lync® Server
2013
MCT USE ONLY. STUDENT USE PROHIBITED
ii Core Solutions of Microsoft® Lync® Server 2013
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.
Released: 05/2013
MCT USE ONLY. STUDENT USE PROHIBITED
MICROSOFT LICENSE TERMS
MICROSOFT INSTRUCTOR-LED COURSEWARE
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to your use of the content accompanying this agreement which
includes the media on which you received it, if any. These license terms also apply to Trainer Content and any
updates and supplements for the Licensed Content unless other terms accompany those items. If so, those terms
apply.
BY ACCESSING, DOWNLOADING OR USING THE LICENSED CONTENT, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT ACCESS, DOWNLOAD OR USE THE LICENSED CONTENT.
If you comply with these license terms, you have the rights below for each license you acquire.
1. DEFINITIONS.
a. “Authorized Learning Center” means a Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, or such other entity as Microsoft may designate from time to time.
b. “Authorized Training Session” means the instructor-led training class using Microsoft Instructor-Led
Courseware conducted by a Trainer at or through an Authorized Learning Center.
c. “Classroom Device” means one (1) dedicated, secure computer that an Authorized Learning Center owns
or controls that is located at an Authorized Learning Center’s training facilities that meets or exceeds the
hardware level specified for the particular Microsoft Instructor-Led Courseware.
d. “End User” means an individual who is (i) duly enrolled in and attending an Authorized Training Session
or Private Training Session, (ii) an employee of a MPN Member, or (iii) a Microsoft full-time employee.
e. “Licensed Content” means the content accompanying this agreement which may include the Microsoft
Instructor-Led Courseware or Trainer Content.
f. “Microsoft Certified Trainer” or “MCT” means an individual who is (i) engaged to teach a training session
to End Users on behalf of an Authorized Learning Center or MPN Member, and (ii) currently certified as a
Microsoft Certified Trainer under the Microsoft Certification Program.
g. “Microsoft Instructor-Led Courseware” means the Microsoft-branded instructor-led training course that
educates IT professionals and developers on Microsoft technologies. A Microsoft Instructor-Led
Courseware title may be branded as MOC, Microsoft Dynamics or Microsoft Business Group courseware.
h. “Microsoft IT Academy Program Member” means an active member of the Microsoft IT Academy
Program.
i. “Microsoft Learning Competency Member” means an active member of the Microsoft Partner Network
program in good standing that currently holds the Learning Competency status.
j. “MOC” means the “Official Microsoft Learning Product” instructor-led courseware known as Microsoft
Official Course that educates IT professionals and developers on Microsoft technologies.
k. “MPN Member” means an active silver or gold-level Microsoft Partner Network program member in good
standing.
MCT USE ONLY. STUDENT USE PROHIBITED
l. “Personal Device” means one (1) personal computer, device, workstation or other digital electronic device
that you personally own or control that meets or exceeds the hardware level specified for the particular
Microsoft Instructor-Led Courseware.
m. “Private Training Session” means the instructor-led training classes provided by MPN Members for
corporate customers to teach a predefined learning objective using Microsoft Instructor-Led Courseware.
These classes are not advertised or promoted to the general public and class attendance is restricted to
individuals employed by or contracted by the corporate customer.
n. “Trainer” means (i) an academically accredited educator engaged by a Microsoft IT Academy Program
Member to teach an Authorized Training Session, and/or (ii) a MCT.
o. “Trainer Content” means the trainer version of the Microsoft Instructor-Led Courseware and additional
supplemental content designated solely for Trainers’ use to teach a training session using the Microsoft
Instructor-Led Courseware. Trainer Content may include Microsoft PowerPoint presentations, trainer
preparation guide, train the trainer materials, Microsoft One Note packs, classroom setup guide and Pre-
release course feedback form. To clarify, Trainer Content does not include any software, virtual hard
disks or virtual machines.
2. USE RIGHTS. The Licensed Content is licensed not sold. The Licensed Content is licensed on a one copy
per user basis, such that you must acquire a license for each individual that accesses or uses the Licensed
Content.
2.1 Below are five separate sets of use rights. Only one set of rights apply to you.
2.2 Separation of Components. The Licensed Content is licensed as a single unit and you may not
separate their components and install them on different devices.
2.3 Redistribution of Licensed Content. Except as expressly provided in the use rights above, you may
not distribute any Licensed Content or any portion thereof (including any permitted modifications) to any
third parties without the express written permission of Microsoft.
2.4 Third Party Programs and Services. The Licensed Content may contain third party programs or
services. These license terms will apply to your use of those third party programs or services, unless other
terms accompany those programs and services.
2.5 Additional Terms. Some Licensed Content may contain components with additional terms,
conditions, and licenses regarding its use. Any non-conflicting terms in those conditions and licenses also
apply to your use of that respective component and supplements the terms described in this agreement.
a. Pre-Release Licensed Content. This Licensed Content subject matter is on the Pre-release version of
the Microsoft technology. The technology may not work the way a final version of the technology will
and we may change the technology for the final version. We also may not release a final version.
Licensed Content based on the final version of the technology may not contain the same information as
the Licensed Content based on the Pre-release version. Microsoft is under no obligation to provide you
with any further content, including any Licensed Content based on the final version of the technology.
b. Feedback. If you agree to give feedback about the Licensed Content to Microsoft, either directly or
through its third party designee, you give to Microsoft without charge, the right to use, share and
commercialize your feedback in any way and for any purpose. You also give to third parties, without
charge, any patent rights needed for their products, technologies and services to use or interface with
any specific parts of a Microsoft software, Microsoft product, or service that includes the feedback. You
will not give feedback that is subject to a license that requires Microsoft to license its software,
technologies, or products to third parties because we include your feedback in them. These rights
survive this agreement.
c. Pre-release Term. If you are an Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, MPN Member or Trainer, you will cease using all copies of the Licensed Content on
the Pre-release technology upon (i) the date which Microsoft informs you is the end date for using the
Licensed Content on the Pre-release technology, or (ii) sixty (60) days after the commercial release of the
technology that is the subject of the Licensed Content, whichever is earliest (“Pre-release term”).
Upon expiration or termination of the Pre-release term, you will irretrievably delete and destroy all copies
of the Licensed Content in your possession or under your control.
MCT USE ONLY. STUDENT USE PROHIBITED
4. SCOPE OF LICENSE. The Licensed Content is licensed, not sold. This agreement only gives you some
rights to use the Licensed Content. Microsoft reserves all other rights. Unless applicable law gives you more
rights despite this limitation, you may use the Licensed Content only as expressly permitted in this
agreement. In doing so, you must comply with any technical limitations in the Licensed Content that only
allows you to use it in certain ways. Except as expressly permitted in this agreement, you may not:
access or allow any individual to access the Licensed Content if they have not acquired a valid license
for the Licensed Content,
alter, remove or obscure any copyright or other protective notices (including watermarks), branding
or identifications contained in the Licensed Content,
modify or create a derivative work of any Licensed Content,
publicly display, or make the Licensed Content available for others to access or use,
copy, print, install, sell, publish, transmit, lend, adapt, reuse, link to or post, make available or
distribute the Licensed Content to any third party,
work around any technical limitations in the Licensed Content, or
reverse engineer, decompile, remove or otherwise thwart any protections or disassemble the
Licensed Content except and only to the extent that applicable law expressly permits, despite this
limitation.
5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to
you in this agreement. The Licensed Content is protected by copyright and other intellectual property laws
and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the
Licensed Content.
6. EXPORT RESTRICTIONS. The Licensed Content is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the Licensed
Content. These laws include restrictions on destinations, end users and end use. For additional information,
see www.microsoft.com/exporting.
7. SUPPORT SERVICES. Because the Licensed Content is “as is”, we may not provide support services for it.
8. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this agreement if you fail
to comply with the terms and conditions of this agreement. Upon termination of this agreement for any
reason, you will immediately stop all use of and delete and destroy all copies of the Licensed Content in
your possession or under your control.
9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Licensed
Content. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for
the contents of any third party sites, any links contained in third party sites, or any changes or updates to
third party sites. Microsoft is not responsible for webcasting or any other form of transmission received
from any third party sites. Microsoft is providing these links to third party sites to you only as a
convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party
site.
10. ENTIRE AGREEMENT. This agreement, and any additional terms for the Trainer Content, updates and
supplements are the entire agreement for the Licensed Content, updates and supplements.
12. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws
of your country. You may also have rights with respect to the party from whom you acquired the Licensed
Content. This agreement does not change your rights under the laws of your country if the laws of your
country do not permit it to do so.
13. DISCLAIMER OF WARRANTY. THE LICENSED CONTENT IS LICENSED "AS-IS" AND "AS
AVAILABLE." YOU BEAR THE RISK OF USING IT. MICROSOFT AND ITS RESPECTIVE
AFFILIATES GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. YOU MAY
HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT
CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT AND
ITS RESPECTIVE AFFILIATES EXCLUDES ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
14. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT, ITS RESPECTIVE AFFILIATES AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP
TO US$5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL,
LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The
above limitation or exclusion may not apply to you because your country may not allow the exclusion or
limitation of incidental, consequential or other damages.
Please note: As this Licensed Content is distributed in Quebec, Canada, some of the clauses in this
agreement are provided below in French.
Remarque : Ce le contenu sous licence étant distribué au Québec, Canada, certaines des clauses
dans ce contrat sont fournies ci-dessous en français.
EXONÉRATION DE GARANTIE. Le contenu sous licence visé par une licence est offert « tel quel ». Toute
utilisation de ce contenu sous licence est à votre seule risque et péril. Microsoft n’accorde aucune autre garantie
expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection dues
consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties
implicites de qualité marchande, d’adéquation à un usage particulier et d’absence de contrefaçon sont exclues.
EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d’autres droits
prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre
pays si celles-ci ne le permettent pas.
Acknowledgments
Microsoft Learning wants to acknowledge and thank the following for their contribution toward
developing this title. Their effort at various stages in the development has ensured that you have a good
classroom experience.
Module 1: Architecture and design approach for Microsoft Lync Server 2013
Lesson 1: Overview of Lync Server 2013 Architecture 1-2
Lesson 2: Overview of Lync Server 2013 Core Capabilities 1-14
Lesson 3: Introduction to the Lync Server 2013 Design Process 1-21
Lesson 4: Assessing Infrastructure Requirements and Updating the Design 1-29
Lesson 5: Planning for all Microsoft Solutions Framework Phases 1-37
This instructor-led course teaches IT professionals how to plan, design, deploy, configure, and administer
a Microsoft Lync Server 2013 solution. The course emphasizes Lync Server 2013 Enterprise Unified
Communications features with particular emphasis on coexisting with and migrating from legacy
communication services. The labs in this course create a solution that includes IM and Presence,
Conferencing, and Persistent Chat. This course helps the student prepare for Exam 70-336.
Audience
This course is intended for IT consultants and telecommunications consulting professionals who design,
plan, deploy, and maintain solutions for unified communications (UC). Candidates should be able to
translate business requirements into technical architecture and design for a UC solution. In addition,
Business Application Administrators (BAAs) who are engaged in the administering line-of-business (LOB)
projects in conjunction with internal business customers would benefit from understanding of managing
Lync Server 2013.
Student Prerequisites
This course requires that you meet the following prerequisites:
• Experience managing software in a Windows 2008 R2 enterprise server or Windows Server 2012
environment.
• Experience managing an application remotely using Windows PowerShell 2.0.
• Experience managing and configuring databases.
• An introduction to Active Directory Domain Services
Course Objectives
After completing this course, students will be able to:
• Describe the overall server and client Lync Server 2013 architecture.
• Describe Lync 2013 features and user scenarios.
• Describe the Lync Server deployment process.
• Describe the components of a Lync Server 2013 Design.
• Plan for Microsoft Solutions Framework for Lync 2013
• Plan Infrastructure Requirements for Lync Server 2013
• Use the Lync Server 2013 Planning Tool
• Use Topology Builder
• Plan for Site Topology
• Design a Site Topology
• Plan the Server Infrastructure
• Design Documentation Using Microsoft Office
• Use Lync Server 2013 management interfaces.
• Configure Role-Based Access Control.
• Prepare for client deployment.
• Deploy and manage clients.
• Prepare for device deployment.
• Deploy and manage Internet Protocol (IP) phones.
• Describe conferencing in Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
ii About This Course
Course Outline
The course outline is as follows:
Module 1, Architecture Overview and design approach of Microsoft Lync Server 2013
Module 2, Designing a Lync Server 2013 Topology
Course Materials
The following materials are included with your kit:
• Course Handbook: a succinct classroom learning guide that provides the critical technical
information in a crisp, tightly-focused format, which is essential for an effective in-class learning
experience.
• Lessons: guide you through the learning objectives and provide the key points that are critical to
the success of the in-class learning experience.
• Labs: provide a real-world, hands-on platform for you to apply the knowledge and skills learned
in the module.
• Module Reviews and Takeaways: provide on-the-job reference material to boost knowledge
and skills retention.
• Lab Answer Keys: provide step-by-step lab solution guidance.
Course Companion Content: searchable, easy-to-browse digital content with integrated premium
online resources that supplement the Course Handbook.
• Modules: include companion content, such as questions and answers, detailed demo steps and
additional 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
most current premium content on TechNet, MSDN®, or Microsoft® Press®.
Note: For this version of the Courseware on Prerelease Software (specify RC0/Beta etc.),
Companion Content is not available. However, the Companion Content will be published when
the next (B) version of this course is released, and students who have taken this course will be
able to download the Companion Content at that time from the
http://www.microsoft.com/learning/companionmoc site. Please check with your instructor
when the ‘B’ version of this course is scheduled to release to learn when you can access
Companion Content for this course.
Student Course files: includes the Allfiles.exe, a self-extracting executable file that contains all
required files for the labs and demonstrations.
Note: For this version of the Courseware on Prerelease Software (specify RC0/Beta etc.), Allfiles.exe
file is not available. However, this file will be published when the next (B) version of this course is
released, and students who have taken this course will be able to download the Allfiles.exe at that
time from the http://www.microsoft.com/learning/companionmoc site.
• Course evaluation: at the end of the course, you will have the opportunity to complete an
online evaluation to provide feedback on the course, training facility, and instructor. To provide
additional comments or feedback on the course, send an email to support@mscourseware.com.
To inquire about the Microsoft Certification Program, send an email to mcphelp@microsoft.com.
MCT USE ONLY. STUDENT USE PROHIBITED
iv About This Course
Note: At the end of each lab, you should close the virtual machine and not save any
changes. To close a virtual machine (VM) without saving the changes, perform the following
steps:
2. In the Close dialog box, in the What do you want the virtual machine to do? list, click
Turn off and delete changes, and then click OK.
The following table shows the role of each virtual machine that is used in this course; another set of virtual
machines that end in -02 are for use in the module 2 labs only:
20336A-LON-ROUT1-03 Router
Software Configuration
The following software is installed on the various VM’s:
Course Files
The files associated with the labs in this course are located in the X:\Labfiles\LabXX folder on the student
computers.
Classroom Setup
Each classroom computer will have the same virtual machine configured in the same way.
• 64 bit Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) processor (2.8 Ghz
dual core or better recommended)
• Dual 500 GB hard disks 7200 RPM SATA or faster (striped). Note that the course can run using a single
120GB hard disk if dual 500BG disks are not available.
• 16GB RAM.
• DVD drive (dual layer recommended)
• Network adapter with Internet connectivity
• Dual SVGA monitors 17” or larger supporting 1440X900 minimum resolution
• Video adapter that supports 14400 x 900 resolution
• Microsoft Mouse or compatible pointing device
• Sound card with amplified speakers
• Approved Microsoft Lync Headset (optional)
• In addition, the instructor computer must be connected to a projection display device that supports
SVGA 1024 x 768 pixels, 16 bit colors.
MCT USE ONLY. STUDENT USE PROHIBITED
About This Course
vi
MCT USE ONLY. STUDENT USE PROHIBITED
1-1
Module1
Architecture and Design Approach for Microsoft Lync Server
2013
Contents:
Module Overview 1-1
Module Overview
Microsoft® Lync® Server 2013 offers several enhancements to server roles and client features, and new tools for
administration. You should understand the overall architecture of Lync Server 2013 and the core capabilities
offered. This understanding will help you plan and design a Lync Server 2013 implementation that meets
organizational and user needs. You should also be familiar with the key features and functionality of Lync Server
2013, and with Microsoft Solutions Framework (MSF), which requires a structured approach to project
management and execution.
Objectives
• Describe the overall server and client Lync Server 2013 architecture.
Lesson 1
Overview of Lync Server 2013 Architecture
Lync Server 2013 introduces many new features and significant enhancements to existing features and
functionality of the previous versions. To use Lync Server 2013, you should understand its architecture,
and be able to use the server features, client features, and administrative tools. This will help you to better
plan and design a Lync Server 2013 implementation that meets organizational needs. You should also
know about the enhancements in call routing, hosted voice, mediation server and gateway topologies, call
translation rules, and call management, which have improved Enterprise Voice. Lync Server 2013 is built
on a Session Initiation Protocol (SIP)–based foundation, and you should know how Lync Server 2013 uses
SIP to create, modify, and terminate the sessions.
Lesson Objectives
After completing this lesson, you will be able to:
Deployment Options
When you plan for Lync, you should first
determine how to deploy Microsoft Lync—as Lync
Server 2013 on premises, or Lync Online—with
Microsoft Office 365 in the cloud.
• Lync Hybrid (Split Domain). In a full Lync Hybrid, a single domain is shared across on-premises and
online deployment, and requires a Lync 2013 tenant in Office 365. Lync 2013 introduces new
scenarios for hybrid deployments. As available now in Office 365, it will be able to have Exchange
going to the cloud while keeping Lync on-premises. The value of hybrid scenarios in Lync 2013 is the
possibility to be able to either migrate everybody or just a subset of users to Lync Online from Lync
Server 2010 on-premises. It is therefore possible to imagine that some users will be moved to the
cloud based on their location or their usage profile.
• The goal of Lync 2013 Hybrid architecture is to offer multiple scenarios where most of the existing
and new customers can fit in, based on their technical and functional needs. By knowing the features
that are available in the cloud and what gets migrated between on-premises and online deployments,
you can make the migration scenario clear and predictable.
Which is the best type of deployment will depend on the workloads you want to deploy, and the
geographical and business status of your organization.
• The 64-bit edition of Windows Server 2012 Standard, the 64-bit edition of Windows Server 2012
Enterprise, or the 64-bit edition of Windows Server 2012 Datacenter
• Edge Server
• Mediation Server
• Director
• Persistent Chat front-end server
The Standard Edition server enables you to use instant messaging (IM), presence, conferencing, and
Enterprise Voice, all running on one server. For a high-availability solution, use Lync Server Enterprise
Edition.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-5
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. A pool of multiple servers running the same role provides
scalability and failover capability.
The front-end server includes the following features:
• Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call
error records (CERs). This information provides metrics about the quality of the media (audio and
video) traversing your network for both Enterprise Voice calls and A/V conferences.
• Web components to supported web-based tasks such as web scheduler and join launcher.
• Optionally, Archiving, to archive IM communications and meeting content for compliance reasons.
• In Lync Server 2010 and prior versions, Monitoring and Archiving were separate server roles, not
collocated on the front-end server.
• Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management
and Persistent Chat Web Services for File Upload/Download.
Front-end pools are also the primary store for user and conference data. Information about each user is
replicated among three front-end servers in the pool, and backed up on the back-end servers.
Additionally, one front-end pool in the deployment also runs the Central Management Server, which
manages and deploys basic configuration data to all servers running Lync Server. The Central
Management Server also provides Lync Server Management Shell and file transfer capabilities.
The back-end servers are database servers running Microsoft SQL Server that provide the database
services for the front-end pool. The back-end servers serve as backup stores for the pool users, and for
conference data, and they are the primary stores for other databases such as the Response Group
database. You can have a single back-end server, but a solution that uses SQL Server mirroring is
recommended for failover. Back-end servers do not run any Lync Server software.
Note: We do not recommend collocating Lync Server databases with other databases. If
you do so, availability and performance may be affected. Information stored in the back-end
server databases includes presence information, users' Contacts lists, conferencing data, including
persistent data about the state of all current conferences, and conference scheduling data.
Edge Server
Edge Server enables your users to communicate and collaborate with users outside the organization’s
firewalls. These external users can include the organization’s own users who are currently working offsite,
MCT USE ONLY. STUDENT USE PROHIBITED
1-6 Architecture and Design Approach for Microsoft Lync Server 2013
users from federated partner organizations, and outside users who have been invited to join conferences
hosted on your Lync Server deployment. Edge Server also enables connectivity to public IM connectivity
services, including Windows Live, AOL, Yahoo!, and Google Talk.
Deploying Edge Server also enables mobility services, which supports Lync functionality on mobile
devices. Users can use supported Apple iOS, Android, Windows Phone, or Nokia mobile devices to
perform activities such as sending and receiving instant messages, viewing contacts, and viewing
presence. In addition, mobile devices support some Enterprise Voice features, such as click to join a
conference, Call via Work, single number reach, voice mail, and missed calls. The mobility feature also
supports push notifications for mobile devices that do not support applications running in the
background. A push notification is a notification that is sent to a mobile device about an event that occurs
while a mobile application is inactive.
Edge Servers also include a fully-integrated Extensible Messaging and Presence Protocol (XMPP) proxy,
with an XMPP gateway included on front-end servers. You can configure these XMPP components to
enable your Lync Server 2013 users to add contacts from XMPP-based partners (such as Google Talk) for
instant messaging and presence.
Mediation Server
Mediation Server is a necessary component for implementing Enterprise Voice and dial-in conferencing.
Mediation Server translates signalling, and in some configurations, media between your internal Lync
Server infrastructure and a public switched telephone network (PSTN) gateway, IP-PBX, or a Session
Initiation Protocol (SIP) trunk. You can run Mediation Server collocated on the same server as front-end
server, or separated into a stand-alone Mediation Server pool.
Director
Directors can authenticate Lync Server user requests, but they do not host user accounts or provide
presence or conferencing services. Directors are most useful to enhance security in deployments that
enable external user access. The Director can authenticate requests before sending them to internal
servers. In the case of a denial-of-service attack, the attack ends with the Director and does not reach the
front-end servers.
Question: What are the four functions managed by the front-end server?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-7
Lync 2013
Lync 2013 is the full-featured client for Lync
Server. The Lync 2013 user interface has been
redesigned and includes newly integrated features,
such as persistent chat (Lync 2010 had a separate
client for chat functionality), tabbed conversations,
video preview, and multiparty video.
Lync 2013 client setup is part of the Microsoft Office setup program on the installation media.
Because of the enhancements to Lync Web App, an updated version of Microsoft Lync 2010 Attendee is
not available for Lync Server 2013. Lync Web App is the client of choice for participants outside your
organization. With Lync Web App, no local client installation is required, although audio, video, and
sharing features require installation of a plug-in during first use.
• Lync 2010 Mobile. Lync Server 2013 supports all Microsoft Lync 2010 mobile apps. Microsoft Lync
2010 Mobile provides IM, enhanced presence, and telephony for users in your organization who are
connecting from a smartphone or a phone running a Professional edition of Windows Mobile. You
can instruct your users to install Microsoft Lync 2010 Mobile by directing them to the app
marketplace for their mobile phone.
• Lync Phone Edition. Lync Phone Edition software for intelligent IP phones (for example, USB-attached
phones) has not been updated for Lync Server 2013. Lync Phone Edition continues to be supported
for placing and receiving calls, enhanced presence, and client audio capabilities for conferences.
• Lync 2010 Attendant. The Microsoft Lync 2010 Attendant integrated call-management program
enables a receptionist to manage multiple conversations at the same time through rapid call
handling, IM, and on-screen routing.
Question: Which Lync Server 2013 clients can be used without Lync 2013 to participate in
online conferences?
• Lync Server Control Panel. Use for on-going management of your deployment by using a web-based
interface.
• Lync Server Management Shell. Use for on-going management of your deployment by using the
command line.
You can manage your deployment by primarily using Topology Builder and Lync Server Control Panel.
Deployment Wizard
You must use the Lync Server Deployment Wizard included on the installation media to install all
administrative tools onto a computer on which you have not already installed Lync Server. During the
administrative tools installation process, the Lync Server Deployment Wizard is installed locally, along with
the other tools so that you can later use it to install files for additional components, or remove files for
components that you do not want on the computer.
Topology Builder
For details about deployment tasks that you can perform by using Topology Builder, see the Deployment
documentation for each server role.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-9
Lync Server Control Panel is automatically installed on every Lync Server front-end server or Standard
Edition server. In this release, you administer Edge Servers remotely. You can also install Lync Server
Control Panel on another computer, such as a management console from which you want to centrally
manage Lync Server.
Note: To configure settings by using Lync Server Control Panel, you must be logged on by
using an account that is assigned to the CsAdministrator role. To configure settings by using Lync
Server Control Panel, you must use a computer with a minimum screen resolution of 1024 x 768.
Logging Tool
The Lync Server Logging Tool facilitates troubleshooting by capturing logging and tracing information
from the product while the product is running. You can use the tool to run debug sessions on any Lync
Server server role.
For more information about the Logging Tool, see the Lync Server 2010 Logging Tool
documentation on the TechNet Library at:
http://go.microsoft.com/fwlink/p/?linkId=199265
To administer servers and services, you can use Lync Management Shell or Lync Server 2013 Control Panel
to update the settings in the Central Management Database. The Central Management Database
replicates these configuration changes to all the servers in your deployment.
You can store user information in Microsoft Active Directory® Domain Services (AD DS) and the Central
Management Database. You can use AD DS to store basic Lync Server 2013 user information, such as the
user’s SIP Uniform Resource Identifier (URI) and phone number. You can use the Central Management
Database to store user policy information. Using AD DS provides backward compatibility with earlier
versions of Lync Server 2013.
The central management server runs on one server in a front-end server pool in a Lync Server 2013
Enterprise Edition–based deployment or on a single front-end server in a Lync Server 2013 Standard
Edition–based deployment.
Question: Where does the Central Management Database replicate configuration changes
to? How is that beneficial?
SIP Definition
The abstract of RFC 3261 defines SIP as an application-layer control or signaling protocol for creating,
modifying, and terminating sessions between one or more participants. These sessions include Internet-
based telephone calls, multimedia distribution, and multimedia conferences. You can use SIP to set up
media sessions of any kind and not just telephony, modify the sessions while they are on, and then
terminate the connections after the sessions are complete. For example, a participant can start an instant
messaging session with another participant, add audio, and then video to the existing call, and finally
terminate it. There is more to SIP than just handling media; SIP can be extended to perform multiple tasks.
For example, SIP can manage the publishing and requesting of Presence information and the delivery of
instant messages.
Because of the dynamic evolution of Unified Communications, Lync Server 2013 and similar products are
not just based on RFC 3261, but also on the 200 or more IETF Internet drafts and proposed standards, and
SIP-related RFCs. Unified Communications products are based on a range of these RFCs. The following
table describes some drafts and standards that Lync Server 2013 is built on.
RFC/Draft Description
There are many more RFCs and if you are interested in knowing more about the standard and non-
standard protocols that are used and how they are used, you can read the Microsoft Office protocol
documents on the Microsoft website.
Question: What do you think are the benefits of using a SIP-based foundation in your
organization?
MCT USE ONLY. STUDENT USE PROHIBITED
1-12 Architecture and Design Approach for Microsoft Lync Server 2013
Federation must use a Lync 2010+ Federation Edge, which must route traffic to a Lync 2010+ pool. If the
company is only using OCS 2007 R2, it will have to deploy Lync 2010 or Lync 2013 to be able to federate
with Office 365, in case the company wants to deploy a Hybrid scenario or wants to migrate existing on-
premises users to the cloud.
When looking at this type of architecture, it is important to keep in mind that redundancy is important.
Edge and the next-hop pool must be redundant to ensure that flow between on-premises and online
deployments will not stop, when a single server failure occurs.
• Voice Mail. Lync Server 2013 introduces Voice Mail Escape, an enhancement for managing voice mail.
You can use the feature to detect when a call has been routed to voice mail, and you can prevent the
call from being immediately routed to the user’s mobile phone voice mail without giving the user the
opportunity to answer the call. This scenario occurs when the user enables simultaneous ringing to
their mobile phone, and their mobile phone is turned off, out of battery, or out of range. Voicemail
Escape detects that the call was immediately answered by the user’s mobile phone voice mail, and
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-13
disconnects the call to the mobile phone voice mail. The call continues to ring on the user’s other
endpoints, giving the user the opportunity to answer the call. If the user does not answer the call, the
call is routed to the corporate voice mail.
• M:N routing. This is a gateway that can point to multiple Mediation servers.
• Response Group Service (RGS) manager. This role is dedicated for day-to-day use.
• Inter-trunk routing. This allows Lync to be at the center of a voice deployment. Lync can receive a call
on a trunk and send it on another trunk if the called number is not a Lync user.
• Lync now supports IPV6 deployment. but we recommend that you use dual-stack IPV6/IPV4 to allow
all scenarios (coexistence, third party interop, and so on).
• A/V support in VDI environment. A/V is directly captured on the local computer.
MCT USE ONLY. STUDENT USE PROHIBITED
1-14 Architecture and Design Approach for Microsoft Lync Server 2013
Lesson 2
Overview of Lync Server 2013 Core Capabilities
Lync 2013 is a single unified client that provides a Unified Communications solution with features such as
IM, Presence, voice, video, and web conferencing. You need to know how the conferencing clients, Lync
2013 Web App and Lync 2013 Attendee, can be used in remote scenarios. By knowing about the
capabilities of Lync Server 2013, you can better plan for your deployment for internal and external users.
You should also know about the various scenarios in which external users need to access the Lync Server
2013 deployment, and how you can plan for it, based on the support provided for internal and external
users in Lync Server 2013.
Lesson Objectives
• Describe the features of Lync 2013.
Me Area
The Me area provides location enhancements, activity feed, and photo features. Lync 2013 can detect the
location of users as they travel between home and work, thereby allowing their contacts to see whether
they are on the road or in a different building. In case of an emergency, E9-1-1 services can find users
easily.
Contact Card
Lync 2013 offers an extended contact card that shows information about the user, the organization, or
distribution groups. Users can display contacts by group, availability, or by level of privacy, with or without
photos. They can start conversations and meetings from the Contacts list just by pointing to the contact.
Contacts can be searched by using keywords such as a contact’s title, team, or other expert quality that
might appear on their contact card.
Privacy Enhancements
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-15
Users can assign various levels of access to their contacts depending on their relationship with them, such
as Family or Workgroup. Enhanced presence and privacy relationships allow organizations to show
Presence for individuals who have been explicitly added to contact lists.
Polling
The polling feature enhances collaboration by enabling presenters to quickly determine participants’
preferences. During online meetings and conversations, presenters can use polling to gather anonymous
responses from participants. Presenters can view poll results and choose to show or hide the results to the
attendees.
Joining meetings is faster. After a user has installed Lync 2013, the user typically takes less than two
seconds to join a meeting. Users can easily schedule meetings and invite others before and during
meetings.
Video Enhancements
Lync 2013 provides video controls and full-screen video experience. Lync Server 2013 also supports
panoramic video, multipoint video, subscription video, Video Graphics Array (VGA), and high definition
(HD) video in conferences.
• Video is enhanced with face detection and smart framing, so that a participant’s video moves to help
keep them centered in the frame.
• High-definition video is now supported in two-party calls and multiparty conferences. Users can
experience resolutions up to HD 1080p.
• Participants can select from different meeting layouts. Gallery View shows all participants’ pictures or
videos; Speaker View shows the meeting content and only the current speaker’s video or picture;
Presentation View shows meeting content only; Compact View shows just the meeting controls.
• With the new Gallery feature, participants can see multiple video feeds at the same time. If the
conference has more than five participants, video feeds of only the most active participants appear in
the top row, and pictures appear for the other participants.
MCT USE ONLY. STUDENT USE PROHIBITED
1-16 Architecture and Design Approach for Microsoft Lync Server 2013
• Participants can use video pinning to select one or more of the available video feeds to be visible at
all times.
• Presenters can use the Video Spotlight feature to select one person’s video feed so that every
participant in the meeting sees that participant only.
Administrative Enhancements
Lync 2013 provides support for delegate features so that delegates do not have to switch between Lync
2013 and the Lync 2013 Attendant console. Also, in Lync 2013, a delegate can support multiple managers
and use collaboration tools such as application sharing and file transfer, which are not supported by the
Lync 2013 Attendant console.
Diagnostics
Pre-call and in-call diagnostics alert users when network quality is poor. During a call, twelve types of
audio quality issues from network, computer, and device sources are diagnosed and communicated to
users. For example, if a user gets a message that the call quality is poor; the user can quickly switch to a
landline phone or mobile phone.
Delegates can support their manager easily by using Lync 2013. Shared lines and the ability to interrupt
the manager at any time, and quick transfer of the line empower delegates with the access they need.
Response group handling of calls is enhanced to support anonymous agents. Response group agents can
answer calls anonymously so that the workflow is not circumvented by callers who use a direct line.
Lync 2013 provides all the functions of a traditional PBX system, in addition to useful productivity
features. The Lync 2013 user interface (UI) includes a tally of the number of missed calls and voice mail
that alerts the user of recent activity. The Phone tab provides a list of voice mails and call logs, and an on-
screen dial pad.
Office and Windows 8 Integration
A user’s contacts, instant messaging, and sharing content are available in Microsoft® Office 2013
applications, including Microsoft® Office Outlook, Microsoft® Office Word 2013, Microsoft® Office
PowerPoint 2013, Microsoft® Office Excel 2013, and Microsoft® SharePoint® 2013.
Start a conversation
Add computer X X X X
audio
Add video X X X X
View in multiparty X X X
video
Use in-meeting X X X
presenter controls
Access detailed X X X
meeting roster
Participate in X X X
multiparty IM
Add anonymous X X
participants (if
enabled)
Initiate a meeting X X
MCT USE ONLY. STUDENT USE PROHIBITED
1-18 Architecture and Design Approach for Microsoft Lync Server 2013
Add Microsoft X X X
PowerPoint files
Navigate X X X
Microsoft
PowerPoint files
Use OneNote X X
meeting notes
Use a whiteboard X X X
Conduct polls X X X
Share files X X X
• Public IM users. Are users who use IM services, such as Windows Live™ Messenger. The specific public
IM provisioning process ensures that IM users can interact with Lync Server 2013. To configure public
IM connectivity with public IMs such as Windows Live Messenger, you may need to have a separate
license, depending on your licensing model.
• Anonymous users. Are users who have received invitations to participate remotely in a conference,
regardless of whether they have a user account in your organization's AD DS or in a supported
federated domain.
• XMPP users. Are users who have an account on an XMPP-based system. Edge Server introduces a fully
integrated XMPP proxy (deployed on the Edge Servers) and an XMPP gateway (deployed on your
front-end servers). You can deploy XMPP federation as an optional component. By adding and
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-19
configuring the XMPP proxy and XMPP gateway, you can enable your Microsoft Lync 2013 users to
add contacts from XMPP-based partners for instant messaging (IM) and presence.
Question: Based on your experience, what is your opinion about firewall traversal of
communications, including audio, video, and files?
• Web conferencing. Meeting organizers can invite remote users, federated users, and anonymous users
to web conferences as either presenters or attendees. Presenters can share applications or their
desktop with federated users, and they can give control to federated users.
• Audio/video conferencing. Meeting organizers can specify whether audio and video of the meeting
needs to be hosted for conferences on the internal Lync Server 2013 deployment.
• IM and Presence. Users can send instant messages and view Presence status without using a VPN to
log on to the internal network. They can add users from federated partners and users of supported
public IM service providers to their contact list. They can also view those users’ Presence status, even
while they are signed in remotely.
• Web conferencing. Users can participate in web conferences as if they were logged on to the internal
network.
• Audio/video conferencing. Users can participate in audio/video conferences as if they were logged on
to the internal network.
• IM and Presence only. Users can participate in IM conversations with individual Lync Server 2013 users
in the organization and access Presence information. However, they cannot participate in Lync Server
2013 multiparty conferences, and they are restricted to peer-to-peer conferencing. You can choose
this option whether or not you deploy conferencing support internally.
MCT USE ONLY. STUDENT USE PROHIBITED
1-20 Architecture and Design Approach for Microsoft Lync Server 2013
• IM and Presence, web conferencing, and A/V conferencing. Users can participate in IM conversations
with individual Lync Server 2013 users in the organization and access Presence information. They can
also participate in web conferences and audio/video conferences, if you have planned for it in your
Lync Server 2013 deployment. Federated users have access to the full feature set, except the Lync
Server 2013 address book.
• IM and Presence only. Users can participate in IM conversations with individual Lync Server 2013 users
in the organization and access Presence information. However, they cannot participate in Lync Server
2013 multiparty conferences, and they are restricted to peer-to-peer conferencing.
Lesson 3
Introduction to the Lync Server 2013 Design Process
The various phases of a Lync Server 2013 deployment are envisioning, planning, stabilizing, deploying,
and operating. Though the sequence of these phases may vary from project to project, the underlying
objective is to manage the deployment in a structured manner. By understanding these phases and
knowing how to convert business drivers into actual functionality, you can effectively meet organizational
requirements and user needs. You must get stakeholder consensus on key aspects and decisions in the
deployment. You must also plan for user education. This is necessary to ensure that users are aware of all
the Lync 2013 features to best meet the organizational business goals.
Lesson Objectives
• Describe the phases of the deployment process of Lync Server 2013.
Envisioning
To determine the scope and plan the
implementation of a Unified Communications
solution such as Lync Server 2013, you should
implement the project in several phases. You can create one or more phases between the initial-state
deployment and the end-state deployment, based on organizational needs. The decisions on phasing and
how to phase your Unified Communications project is usually an iterative process that is based on the
business and technical requirements of the organization.
Planning
During planning, you need to plan for infrastructure requirements and for any dependencies related to
the basic requirements for Lync Server 2013. Based on these decisions, your plan will further evolve to
include external user access and voice requirements. Decisions on external user access and voice
requirements depend on the phasing decisions made in the Envisioning phase.
Stabilizing
The outcome of the Envisioning and Planning stages is the functional specification of the design
document. At this stage, you need to validate the assumptions made during planning on how users will
use the Lync Server 2013 solution. You also need to test and validate the technical assumptions
MCT USE ONLY. STUDENT USE PROHIBITED
1-22 Architecture and Design Approach for Microsoft Lync Server 2013
underlying the design solution. For example, you might need to test whether Lync Server 2013 integrates
well with gateways and whether the current firmware versions can coexist and work in various scenarios.
Stabilizing also involves acquiring support resources and finalizing the design, before you deploy the Lync
Server 2013 solution.
Deployment
The Deployment phase may vary in Lync Server 2013 implementations, based on the actual
implementation. In some scenarios, it will include migration from previous versions of Lync Server 2013.
You can begin deployment by preparing Microsoft Active Directory, implementing the Central
Management Database, and then implementing the first Lync Server 2013 front-end server pool. In the
Standard Edition, you need to prepare the first Standard Edition Server that also includes the Central
Management Database.
Operation
You do not usually plan for operations during planning. However, identifying new operational procedures
or changing existing operational procedures is an important part of the planning phase. If you identify
these operational procedures during planning, your implementation will be successful, because all
stakeholders will have the required documentation ready, and this helps smooth transition.
Question: Does this planning process reflect the planning process you are using now? What
are you doing differently?
All these changes allow pools to scale out to more servers than Lync 2010 allowed.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-23
Internal Deployment
Most organizations start with installing and
configuring Lync Server 2013 functionality within
the organization network through local area
network (LAN), wide area network (WAN), and VPN. They deploy IM, Presence, and web conferencing
capabilities.
Small organizations can install Lync Server 2013 Standard Edition, which provides them with most of the
features of Lync Server 2013, except external user access and voice telephony. Organizations that require
redundancy can start with a pilot project, and then proceed to production. If they anticipate the need for
redundancy or the need for additional servers to provide more capacity when moving to production, they
can deploy a single-server Enterprise Edition installation of Lync Server 2013. This installation comprises
one front-end server and a back end Microsoft® SQL Server®. In this installation, it is very easy to add a
secondary server and then implement DNS load balancing and hardware network load balancing for both
servers, rather than migrate from a Lync Server 2013 Standard Edition installation.
Although it is possible to deploy video at this stage, many organizations do not pursue this in the
beginning, because of the bandwidth requirements for video. Also, implementing video adds to
complexity. Implementing instant messaging and Presence is an easy way to start the deployment, and is
easily accepted. IM and its success in the organization can be used as a driver for additional functionality.
External Deployment
Performing the Edge Server deployment for external scenarios can be quite challenging, primarily because
of firewall implementation issues. Because of these challenges, some organizations deploy external
scenarios many months after the internal deployment has been completed and rolled out to users. With
Lync Server 2013, the planning and deployment of Edge Scenarios has been simplified and this will
probably change this timeframe considerably.
In some organizations, PSTN Dial-in Conferencing and Edge Server deployment are deployed at the same
time because they complement each other. With both options available, users can easily join a web
conference, in various situations. An external user who has been invited to a web conference, an internal
user who is driving toward work, and an internal user without access to a computer can join the meeting.
qualified SIP-to-PSTN gateway or SIP Trunking. In all voice deployments, but especially when
implementing Direct SIP and Remote Call Control (RCC), possessing knowledge on SIP is a great
advantage, because you can debug and troubleshoot any issues during integration. Enterprise Voice
deployment usually includes dial-in conferencing, if it has not already been deployed.
Sequence of Phases
The following are examples of the possible order of sequence for deployment:
• Internal deployment, external deployment, PSTN dial-in conferencing, and then Voice
• Internal deployment and voice deployment, and then external deployment
The order of Lync Server 2013 deployment depends on the business drivers of the organization. If an
organization’s main business driver is access for remote users, work-from-home users, or traveling users,
you will need both internal and external deployments, simultaneously.
Question: How can you plan for challenges in funding issues when implementing a Lync
Server 2013 solution in an organization?
You need to ask the right questions, which will help you determine the key driver for the deployment.
Determining the key driver helps you determine how to execute the project in various phases, and the
sequence of these phases.
Note: At the writing of this section, the Lync 2013 Planning Tool had not been released yet.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-25
Answers to these questions indicate the various scenarios and the related functionality that you should
implement to support these scenarios. You can identify the functionalities that are mandatory and those
that are optional.
• Network. Involves decisions about DNS, firewalls, VPN, public key infrastructure (PKI), and Internet
service providers (ISPs).
• Server. Involves decisions about Active Directory, including identity management and provisioning,
and Exchange Server, backup, and monitoring requirements.
• Client Desktops. Involves decisions about installing Windows operating system, Microsoft Office, or
other applications.
• Education. Involves decisions about user education, Help Desk team member education, and
education for overall operations personnel.
• Operations. Involves decisions about handling change management, processes, and working toward
the use of Lync Server 2013 for organization-wide operations.
• Telephony. Involves decisions about whether to deploy Enterprise Voice and PSTN connectivity for the
Lync Server 2013 implementation.
Lync Server 2013 is a Unified Communication–based solution, that involves dependencies on both
Microsoft-based and non-Microsoft infrastructure services. Therefore, you must involve stakeholders
related to these areas in your project. You also need to rely heavily on the stable operations of these
infrastructure areas. The following are some of the key areas that you must consider during a Lync Server
2013 implementation:
Firewall
Deploying Lync Server 2013 for internal use in an organization is usually not too complicated. However,
some organizations may have specific requirements for firewalls between different organizational
departments, regions, or countries. For example, financial institutions operating in Switzerland, Gibraltar,
and other countries have requirements for keeping archiving of voice and IM local to the country.
MCT USE ONLY. STUDENT USE PROHIBITED
1-26 Architecture and Design Approach for Microsoft Lync Server 2013
Network
If you want to implement IP telephony platform and audio/video conferencing in your Lync Server 2013
solution, you will require coordination with and cooperation of the Network department. To achieve good
and consistent voice and video quality, the network, devices, gateways, and servers need to function well.
To facilitate this, Lync Server 2013 supports network layer traffic management by using call admission
control, and end-to-end monitoring and troubleshooting of voice quality by using the Monitoring Server
role.
If IP telephony is already deployed in the organization, the required network support may already be
available for IP telephony. However, you may not be able to directly re-use the solution with Lync Server
2013 because Lync Server 2013 may not support the standards that the current IP telephony solution uses.
For example, Lync Server 2013 does not support Resource Reservation Protocol (RSVP).
Telephony
If you plan to include telephony in the Lync Server 2013 deployment, you might need to manage a few
people-related soft-skill issues. In many organizations, when telephony is introduced as part of the Lync
Server 2013 solution, the telephone department may resist the changes. Some of the reasons for their
resistance may be valid, while others may originate from a failure to correctly interpret the Lync Server
2013 approach to voice, or a lack of comprehension for the troubleshooting tools available for design and
capacity planning.
Educating Stakeholders
The best method to manage these technical and nontechnical issues is to educate all stakeholders on the
Lync Server 2013 solution. If you are only familiar with Microsoft infrastructure products, you should
attempt to know more about telephony and be familiar with the telephony terminology. You can read
beginners guides on Voice over IP and legacy PSTN/Time Division Multiplexing (TDM) telephony
terminology to know more about these subjects.
Hiring Help
If the organization hires an experienced Lync Server 2013 telephony consultant, at least during the initial
phases of the project, it may be easier to deal with some of the technical and nontechnical challenges.
These consultants could be experts who have passed the Microsoft Unified Communications (UC) Voice
Specialization Exam and/or partners who are members of the Microsoft Voice Partner Program (VPP).
They might also have passed the Microsoft Certified Master Exam and have a thorough understanding of
the Lync 2013 product.
Management Support
Support from senior management is vital for the success of the project. With good support from the
management, you can easily transition from the current environment to a full-fledged UC solution that
also contains voice. Management support is beneficial throughout the project, especially in providing the
right direction to all stakeholders.
Question: Have you seen issues with lack of stakeholder participation in other projects?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-27
What has been your experience in trying to educate users about UC-based solutions?
• You can deliver user education through various methods. Delivering training to several thousand
users can be quite challenging. Using the standard classroom training may not be possible or
effective. Therefore, delivering online training through e-learning or video-based training is an
option. Microsoft provides a few Quick Start guides and question/answer cards on Lync Server 2013
and Unified Communications, which you can use for user training.
• Departmental and inter-departmental meetings can be organised by using Lync Server 2013 so that
users experience the benefits from the solution. User training can also be held by using Lync 2013
meetings so that users can experience how the product can be used in real-time. Evangelists for
Unified Communications can be identified in the organization to help users who have queries about
Lync 2013 or have challenges in using some features, such as web conferencing or audio/video
conferencing.
RASK uses an intuitive framework with valuable resources and prescriptive guidance to ensure that these
critical components are considered, incorporated, and properly aligned from the earliest stages of your
technical deployment through run state operations.
MCT USE ONLY. STUDENT USE PROHIBITED
1-28 Architecture and Design Approach for Microsoft Lync Server 2013
RASK is organized into 3 core components: Rollout phases, Readiness focus areas, and the Deployment
readiness report. Together, these components create a flexible framework that is easy to
customize according to the unique characteristics of your organization, and that is relevant to
deployments of almost any size or complexity.
Lesson 4
Assessing Infrastructure Requirements and Updating the
Design
A Lync Server 2013 design contains various components. Before you begin deploying Lync Server 2013,
you should assess the current network and infrastructure of your organization. This will help you to plan,
design, and implement Lync Server 2013 so that it works well for your organizational needs. You need to
assess session initiation protocol (SIP) domains and update the design accordingly. You will also need to
assess Exchange Server integration, client integration, and voice requirements, and update your design
during the planning phase. In addition, you will need to analyze the importance of documenting the
business and technical requirements.
Lesson Objectives
• Describe the components of a Lync Server 2013 design.
• Assess SIP domains and update the design.
Conceptual Design
The conceptual design depicts the functionality of each major feature of the solution. It captures how the
solution will work for both users and administrators. The design team needs to consider the needs of all
user profile groups when designing the solution. To determine user needs correctly, the design team must
have a clear understanding of the requirements. You can perform requirements analysis by reviewing the
documents that you develop during Envisioning, include the following:
• Business requirements
• User requirements
MCT USE ONLY. STUDENT USE PROHIBITED
1-30 Architecture and Design Approach for Microsoft Lync Server 2013
• Usage scenarios
• Operational requirements
• System requirements
The design team incorporates these requirements in terms of descriptions that eventually become part of
the functional specification. You then need to convert the conceptual design into a logical design.
Logical Design
The logical design provides information on components and roles of the architecture, component
behavior, and relationship between the components. In the logical design, you need to convert the
content from the conceptual design to an abstract model that highlights the logical objects and entities of
architecture. For example, in an infrastructure project, the architecture can include a series of block
diagrams showing networks, service components, and network connection elements. You can show
components that are out of scope of the project, but may interact with the subject of the migration. The
logical design helps in refining the requirements that were created in the conceptual design. You now
need to implement the physical design from the logical design.
Physical Design
The physical design of the solution specifies the logical objects that fit into specific physical objects of
architecture. The physical design includes the anticipated metrics to assess performance goals, uptime
goals, and milestones of the solution. For example, the physical design might include metrics for network
performance and the requirements to meet these metrics. You might also need to establish the
production metrics for various deployment scenarios. The design strategy may include how the existing
application or infrastructure implementation will be replaced by the new implementation without
violating ongoing service level agreements (SLAs). It should depict the start point of the current
organizational state until the end-state environment, showing specific deployment activities. The
deployment scenarios must show both the desired end-state and the path to reach that end-state.
You can use the Lync Server 2013 Planning Tool to create the conceptual design of your Lync Server 2013
implementation. However, before using the planning tool, you need to assess the current infrastructure
requirements in detail.
Note: The Lync 2013 Planning Tool can be found here: http://www.microsoft.com/en-
us/download/details.aspx?id=36823.
Question: How can you apply the components of design to a Lync Server 2013 project?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-31
• Determine how to choose the SIP address for users who have different email addresses, for example,
claus.hansen@contoso.com, claush@contoso.com, and claus@contososales.com.
You can ensure that there is a single SIP domain in a Lync Server 2013 deployment by planning
thoroughly and by determining effective methods to collate and make the SIP domain identical for all
users. One method to collate existing SMTP domain names is to use PowerShell script.
The following code example shows how you can gather SMTP domains that are currently in use in the
organization from Exchange Server 2007 or Exchange Server 2013.
Question: How is the SIP URI different from the mail URI?
You need to remember that Office Outlook 2013 makes remote procedure calls to resolve SIP addresses
only, if you select the Display online status next to a person name option. To view this option in Office
Outlook 2013 from the Tools menu, click Options, click Other, and then click Person Names. Choose an
Appropriate Exchange Server Communication Interface.
You can evaluate the communication interfaces used by Lync 2013 to access and update features shared
with Office Outlook 2013. Lync 2013 makes Exchange Server calls either directly, through MAPI or
Exchange Web Services (EWS), or indirectly, by using the Microsoft Office Outlook Object Model.
• On User A’s computer, Lync 2013 sends Exchange Web Services calls to determine User A’s Free/Busy
and Out of Office status.
• Lync 2013 then updates User A’s enhanced Presence data with this information.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-33
• Other Lync 2013 and Microsoft Office 2013 users can now view User A’s schedule details and Out of
Office status, if applicable.
The availability of Free/Busy and Out of Office information about a contact is also controlled by a user’s
Privacy Relationship settings.
Controlling Integration
All Outlook 2013 integration features are enabled by default, but can be controlled individually by using
Lync 2013 or by using in-band server settings.
When you plan for the Lync Server 2013 solution, you can use the in-band server settings to enable or
disable individual integration features, either during deployment or during maintenance.
You can configure most Group Policy settings in previous versions of Lync Server 2013, such as Office
Communications Server 2007, by using Windows PowerShell cmdlets, New-CsClientPolicy, or Set-
CsClientPolicy. With the new approach in Lync Server 2013 toward in-band settings, you can plan for
moving appropriate Group Policy settings from GPOs to policies. You can also plan for eventual
coexistence of policies for Lync 2013 clients and GPOs for previous versions of Lync Server 2013 clients
during migration.
• You cannot park a call from an Office Communications Server 2007 client or device.
The following table describes the Lync 2013 interoperability with meetings hosted or scheduled on
previous versions of Office Communications Server.
Joining No issues.
Question: Where would you put your effort in the client integration and to update the
design?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-35
• Devices.
During envisioning, you need to evaluate the options available for the organization, perform an initial
assessment, and make design decisions on the various methods that you plan to use. For example, some
branch offices may use Direct SIP, while others may use SIP Trunking. You need to consider such
requirements in your plan.
At this stage, it may be neither feasible nor necessary to decide on the final voice implementation design.
However, you need to create the first version of your vision and scope document. You will need to make
some initial decisions to perform a rough calculation of the project cost and expected savings for the
organization. For example, removing a PBX, which has an expensive yearly maintenance contract, would
be a tangible benefit that you can highlight to project stakeholders and senior management.
In the envisioning phase, you can leave certain options open for further investigation. For example, you
will be able to perform a more detailed technology evaluation during the planning phase. So, a decision
may also be to deliver possible solutions:
• If possible, use Direct SIP from vendor PBX to Lync Server 2013.
• Use a fall back plan of SIP-to-PSTN Gateway from PBX to Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
1-36 Architecture and Design Approach for Microsoft Lync Server 2013
• Helps stakeholders from the technical side—When the documentation of the technical design is
considered, you can use a Microsoft Office Visio diagram to effectively communicate the design
solution. Your description in the conceptual design should be simple and direct. A good conceptual
design of about 4-5 pages, which clearly records how organizational needs and user needs are going
to be met, is better than a 75-page document that stakeholders may not read.
How do you records the business requirements and ensure that they are met?
• Record the business requirements—Create a numbered list of all the requirements in the logical and
physical design, and correlate this numbered list to the conceptual design, to ensure that all
requirements are met.
Why should you receive feedback from stakeholders and update the design at key
milestones?
• Get feedback from stakeholders at every milestone—Involve stakeholders during the project at
specific milestones and show them the current planned design, and get their feedback on whether
the design will meet their needs. Their opinions help you keep the scope of the project in perspective;
and if there is a change in scope, it can be handled, as and when required.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-37
Lesson 5
Planning for all Microsoft Solutions Framework Phases
When making design decisions in the envisioning and planning phases, you need to involve the key teams
in the organizations to ensure that the Lync Server 2013 implementation meets organization needs.
Following the plan, build, deploy, and operate model, based on the Microsoft Solutions Framework (MSF),
will help you effectively use the existing processes and activities.
Migration to Lync Server 2013 can involve migration from previous versions of the product such as Office
Communications Server 2007 and 2007 R2 to Lync Server 2013, and migrating existing audio/video, web,
or voice platform to Lync Server 2013. By planning for the right migration strategy, you can ensure a
smooth transition to Lync Server 2013.
Establishing the initial state and end-state environment of the deployment at various stages can help you
effectively build a good technology plan for the organization. In addition, the functional specification
provides clarity by serving as a technical description of the solution and as a contract between the
organization and the project team.
Lesson Objectives
• Describe the importance of discussions with stakeholders during the envisioning and planning phases.
• Describe how to plan for project extensibility.
• Describe the need to decide on initial state and end-state environment of various project stages.
• Describe the components of a functional specification.
Phase 1—Envisioning
Phase 2—Planning
Phase 3—Design/Developing
Phase 4—Stabilizing
Phase 5—Deploying
Discussion Questions
Do you usually involve team members from operations during the initial envisioning
phases?
Often, team members from the operations team are not involved in initial discussions and during design.
One reason for this can be that the initial decisions of a project are taken at the business level. Then, these
business personnel, along with an IT manager or IT architect, complete most of the envisioning phase
before handing it off to the IT department. The reason why organizations do not involve team members
from the operations team is to save the time of operational resources. The design solution may not truly
reflect the scenarios at the operations’ level. Organizations should do this only if the IT manager or IT
architect is able to view the solution from an operation perspective.
The Microsoft presentation on MSF (Presentation at MSF for Danfoss.ppt) states that the reasons for
failure have very little to do with technology. The issue, instead, is with the processes people use to be
successful with technology. These reasons are not related to a single person’s capabilities, but to the way
people work together. MSF is built to improve the way people work together to deliver technology
solutions.
What benefits do you think can be reaped, if any, from the early involvement of
stakeholders other than the business and IT management, and a few select IT
architects?
Early identification of design influencing factors creates a better scoping of the actual project cost in
terms of time and material. This way, smoother deployments and roll-outs can happen during production.
Following the plan, build, deploy, and operate model will help you to effectively use the existing ITIL
processes and activities. You can use MOF for the detailed service management functions, which include
key processes. In MOF, each process has a key set of activities coupled to it. Planning for the after-life of a
project by using MSF and MOF is about designing, building, and deploying, and using the tools necessary
to refine and expand the scope of your Lync Server 2013 implementation. The MSF and MOF process
models provide guidance on how to implement value-added activities.
Most organizations face challenges in delivering IT solutions. However, MSF brings together a wide body
of experience that you can use in your projects. You can choose and customize the parts of the MSF
model that resolve your critical problems, and put those parts into practice.
Question: Are you familiar with MSF and MOF or similar frameworks? If yes, what is your
experience with them?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-41
The following is an example of a simplified description of Lync Server 2013 deployment phases:
o Audio/video
o Dial-in conferencing
The functional specification must describe, without ambiguity, the complete functionality of the solution.
Quantitative measurements should be included in the functional specification whenever possible.
Quantifying performance or business metrics in a functional specification is significant because the
information can be used to drive justifications, for example, in development and operations, for a project.
These metrics are as much a part of the specification as any other functional details. The following list
describes the information that should be included in the functional specification:
• Features. The functional specification should record the complete set of planned features for the
solution. The features of the solution should be expressed by using both words and diagrams, if
possible. Quantitative specifications for the solution, such as database capacity, concurrent user
capacity, and performance metrics should be clearly stated.
• Security Requirements. A functional specification should specify the strength of security to be used for
concepts such as transactions, including a description of any encryption standards to be used. A
description of the types and locations of the security systems should also be included.
• Legal Requirements. Legal requirements must be clearly understood and stated in the functional
specification, including what needs to be done to adhere to these requirements. For example, custom
solutions to meet a custom user scenario, a governmental requirement, or a business policy can be a
part of the legal requirement.
• Risk Analysis Documents. Risk analysis documents should include descriptions of potential impact to
the project and mitigation strategies. For example, the risk analysis documents should state what the
risk of failing to obtain necessary hardware would be, and the documents should provide a mitigation
strategy for dealing with this risk.
The following are examples of information that should not be included in a functional specification
document:
• Details of Software Architecture. Too much detail in a functional specification can overburden a
project team with extraneous facts.
• Detailed Database Schema. A high-level description of database details is sufficient to include in a
functional specification.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 1-43
Question: Are you aware of the templates and tools that Microsoft provides to create a
functional specification, and if so, do you have experience in using them?
MCT USE ONLY. STUDENT USE PROHIBITED
1-44 Architecture and Design Approach for Microsoft Lync Server 2013
Module2
Designing a Lync Server 2013 Topology
Contents:
Module Overview 2-1
Lesson 1: Planning the Infrastructure Requirements for Lync Server 2013 2-2
Module Overview
Designing a complex Microsoft® Lync® Server 2013 topology, including defining the network sites and
network regions, and sizing and placing server roles, can be challenging. The topology must adhere to
organizational compliance requirements, if any. When you design the topology, you must consider the
infrastructure requirements of the organization. To make your work easier, Lync Server 2013 provides
tools such as Planning Tool and Topology Builder to plan, design, and publish your Lync Server 2013
topology. Using these tools, you can plan and design an effective site topology. In addition, you need to
create a document of your design and update it throughout the project, by using tools such as
Microsoft® Office 2010 or 2013.
Objectives
• Plan the infrastructure requirements for Lync Server 2013.
Lesson 1
Planning the Infrastructure Requirements for Lync Server
2013
As a Unified Communications architect, when you plan for a Lync Server 2013 solution, you need to plan
for server hardware and software requirements. You must ensure that all the network and infrastructure
components work well with Lync Server 2013. Based on your evaluation of the utilization of resources, you
may need to readjust and realign your original plan, for a successful implementation.
Lesson Objectives
• Plan for server hardware in a physical server-based topology.
• Plan the network and infrastructure dependencies for Lync Server 2013.
• Plan for client hardware and software requirements.
The hardware required for each server in the Lync Server 2013 deployment varies, based on the size of the
organization, and the usage. You need to consider the user size and usage of the Lync Server 2013
functionalities in the organization. For example, if the recommendation for Lync Server 2013 Standard
Edition is a Dual Quad-Core server with 32 gigabyte (GB) of random access memory (RAM) for up to 5,000
users, the same configuration will not be required for a Lync Server 2013 implementation with 400 users,
who use only instant messaging (IM).
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-3
Based on these considerations, you need to design your Lync Server 2013 deployment with assumptions
related to hardware requirements. For example, for a design involving 5,000 concurrent users, you might
assume that at a given moment, 250 users are running web conferencing, 250 users are sharing their
desktops, 100 users are running audio/video conferencing, 750 users are using IM, and the remaining
users are dormant. Consequently, the scaling up or scaling down of hardware will depend on these
organizational needs and expected usage.
With Lync 2013 and support for Hyper-V 3.0, the hardware requirements for Lync Server 2013 remain the
same as that for a virtualized or physical deployment. If the Lync Server can be supplied with the same
hardware requirements when running in a virtual environment as if it is running in a physical environment,
the same amount of users will be supported.
Question: How do hardware requirements affect your current server procurement strategy?
• The requirements for each physical server are high, and each physical server can only run about 2-4
servers.
The choice between virtualization and physical hardware depends on your organization's virtualization
strategy, and whether these considerations will affect your deployment.
Services to manage the virtual machines. You can view and manage performance, and view components
such as disk space. You can also save a virtual machine as a template for creating other instances.
Because Microsoft System Center Virtual Machine Manager uses Windows® PowerShell™, you can create
scripts that integrate with Lync Server 2013 Management Shell to manage Lync Server 2013.
Question: How critical is it for your organization to deploy virtualization? Will the restrictions
discussed affect the decision?
Lync Server 2013 supports the 64-bit editions of the following operating systems:
• Microsoft® Windows Server 2008 R2 Standard operating system
By default, Lync Server 2013 administrative tools are installed on the server running Lync Server 2013.
However, you need to install administrative tools separately on computers that run Windows operating
systems.
• Microsoft SQL Server® 2008 with SP1 Enterprise database software (64-bit Edition)
• Microsoft SQL Server® 2008 Express (64-bit Edition), only for Standard Edition server, which is
automatically installed by Lync Server 2013 on each Standard Edition server
Lync Server 2013 only supports SQL Server database mirroring. To use the Monitoring Server role, you
need to install SQL Server Reporting Services. You cannot use SQL Server Web Edition, SQL Server
Workgroup Edition, and database clustering with Lync Server 2013.
Question: Which components of your Lync Server 2013 require a plan for software support?
If your organization is running in a resource forest model, you should deploy Forefront Identity Manager
or similar directory synchronization software, to support your forest model.
MCT USE ONLY. STUDENT USE PROHIBITED
2-6 Designing a Lync Server 2013 Topology
• Windows Server 2003 operating system with SP1 stand-alone CA. Although this certificate is
supported by Lync Server 2013, we do not recommend it.
Certificates issued from a public CA:
• If there is no internal certificate infrastructure available, you will need to either deploy a certificate
infrastructure or buy certificates. You can speed up the deployment process by buying certificates
externally with one year expiration until you have your own certificate infrastructure ready.
• Allow clients to discover the front-end pool or Standard Edition server that is used for various Session
Initiation Protocol (SIP) transactions.
• Associate simple URLs for conferences with the servers hosting those conferences.
• Allow external servers and clients to connect to Edge Servers or the HTTP reverse proxy for IM or
conferencing.
• Enable unified communications (UC) devices that are not logged on to discover the front-end pool or
Standard Edition server running the Device Update service, to obtain updates and send logs.
• Enable external servers and clients to connect to Edge Servers or the HTTP reverse proxy for IM or
conferencing.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-7
Lync Server 2013 does not support internationalized domain names (IDNs).
• SIP Transport Protocols: SIP can use at least three transport types and these are User Datagram
Protocol (UDP), TCP, and Transport Layer Security (TLS). In the default SIP transport configuration, SIP
is enabled to run over TLS.
Lync Server 2013 Features Available with Microsoft Office 2010 and Microsoft Office
2013
There are certain features of Lync Server 2013 that are available only with Microsoft Office 2010 and
Microsoft Office 2013. The following is the list of these features:
• New Contact Card with expanded options such as video call and desktop sharing
• Quick search from the Office Outlook Find a Contact box
• Reply with an IM or call from the Outlook Home ribbon in the Mail, Calendar, Contacts, and Tasks
folders
• Presence menu in Microsoft® Office SharePoint® Workspace 2010 (formerly Microsoft Office Groove
2007)
Lesson 2
Using the Lync Server 2013 Planning Tool
In this lesson, you will learn about the Planning tool, its capabilities, and benefits. In addition, you will
learn about exploring a sample design by using the Planning tool and exporting the configuration data.
Lesson Objectives
• Describe the capabilities and benefits of the Planning tool.
• Describe how to use the Planning tool to experiment with various scenarios based on the conceptual
design.
You can run the Planning tool multiple times, with different options and compare the different topologies.
You can also load the design in the tool and make changes to it. After you create the topology, you can
use the Export to Topology Builder option in the Planning tool, to export your topology to an Extensible
Markup Language (XML) file. You can provide this XML file as input to Topology Builder.
You can use the Planning tool only for exporting your initial topology design. After you export the
topology to Topology Builder and begin working with it, you can no longer use the Planning tool to
modify your topology. However, you can use the tool to test and validate assumptions about the impact
of changes that you make to your design, and to document your design.
Using the Planning tool is advantageous as it provides various options that can be used in a given
scenario. You need not prepare a plan before using the tool. The tool is an informative and useful way to
understand the types of questions that may come up during the envisioning phase and the planning
phase.
Question: When can you start working with the Planning Tool?
Inputs
Based on these inputs, you will receive a summary of hardware requirements. You can change the current
topology to provide different inputs. For example, in the sample topology, if you removed the need for
high availability and added redundant networks to the branch office sites, the output changes. Based on
the inputs, there is a difference in the two designs, in terms of the required hardware, implementation
time, and project complexity.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-11
Question: Do you see this as a tool you can use for your initial planning decisions?
MCT USE ONLY. STUDENT USE PROHIBITED
2-12 Designing a Lync Server 2013 Topology
Lesson 3
Using Topology Builder
Topology Builder and Central Management Database were significant enhancements in Lync Server 2010
and have been further improved in Lync Server 2013. In this lesson you will examine the Lync Server 2013
topology setup process. You can use the Topology Builder to save and publish a topology to the Central
Management Database.
Lesson Objectives
• Describe the Lync Server 2013 topology setup process.
3. Publish the topology. In a Lync Server 2013 Enterprise Edition, the published topology XML document
is stored in the back-end database that supports the first front-end server pool. In the Lync Server
2013 Standard Edition, the topology is stored in the SQL Express Edition database. Remote access is
not enabled by default. However, you can change this during the setup process.
4. Set up Lync Server 2013. After you publish the topology document to the database, you need to run
the local setup of the first Lync Server 2013 server again. After you complete this installation, the
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-13
setup routine provides a reference of a Service Connection Point (SCP) object from Active Directory.
This object points the setup to the Central Management Database. You should install the Lync Server
2013 component as defined in the topology document and perform the activation of services and
roles of the component accordingly.
5. Install the certificates. You can use the certificate wizard to generate the certificate request. After
running the wizard, you can install the received certificate response on the server specified for this
purpose and bind the certificate to specified Lync Server 2013 services and roles.
6. Modify the design. As you make some changes to your Lync Server 2013 environment, for example,
change the URL path for web services, or change a port that IIS uses, you need to reflect those
changes in the topology document by using Topology Builder. Then, you must publish the new
topology document. After this, you will be prompted to rerun the setup on the Lync Server 2013
servers to update the configuration changes.
Question: How can you prepare AD DS as part of the topology setup process?
3. Build the infrastructure visually by creating sites, pools, edge, and conferencing information.
4. Add information such as IP addresses and FQDNs of servers.
5. Validate the topology by using Topology Builder and verify if the topology is approved.
6. Publish the topology.
When you publish the topology, Lync Server 2013 places the topology in the Central Management
Database, which is created at this stage if it does not already exist. Then, when you install Lync Server on
each server in your deployment, the server reads the topology from the Central Management database
and installs a replica copy of the Central Management Database into a new local SQL Server Instance.
After configuring the first version of the topology, you can use the Topology Builder tool to publish the
configuration to the Central Management Server. The Central Management Server replicates this
configuration to all Central Management Databases in your environment. You can also use Topology
Builder to change the configuration of your topology in the later stages of the design and deployment.
MCT USE ONLY. STUDENT USE PROHIBITED
2-14 Designing a Lync Server 2013 Topology
If you are very familiar with Lync Server 2013 and need less prescriptive guidance, you can skip the
Planning tool and use the wizards in Topology Builder for the initial design of your deployment, and for
the validation and publishing steps. Although you can create and edit the topology XML manually, you
should avoid this because any error in manual editing might lead to failure of large portions of your
deployment. You might need to perform manual editing in rare situations. In such situations, follow the
recommendations in the Lync Server 2013 product documentation.
Whether you use the Planning tool or Topology Builder to define the topology, you are required to
publish the topology by using Topology Builder before you install Lync Server 2013 on servers.
If you import the topology design from the Planning tool, some of the information is pre-populated in
Topology Builder. Therefore, you need to specify only the configuration information that is not pre-
populated. If you import the topology design from the Planning tool and define a topology directly by
using Topology Builder, you must manually specify all required configuration information.
Using Topology Builder to plan and publish a topology is a mandatory step. You cannot bypass Topology
Builder and install Lync Server 2013 individually on the servers in your deployment. Each server must
retrieve and use the topology information from a validated, published topology XML file, in the Central
Management Database.
Question: Would you use the Planning tool or Topology Builder to build you topology?
What would be your reasons for doing so?
Schema Documents
You can classify schema documents into three types based on how they are exposed to the administrator:
• Deployment schemas. Describe how the deployment is configured, for example, the topology schema.
Most deployment schemas only support the global scope. Many of these schemas are not directly
exposed to the administrator, with the exception of the topology schema.
• Policy schemas. Contain information about the user permissions for setting up conferences and
Presence. After creating a policy document, you can assign it to one or more users. Policy schemas
use the tag scope.
• Settings schemas. Contain configuration information pertaining to specific roles within the
deployment. You can scope the setting schemas to an individual site or service.
Replica
Lync Server 2013 contains a replica, a SQL Server Express database, which runs on each Lync Server 2013
server role and contains a copy of the complete topology from the Central Management Database.
Therefore, when a server starts and finds that its configuration replica is current, it does not require
connecting with any root Forest Global Catalog or Domain Controller server to start its services. Moreover,
if the Central Management Database is offline, each Lync Server 2013 server role will use the data from its
local replica, and this will result in more resiliency. AD DS is used to store basic Lync Server 2013 user
information, such as the user’s SIP Uniform Resource Identifier (URI) and phone number.
To administer servers and services, you use Topology Builder, Lync Server 2013 Management Shell, or the
Lync Server Control Panel, which then retrieve the settings in the Central Management Store.
Configuration changes are replicated to all the servers in your deployment by the Central Management
Server, which runs on one of the servers in the front-end pool, if you are using Lync Server 2013 Enterprise
Edition server, or the front-end server, if you are using Lync Server 2013 Standard Edition server, in your
deployment.
Question: What is the difference between the Central Management Store, Central
Management Database, and the Central Management Server?
MCT USE ONLY. STUDENT USE PROHIBITED
2-16 Designing a Lync Server 2013 Topology
• Global. You can apply this policy globally to the entire environment.
• Site. You can apply this policy to a specific site.
• Tag. This policy uses an arbitrary string to specify its uniqueness. Usually, the string is not truly
arbitrary, but it has different meanings depending on the document.
Branch sites with less-resilient links should use the Survival Branch Appliance that provides resiliency in
times of wide area network (WAN) failures. A Survival Branch Appliance combines a public switched
telephone network (PSTN) gateway with some Lync Server 2013 functionality. For example, in a site where
you have deployed Survival Branch Appliance, users can still send and receive Enterprise Voice calls, even
if the WAN connecting the branch site to the central site is unavailable.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-17
Branch sites with resilient WAN can connect to the central site by using a PSTN gateway, and optionally,
use a Mediation Server.
Question: How do central and branch office sites and site topology design correlate with
Active Directory sites?
Lesson 4
Planning the Server Infrastructure
To plan the server infrastructure, you should consider user requirements. First, select Standard Edition or
Enterprise Edition–based licensing, and then select the type of pool that is required for the deployment.
Before you select the server, consider capacity and scaling requirements based on the number of users in
the organization. You should also consider the different server pools and collocation scenarios, in addition
to capacity and scaling.
Lesson Objectives
• Determine the appropriate server editions.
Question: Which types of servers require licensing other than Lync Server Standard Edition
and Lync Server 2013 Enterprise Edition pools?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 2-19
Types of Pools
Lync Server 2013 comprises several types of server
pools. These server pools are Enterprise Edition
front-end server pool, Conferencing server pool,
Mediation server pool, and Director server pool.
Director Pool
Directors can be single-instance servers or can be installed as a load-balanced pool of multiple Directors
for higher availability and capacity. Both hardware load balancing (HLB) and DNS load balancing are
supported. A Director or Director pool facilitates user authentication and redirection of Lync Server user
requests to the user’s home pool. The home pool is either a front-end pool or a Standard Edition server.
We recommend that you deploy a Director pool in each central site that supports external user access. A
Director pool is deployed in each central site with one or more front-end pools. Each Director pool can
contain a maximum of 10 Directors. A Director cannot be collocated with any other server role.
Question: Which server pool is required as a mandate in a Lync Server 2013 Enterprise
Edition deployment?
MCT USE ONLY. STUDENT USE PROHIBITED
2-20 Designing a Lync Server 2013 Topology
Virtualization
You can run a virtualized topology of Lync Server 2013 in both small and enterprise topologies.
Collocation
Collocation in a Unified Communications project helps reduce cost and time. Therefore, when you design
a topology, you should start with collocation until technical reasons or capacity reasons require you to
split roles to multiple servers.
Question: What are the deployment options for an organization with 6,000 users?
MCT USE ONLY. STUDENT USE PROHIBITED
2-22 Designing a Lync Server 2013 Topology
Lesson 5
Designing Documentation by Using Microsoft Office
A good design document should be well-structured and have all the information that a person might
need to understand the deployment of Lync Server 2013. You should also know the benefits of having a
good design document and the various options available for documenting the design.
Lesson Objectives
• Describe the benefits of good design documentation.
Maintain the design document so that the conceptual and logical levels are described early in the project.
This enables each person or working group to maintain a lower-level physical design for each of their
responsibility areas.
• Edge Design
• Certificates design
You may use one or more Microsoft Office Excel spreadsheets for detailed documentation.
• IP address documentation
• VLAN documentation
The Planning tool for Lync Server 2013 helps you create the initial Office Visio diagrams. You can later
expand them as required by the organization.
Question: What does good server infrastructure design documentation provide you?
MCT USE ONLY. STUDENT USE PROHIBITED
2-24 Designing a Lync Server 2013 Topology
Note On all virtual machines, verify that all of the services set to start automatically have started. Most
notably, check the Exchange, SQL Server, and Lync Server 2013 services. If any are not started, right-click
each and then click Start.
The main tasks for this exercise are as follows:
Results: After completing this exercise, you should have prepared Active Directory for an installation of
Lync Server 2013.
• Front End pool FQDN :lon-pool.ADatum.com. and it should be Enterprise Edition Front End Pool
• Computer FQDN : lon-fe01.adatum.com
• In Features Conferencing (includes audio, video and application sharing), Dial in (PSTN)
conferencing, Enterprise Voice and Call Admission Control
• Mediation server should be collocated
• Nothing is associated with this front end pool
• SQL Server FQDN : Lon-SQL01.ADatum.com
• Named Instance : LYNC.
• No SQL mirroring
• File Server FQDN : Lon-SQL01.adatum.com
• File Share : LyncShare,
• Make sure Override Internal Web Services Pool FQDN is selected : use lon-poolweb-
int.adatum.com
• External Base URL : lon-poolweb-ext.adatum.com
• No Office Web Apps Server
• Once the topology is created add a new Central site with these options
• Name : Redmond (Site 1), City Redmond, Country/Region Code +1
• Front End pool FQDN : red-pool.ADatum.com, it should be Enterprise Edition Front End Pool
• Computer FQDN : red-fe01.adatum.com.
• Features include : Conferencing(includes audio, video and application sharing), Dial in (PSTN)
conferencing, Enterprise Voice and Call Admission Control
• Mediation server should be collocated
• Nothing is associated with this front end pool
• SQL Server FQDN : Red-SQL01.ADatum.com
• Named Instance : LYNC.
• No SQL mirroring
• File Server FQDN : RED-SQL02.adatum.com
• File Share : LyncShare,
• Make sure Override Internal Web Services Pool FQDN is selected : use red-poolweb-
int.adatum.com
• External Base URL : red-poolweb-ext.adatum.com
• No Office Web Apps Server
• Administrative URL: https://lyncadmin.adatum.com.
• Central Management Server should be on lon-pool.adatum.com London (Site 0)
(To configure DNS and certificates for your deployment please follow the steps mentioned in the tasks)
Results: After completing this exercise, you should have created and edited a publishable topology.
MCT USE ONLY. STUDENT USE PROHIBITED
2-26 Designing a Lync Server 2013 Topology
Results: After completing this exercise, you should have a published topology.
Task 1: Create the necessary DNS Records for Lync Server 2013.
Create the necessary DNS Records for Lync Server 2013.
Note The steps for Lon-FE01 and Red-FE01 can be completed in parallel.
2. Set up components.
6. Set up components.
Results: After completing this exercise, you should have a configured Lync Server 2013 deployment.
Task 3: Enable users for Lync Enterprise Voice and Exchange UM.
Enable users for Lync Enterprise Voice and Exchange UM
MCT USE ONLY. STUDENT USE PROHIBITED
2-28 Designing a Lync Server 2013 Topology
Ensure that you identify and involve the other stakeholders required for a successful Lync Server
implementation as early as possible and get approval on the deployment plans before starting
any work. This helps minimize deployment delays and roadblocks in implementing changes to
firewalls or other network configurations, acquiring certificates, preparing Active Directory
Domain Services, and configuring DNS, PBXs, or gateways. The likelihood that these items are
owned or managed by one entity decrease with the size of the organization. Not involving the
appropriate departments early during the planning phase to cause roadblocks and delays in the
subsequent deployment. Remember to schedule the appropriate time for change management
approvals and scheduling, in a large organization.
Review Question(s)
Question: For a Greenfield Deployment of Lync Server 2013 or migration from Office
Communications Server 2007 R2, which two actions must be completed before you can
publish a topology by using Topology Builder?
Question: After publishing the topology, but before clicking the Finish button in the
publishing wizard, what should you do?
Answer: They should deploy Enterprise Edition first to host the Central Management Store. If they plan to
start a pilot with Standard Edition, they would need to first prepare the Standard Edition server to host the
CMS, and then later move the CMS.
MCT USE ONLY. STUDENT USE PROHIBITED
3-1
Module3
Configuring Users and Rights in Microsoft Lync Server 2013
Contents:
Module Overview 3-1
Module Overview
To configure and manage users in Microsoft® Lync® Server 2013, you can use a variety of methods.
Lync Server 2013 provides configuration management options, including Lync Server Control Panel and
Lync Server Management Shell. You can use basic syntax for working in Windows PowerShell® because it
has powerful scripting capabilities. You can also use the administrative model of the new role-based
access control (RBAC) in Lync Server 2013. The administrative model provides predefined roles, which you
can assign to administrators, and you can create new custom roles.
Objectives
• Use Lync Server 2013 management interfaces.
• Configure role-based access control.
MCT USE ONLY. STUDENT USE PROHIBITED
3-2 Configuring Users and Rights in Microsoft Lync Server 2013
Lesson 1
Managing Lync Server 2013
You can use the Lync Server Control Panel, PowerShell 3.0, and Lync Server Management Shell to manage
your Lync Server 2013 communications system. These tools, along with PowerShell cmdlets enable you to
manage users in your organization.
Lesson Objectives
• Manage users with Lync Server Control Panel.
• Assign policies to users. You can assign specific policies to a user or a group of users, such as
conferencing policies, supported client version policies, archiving policies, or remote user access
policies.
• Assign users to a server or pool. You can assign users to a server or move them to a specific pool
under the Edit or move users link in the Lync Server Control Panel.
• Set a user’s dial-in conferencing PIN. You can configure global PIN policies, such as the required
minimum length. In addition, you can configure PIN policies for individual users or sites. You can
choose to generate the PIN automatically, or create one manually.
Lync Server Control Panel is automatically installed on every front-end server or Standard Edition server in
your deployment. In Lync Server 2013, Edge Servers are managed remotely by using the Lync Server
Control Panel, which is not exposed externally to the web.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 3-3
Note: You cannot use Lync Server Control Panel to manage users who are members of the Active
Directory Domain Admins group. For Domain Admin users, you can use Lync Server Control Panel to
perform read-only search operations. To perform write operations on Domain Admin users, such as
enabling or disabling Lync Server 2013, or changing pool or policy assignments, telephony settings, SIP
address, and so on, you must use Windows PowerShell cmdlets while logged on as a Domain
Administrator with appropriate RBAC credentials.
For more information about PowerShell cmdlets, see “Using PowerShell 3.0” in this module.
New-CsUserReplicatorConfiguration
Typing “new” conveys to PowerShell what you want to do. The dash-noun combination signifies a
parameter. In this example, PowerShell creates a new collection of user replicator configuration settings.
The user replicator periodically retrieves up-to-date user account information from Active Directory and
then synchronizes the new information with the current user data stored by Lync Server 2013.
PowerShell Verbs
For more information about PowerShell cmdlets, see “Using PowerShell 3.0” in this module.
MCT USE ONLY. STUDENT USE PROHIBITED
3-4 Configuring Users and Rights in Microsoft Lync Server 2013
Get-Help
Get-Help New-CsVoicePolicy
This command returns the most commonly-sought help for creating a new voice policy.
For more detailed help on a topic, you can add a parameter, preceded by a dash, as shown in the
following example.
Note: You can get help on each cmdlet directly from the command line and from the
Lync Server 2013 Help file. There are two specific Help files available for cmdlets—RTCCmdlets.chm and
RGSCmdlets.chm.
For example, if you want to find all the services running on a particular server, type the following
command.
Get-Service
If you want to return only the Lync Server 2013 services and their active status, type the following
command.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 3-5
Get-CsWindowsService
In the following example, the DisplayName parameter is followed with the value, “Windows Update”, to
convey to the Get-Service cmdlet that is should get only those services with a DisplayName property
equal to Windows Update.
Note: In this example, the double quotation marks before and after Windows Update are
required because the string contains a space. Otherwise, double quotation marks are unnecessary when
assigning a one-word value to a parameter.
Using Wildcards
To further refine your results, you can use wildcards. The primary wildcard characters in PowerShell are the
asterisk (*), which represents one or more characters, and the question mark (?), which represents a single
character.
For example, if you want to display all services that have a display name beginning with “windows,” but
want to exclude any services that contain the word “audio” in the Name or DisplayName, type the
following command.
PowerShell Scripting
In addition to running cmdlets, you can use PowerShell 2.0 to run scripts that automate your more
commonly performed tasks. A script in PowerShell is simply a text file that contains your typed
commands. The lab for this module guides you through the process of running a PowerShell script.
MCT USE ONLY. STUDENT USE PROHIBITED
3-6 Configuring Users and Rights in Microsoft Lync Server 2013
Lesson 2
Introduction to Role-Based Access Control
You can use Lync to delegate specific tasks and permissions to certain administrative staff. This delegation
is done through role-based access control or RBAC.
Lesson Objectives
• Describe role-based access control (RBAC).
Note: RBAC restrictions work only on administrators working remotely, using either the Lync
Server Control Panel or Lync Server Management Shell. A user sitting at a server running Lync Server is
not restricted by RBAC. Therefore, physical security of your Lync Server is important to preserve RBAC
restrictions.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 3-7
• The user script path, which is, by default, C:\Program Files\Common Files\Microsoft Lync Server
2013\AdminScripts
To create a new role, you use the New-CsAdminRole cmdlet. Before running New-CsAdminRole, you must
create the underlying security group that will be associated with this role.
The following cmdlets serve as an example of a creating a new role. They create a new role type called,
MyHelpDeskScriptRole. The new role has the abilities of the predefined CsHelpDesk role, and can
additionally run the functions in a script named, “testscript”.
For this cmdlet to work, you must first create the security group, MyHelpDeskScriptRole.
After this cmdlet runs, you can assign users directly to this role (in which case they have global scope), or
create a scoped role, based on this role.
RBAC Scope
The three limitations that make up the CSAdminRole:
• User scope will enable you to define the set of users that can be modified, based upon OU
membership. These permissions are transitive, so sub-users in sub-OUs can be modified.
MCT USE ONLY. STUDENT USE PROHIBITED
3-8 Configuring Users and Rights in Microsoft Lync Server 2013
• Config scope enables you to define a Lync site for which an admin can manage servers and policies.
Lab Setup
Estimated Time: 45 minutes
Note Ensure that -02 virtual machines from the previous lab are shut down.
Ensure that students close the virtual machines that end in -02, prior to starting this lab.
Results: After completing this exercise, all virtual machines should start properly.
Results: After completing this exercise, you should have provisioned users based on an Active Directory
attribute, in this case, group membership, by using the Lync Server Management Shell.
Results: After completing this exercise, you should be able to use RBAC and know how basic Active
Directory group membership modifies rights within Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 3-11
When planning for role-based access control (RBAC), remember that to follow least privilege practices,
you should not assign users to roles with global scope if they are going to administer only a limited set
of servers or users. All predefined roles shipped in Lync Server have a global scope. To accomplish this,
create roles that are based on an existing role, but with a more limited scope.
Review Question(s)
Question: If someone deletes or disables a Lync user account, is it possible to audit who did
it?
Question: Is a user working directly on a server running Lync Server 2013 restricted by
RBAC?
MCT USE ONLY. STUDENT USE PROHIBITED
3-12 Configuring Users and Rights in Microsoft Lync Server 2013
MCT USE ONLY. STUDENT USE PROHIBITED
4-1
Module4
Client and Device Deployment and Management
Contents:
Module Overview 4-1
Module Overview
Microsoft® Lync® Server 2013 introduces new ways to create and define client and user policies, and
new procedures to deploy clients and devices. You should know how to plan for introducing Lync Server
2013 clients into your network and the various phone devices that are supported. You should also know
how to effectively manage the desktop clients and devices.
Objectives
• Prepare for client deployment.
• Deploy and manage clients.
Lesson 1
Preparing for Client Deployment
There are a number of clients that are available for use with Lync Server 2013 and you can use various
options available for deploying them, including in-band provisioning and
Active Directory® Domain Services (AD DS) Group Policy. You can also configure client policies and
settings, and assign these policies to users.
Lesson Objectives
• Configure client policies and settings.
In-Band Provisioning
Just as in Lync Server 2010, in Lync Server 2013,
most client policies are now controlled through
server-based in-band provisioning. Although it is
still possible to configure and manage client policies by using Group Policy, administrators can also use in-
band provisioning settings to manage policies by using the Lync Server Control Panel, the
Microsoft Windows PowerShell® command-line interface, or both. Administrators can now perform most
client configuration tasks themselves, and apply policies with more precision by assigning them at the
global, site, or tag level. (Tags are settings that can be applied to a single user or to a group of users.)
Group Policies
There are still some essential policies and settings that you can only configure by using Group Policy.
These include client configuration policies that specify, for example, the default servers and security mode
that the client should use until sign-in is complete. Because these policies take effect before the client
signs in and begins receiving in-band provisioning settings from the server, they must exist in the client
computer’s registry before initial sign-in.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-3
Lync Server
Control Panel Description Lync Server2013 cmdlets
group
New-CsImFilterConfiguration -
Identity site:Redmond -Prefixes
@{add="rtsp:", "urn:"}
Lync Server
Control Panel Description Lync Server2013 cmdlets
group
Configure a dial-in access number. site:Redmond –Description “Redmond
Configure a dial-in PIN policy. Default Conferencing Policy” –
AllowIPAudio $true –AllowIPVideo
$false –EnableDesktopSharing
Desktop
Set-CsConferencingConfiguration –
Identity Global –Organization
“Fabrikam Corporation”
New-CsClientVersionPolicy –Identity
site:Miami
$x = [guid]::NewGuid()
New-CsClientVersionPolicyRule -
Parent "site:Miami" -RuleId $x -
MajorVersion 4 -UserAgentInHouse
Set-CsUCPhoneConfiguration -
Identity site:Miami -
PhoneLockTimeout "00:30:00"
Lesson 2
Deploying and Managing Lync 2013 Clients
Lync Server 2013 communications software supports several types of client software that you can deploy
to your organization’s users, including computer-installed client software and web-based clients. You
should be familiar with the essential deployment and configuration options that you can use when
deploying the Lync Server 2013 clients.
Lesson Objectives
• Deploy Lync 2013.
Managed Deployment
If you choose to manage the deployment, you have the following installation options:
• Microsoft System Center Configuration Manager. Use this product for more complex software-
installation scenarios, where scheduling, inventory, reporting, status, and support for an installation
across a wide area network (WAN) are required.
• Active Directory Group Policy. You can create a Group Policy object to deploy Lync Server 2013 to
specific users or computers, based on group memberships.
• Windows logon scripts. The logon script performs an unattended installation of Lync 2013 when a user
logs on. GPOs can be used to target logon scripts to specific devices or users.
MCT USE ONLY. STUDENT USE PROHIBITED
4-6 Client and Device Deployment and Management
You must designate a single server or pool to distribute and authenticate client sign-in requests. For high
availability, we recommend that you configure a Director pool for this function.
You must also create a single, internal DNS Service Location (SRV) record that maps to the fully qualified
domain name (FQDN) of the Director pool (or front-end pool/Standard Edition server) that distributes
sign-in requests from clients:
• For complete auto discovery, create the lyncdiscover URL; Lyncdiscover.<domain>
Note: The SIP domain refers to the host portion of the SIP Uniform Resource Identifiers (URIs)
assigned to users. For example, if SIP URIs are of the form, john@contoso.com, contoso.com is the SIP
domain. The SIP domain may be different from the internal Active Directory Domain Services domain.
You use Lync Server Control Panel to edit the default client version policy. In addition to creating a global
policy, you can create client version policies for a particular service or site, or user-scoped policies that can
be assigned to individual users.
Note: Because anonymous users are not associated with a user, site, or service, anonymous users
are affected by global-level policies only.
to join online meetings by using an alternate client. By default, the meeting join page includes the option
to use the Lync Web App.
You configure the meeting join page in the Lync Server Control Panel or the Lync Server Management
Shell by using the following cmdlets.
New-CsWebServiceConfiguration
Set-CsWebServiceConfiguration
• Configuring available meeting options and meeting-option defaults by using Lync Server 2013 in-
band provisioning.
In addition, users can change the language of the meeting invitation to English when non-English versions
of the Microsoft Office Outlook® messaging and collaboration client and Lync 2013 are installed.
Note: Lync 2013 privacy settings do not apply to client versions before Lync 2010.
• Manage multiple conversations with rapid call handling, IM, and on-screen routing capabilities.
From an administrative perspective, you can deploy Lync 2010 Attendant within your organization by
using any method that supports a Microsoft Windows Installer package (.msi file). Additionally, you can
control key features and settings by using installation scripts or AD DS Group Policies.
The Lync 2010 Attendant is the only Attendant client that is released for Lync Server 2013. There will not
be a special Lync 2013 version of this attendant.
MCT USE ONLY. STUDENT USE PROHIBITED
4-8 Client and Device Deployment and Management
Windows Yes Yes N/A N/A N/A N/A Yes N/A Yes
8 (Intel-
based)
Mac OS- N/A N/A N/A N/A N/A N/A Yes Yes Yes
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-9
When the Lync 2013 client detects that it is being run in a VDI environment, the audio and video will be
redirected to the local plug-in running on the VDI client. The client running on the host will provide a
blue background on which the VDI plug-in will then project the video. This provides for a local
termination point for audio and video, and ensures the best quality for the user.
The following points are known issues or limitations when running in a VDI environment;
• There is limited support for Call Delegation and Response Group Agent Annonymization features.
• There is no support for the following features:
o Recording of conversations
o Joining meetings anonymously (that is, joining Lync meetings hosted by an organization that
does not federate with your organization)
MCT USE ONLY. STUDENT USE PROHIBITED
4-10 Client and Device Deployment and Management
o Using the Lync VDI plug-in, along with a Lync Phone Edition device
Lesson 3
Preparing for Device Deployment
In Lync Server 2013, a device may refer to any Unified Communication (UC) device, including headsets
and webcams. However, we will discuss the IP phone here, because it is a managed device. Phones
running Microsoft Lync 2013 Phone Edition enable users to interact with the Lync Server 2013
communication and collaboration features. A new addition in Lync Server 2013 is the support for 3PIP
devices. These are Lync compatible devices that can be developed by any third-party for direct
registration on Lync Server 2013.
You should be familiar with the planning requirements for deploying Lync Server 2013 IP phones and the
configuration steps that you must perform to enable their use.
Lesson Objectives
• Describe the supported IP phones.
Supported IP Phones
Desk Phones
Lync Server 2013 provides options for both IP desk phones and USB phones. IP phones provide a broader
set of UC features and do not need to be connected to a computer that is running Lync 2013 to provide
communication and collaboration features. USB phones require this connection because they are simply
an extension of a local Lync 2013 client. IP phones will not allow users to log on unless the users are
configured for Enterprise Voice. USB phones allow all users to log on, regardless of their configuration.
USB phones work for Lync 2013 calls by using the Internet, without requiring Enterprise Voice or a
connection to the public switched telephone network (PSTN).
• Aastra 6725ip
• Polycom CX500
• Polycom CX600
MCT USE ONLY. STUDENT USE PROHIBITED
4-12 Client and Device Deployment and Management
• HP 4120
• Polycom CX700
• LG/Nortel 8540
Lync Server 2013 also introduces support for the following USB desk phones:
• Polycom CX100
• Polycom CX200
• Polycom CX300
• Aastra 6721ip
• Polycom CX500
• HP 4110
Because all of the common area phones are IP phones, they do not need to be connected to a computer
to provide Lync Server 2013 UC functionality.
Conferencing Devices
Conference room devices transmit high-quality audio, and those with video capabilities track the person
who is currently speaking. The supported conferencing devices are:
Third-Party IP Phones
With the release of Lync Server 2013, we are now
focusing on third-party IP phones, better known as
3PIP phones. These phones were previously known
as Lync compatible phones.
These phones will need to support the same
phones as the Lync-optimized IP phones, but
because they are running firmware developed
directly by the phone manufacturer, these phone
will get more and faster firmware updates. Also,
new features, which were previously unsupported,
such as 802.1x, will be supported.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-13
• Associate phones with contact objects. Associate all common area phones with an AD DS contact
object.
• Enable a PIN policy. Enable PIN authentication on Lync Server 2013 and ensure that an appropriate
PIN policy is in place.
Best Practices
For optimal audio quality, you need to:
• Separate Voice over Internet Protocol (VoIP) traffic from other network traffic by configuring
Differentiated Services Code Point (DSCP) tagging or any other form of Quality of Service (QoS) and
putting voice traffic in the correct queues.
• Advise users to attach their laptop or computer to a wired network, instead of a wireless network. IP
phones are required to do this.
• Enable correct exceptions for separating Lync traffic from other traffic when connecting over a virtual
private network (VPN) or direct access. Lync traffic should always pass directly through the Edge
Server when accessing from the outside.
For more information about configuring Enterprise Voice, see “Configuring Basic Enterprise Voice” and,
“Extending Enterprise Voice Functionality” from this handbook.
DNS
In addition to the DNS records required for auto-
configuration, the following table describes the
records that you must create and publish to a DNS
service within the corporate network, if you are
MCT USE ONLY. STUDENT USE PROHIBITED
4-14 Client and Device Deployment and Management
deploying IP phones.
A FQDNs for the pool(s) that The new Lync Server 2013 DNS load balancing feature
host the Enhanced requires you to specify the server FQDN and the pool
Registrars FQDN, using the same IP address for each server in the
pool, and you should create A records for all pools that
contain an Enhanced Registrar.
If you use hardware load balancing, just specify A
records for each pool that contains an Enhanced
Registrar. This allows external devices to connect by
using SIP over TLS to the Enhanced Registrar internally.
SRV _sipinternal._tcp.<SIP You specify the two SIP FQDNs for internal routing, one
domain> for communications over TCP, and the other for TCP
communications secured by TLS.
Note: If the pool is already deployed, this information can be referenced from the Lync Server
Control Panel Topology tab by selecting the Edge server properties.
DHCP
DHCP provides an automated way to distribute and update IP addresses and other configuration
information on a network. For connectivity, IP phones require the web services URL and Enhanced
Registrar FQDN from the DHCP server. You can configure this in your corporate DHCP server, or you can
use the DHCP server provided with the Lync Registrar. The Lync Server 2013 DHCP server does not lease
addresses, and can be used safely in conjunction with any other DCHP server.
You can enable the Lync Server 2013 DHCP server by using the following Lync Server Management Shell
command.
You must ensure that broadcast packets from devices can reach the DHCP server(s) by configuring DHCP
relay agents to forward DHCP packets to the Lync Server 2013 DHCP servers.
To enable IP Phones to discover and connect to Lync Server 2013, you must ensure that the following
options are set on the organization’s DHCP servers. You can use the DHCPUtil.exe utility to configure
these options.
120 FQDN for Specify the FQDN of the pool that will be the first
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-15
Lesson 4
Deploying and Managing IP Phones
To deploy and manage IP phones, you can perform the steps in the recommended process. We
recommend that you deploy only qualified UC devices that display the “Optimized for Microsoft Lync”
mark.
Lesson Objectives
• Provision users.
Provisioning Users
Before you connect an IP phone to Lync Server
2013, you must configure an authentication PIN
on the device for the user.
Set -CSClientPIN
1. Create a new contact object for each common area phone. If an AD DS object already exists,
ensure that this object is not SIP-enabled.
If the object is SIP-enabled, you must remove the Lync Server 2010 attributes by running the following
cmdlet.
Disable-csUser
You can then configure the phone by running the following cmdlet.
New-csCommonAreaPhone
2. Create required policies for common area phones. Creating specific policies for common area
phones is optional. However, you might want to create policies for lobby phones that have more
restrictive policies than meeting-room phones. The types of policies that you can create include client,
voice, conferencing, and PIN policies.
Enhancements
• Usage information is captured in the call detail record (CDR) database.
New Features
• Certification authority (CA) discovery is configured in DHCP.
Lync Server Control Useful when setting up dial plans, Lync Server Control Panel
Panel voice policies, calls routes, device
logs, and PINs, and starting web
services and managing Device
Updates.
Power-on self-test Useful when monitoring and On the device. (While the
(POST) troubleshooting issues on the device is starting up, press
phone. You can use this tool to test * + 7 to start POST. If the
the health of the DDR2 RAM. test fails, the preboot code
returns an error message
and the startup process
ends.)
Reset (Hard, Factory) Useful when troubleshooting issues On the device. (When the
on the new IP phones. Hard Reset device starts, press both *#
enables users to delete all user- (Hard) or 46 (Factory) to
created data (such as device logs, reset the device.)
registry settings, and credentials).
The Factory Reset enables users to
revert the device to the last
working software version, in the
event that the phone is updated to
a version that is causing issues.
In Lync Server 2013 Standard Edition, the file store is automatically created by the installer in the Web
Services folder, under the installation folder. The default path is: %Program Files%\Microsoft Lync
Server\Web Services\Device Update Files.
In Lync Server 2013 Enterprise Edition, prior to installation, you must create a shared folder to contain
both client and device update files. You must then specify the location of this folder when you run the
Create Front End Pool Wizard during deployment.
Note: We recommend that you create a quota on the Device Update log file store by using the
File Server Resource Manager. A quota helps ensure that the number of log files does not exceed the
MCT USE ONLY. STUDENT USE PROHIBITED
4-20 Client and Device Deployment and Management
available storage; otherwise, you may encounter problems for the web services role. We recommend
that you set a file store quota, whether or not you use the Device Update service.
For more information about setting up a quota by using the File Server Resource manager,
see “File Server Resource Manager Step-by-Step Guide for Windows Server 2008” at
http://go.microsoft.com/fwlink/?LinkId=201142
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-21
You will create and assign client and device policies at the global, site, and user levels by using the
available Lync Server tools to enforce the defined company policies with granular control.
Results: After completing this exercise, you will have started all the virtual machines to complete the
remaining exercises.
• Site with the following parameters: for site Redmond (Site 1)” with Description "Redmond Default
Client Policy", enabling music on hold, allowing full screen video, enable exchange contact sync and
with an IM warning "Warning: All communications within ADatum may be logged and viewed at any
time and for any reason. Use of the ADatum Instant Messaging Service is a privilege. Abuse of the
system may result in loss of said privilege. This is a Redmond Local Message"
• Marketing with following parameters: Description "ADatum Executive Client Policy" allows appearing
offline, enabling music on holds, allowing full screen video, allowing media redirection, and enabling
exchange contact sync.
Important: On all virtual machines, verify whether all of the services set to start automatically have
started. Most notably, check the Microsoft Exchange, Microsoft SQL Server®, and Lync Server 2013
services. To do so, click Start, click Administrative Tools, and then click Services. In the Services console,
verify that all services set to Automatic start have started. If not, right-click the service, and then click
Start.
MCT USE ONLY. STUDENT USE PROHIBITED
4-22 Client and Device Deployment and Management
Results: After completing this exercise, you should be able to describe how to create client policies in
Lync 2013, how to apply them, and then see the effects of the client policies.
Results: After completing this exercise, you should have created device policies and edited the global
policies by using a PowerShell script. This script should also configure a new common area phone.
Results: After completing this exercise, you should have installed a new device update file, uploaded it
into Lync Server, tested it on a specific device, and then approved it for all devices.
Results: After completing this exercise, you should have created a mobile device policy.
MCT USE ONLY. STUDENT USE PROHIBITED
4-24 Client and Device Deployment and Management
Review Question(s)
Question: Does the Lync 2013 setup program uninstall previous versions of Lync or Office
Communicator?
Question: What do you use to deploy Lync 2013 Group Policy settings?
1. Lync Server 2010 supports the new Lync 2013 clients. This enables organizations that are migrating
from Lync Server 2010 to roll out new clients independent of Lync Server upgrades. For more
information, see the Server and Client Compatibility section at:
http://go.microsoft.com/fwlink/?LinkId=282047
2. When planning for clients to use automatic discovery to find their registration point for a given SIP
URI, you can run into issues in environments that do not use split-brain DNS, nor want to establish
split-brain DNS. Split-brain DNS is where one set of internally managed DNS servers provide
resolution for DNS queries for internal resources, and a set of externally managed DNS servers
provide resolution for DNS queries to external resources published for access from the Internet. In
split-brain DNS environments, the solution for publishing DNS records required for Lync clients is
straightforward. Additionally, putting internal records in an external DNS could reveal internal
addressing to the outside world.
What do you do? The answer is to create "pinpoint" DNS zones. This type of DNS zone is a single record
represented by the zone itself. For example, if you need to have _sipinternaltls._tcp.contoso.com as an
SRV record pointing to pool.contoso.com for internal client resolution, you would create a pinpoint DNS
zone record for zones, "_sipinternaltls._tcp.contoso.com" and "pool.contoso.com", by using, for example,
the DNSCMD command-line tool.
Following is an example.
3. If both Lync 2013 for the desktop and Lync Windows Store app are installed on the computer, you
have to set one of them as the default client to use for meetings. The first time you click the Join Lync
Meeting link in an Outlook calendar reminder to connect to a meeting, the Default Meeting Client
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 4-25
dialog box appears. Select either Microsoft Lync or Lync (which means Lync Windows Store app), and
then click OK. The next time you join a Lync Meeting from an Outlook calendar reminder, the
meeting client you selected will be used automatically. You can change this behavior in the Default
Programs settings.
MCT USE ONLY. STUDENT USE PROHIBITED
4-26 Client and Device Deployment and Management
MCT USE ONLY. STUDENT USE PROHIBITED
5-1
Module5
Conferencing in Lync Server 2013
Contents:
Module Overview 5-1
Module Overview
Conferencing is a core feature of Microsoft® Lync® Server 2013. You can use conferencing feature in Lync
Server 2013 for dial-in conferencing and for managing and administering conferencing policies.
Objectives
• Describe conferencing in Lync Server 2013.
Lesson 1
Introduction to Conferencing in Lync Server 2013
Conferencing in Lync Server 2013 includes the conferencing modes, new conferencing features, and
conferencing architecture and infrastructure components. You should be familiar with all these
components. You should also be familiar with call flows among conferencing components, and be able to
describe the considerations for Lync Server 2013 deployment and migration.
Lesson Objectives
• Describe the conferencing modes in Lync Server 2013.
A/V Conferencing
A/V conferencing enables users to have real-time
audio and video conferences without the need for
external services, such as the Microsoft Live
Meeting service or a third-party audio bridge. A/V
conferencing requires appropriate client devices, such as headsets for audio conferences and webcams for
video conferences. .
With a single click, users can schedule a meeting from Outlook. Details, such as meeting time, location,
and attendees, are based on the familiar Outlook template. Additionally, conference call-specific
information, such as dial-in number, meeting IDs, and personal identification number (PIN) reminders, are
automatically populated.
To help ensure that only the authorized people participate in a call, Lync Server provides multiple levels of
authentication for participants. Users who join by using Lync are already authenticated by Active Directory
Domain Services and do not need to enter a PIN, pass code, or meeting ID.
Lync simplifies the video conferencing user experience by incorporating video into the unified client so
that scheduling a meeting with video or escalating to video spontaneously is seamless.
Lync Server makes it easy to add video to a standard phone call in just one click. When there are multiple
participants in a video call or a conference, each user can see video from up to five other users
simultaneously, or a presenter can choose just one video source to be seen exclusively by everyone.
High-definition video (resolution 1270 x 720; aspect ratio 16:9) and VGA video (resolution 640 x 480;
aspect ratio 4:3) are supported for peer-to-peer calls between users running Lync on high-end computers.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-3
The resolution viewed by each participant in a single conversation may differ, depending on the video
capabilities of each user’s hardware.
Web Conferencing
Web conferencing is integrated with the overall enterprise messaging infrastructure of Lync Server 2013.
When combined with A/V conferencing, web conferencing delivers real-time collaboration that is simple
to manage. With web conferencing, users can share and collaborate on documents, such as Microsoft
PowerPoint presentations, during their online conferences. Additionally, users can share all or part of their
desktop with each other in real time.
Dial-in Conferencing
Dial-in conferencing enables users to join the audio portion of a Lync Server 2013 conference by using a
public switched telephone network (PSTN) phone without requiring a third-party audio conferencing
provider.
Client Features
Lync Server 2013 includes the following new client
features:
• Scheduling Infrastructure Changes.
Administrators can customize email invitations
for online meetings by using Lync Server
Control Panel or Lync Server Management
Shell. Customizations can include URLs for
logos, help text, legal text, and footer text. All
subsequent invitations will include the customizations.
• Join Launcher. Lync Server 2013 updates the Join launcher to validate each meeting before launching
a client, and to provide support for opening a meeting in the following clients:
o Windows Phone 7
o Android devices
o Windows 8
o Internet Explorer 10
• Video Enhancements.
o Gallery View and HD Video Conferencing. In video conferences, users can see videos of up to five
conference participants at the same time.
o HD Video. Users can experience resolutions up to HD 1080p in two-party calls and multiparty
conferences.
o Presenter Only Video Mode. Presenters can configure the conference so that only the video from
the presenter is shown. This mode prevents distractions in large conferences when multiple video
streams are available and locking to different sources. This mode also applies to video captured
and provided by conferencing devices.
MCT USE ONLY. STUDENT USE PROHIBITED
5-4 Conferencing in Lync Server 2013
o Video Spotlight. Presenters can configure the conference so that only the video from a selected
participant, who is a video source, is seen by everyone in the conference. This mode also applies
to video captured and provided by conferencing devices for panoramic video.
• VDI Plug-in: The Lync 2013 client now supports audio and video in a virtual desktop infrastructure
(VDI) environment. A user can connect an audio or video device (for example, a headset or a camera)
to the local computer (for example, a thin client or repurposed computer). The user can connect to
the virtual machine, sign in to the Lync 2013 client that is running on the virtual machine, and
participate in real-time audio and video communication as though the client is running locally.
The Online Meeting Add-in for Lync 2013 includes meeting invite customization and new
meeting options:
o Administrators can customize the organization’s meeting invitations by adding a
custom logo, a support URL, a legal disclaimer URL, or custom footer text.
o New attendee mute controls allow meeting organizers to schedule conferences that
have attendee audio and video muted by default.
• Dial-out Conferencing for non-Enterprise Voice users. Lync Server 2013 now allows participants who
are not Enterprise Voice-enabled to initiate dial-out calls from a meeting conference. The
administrator can configure this feature.
• Integration with Office Setup. The Lync 2013 client and the Online Meeting Add-in for Lync 2013—
which supports meeting management from within the Outlook messaging and collaboration client—
are now both included with the Office 2013 Setup program.
In previous versions of Lync and Office Communicator, you could use Windows Installer properties to
customize and control the Office installation. Because Lync 2013 is integrated with Office setup, you can
use the following to customize the Lync 2013 setup:
• Merge this call into. While in a meeting, users can merge another open conversation into the meeting
by using Merge This Call Into, on the More Options (…) menu.
• View/Show Participants. To see participants’ names, users can hover the mouse pointer over the View
Participants button, or click Show Participant List to dock the panel in the meeting.
• Manage Presentable Content. Users can also use the Manage Presentable Content menu to choose
which content they want to share.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-5
• Share Content and Lead Meeting Activities. Users can switch between content types by using Share
content and lead meeting activities at the lowermost part of the meeting room window.
• Presence While Sharing. When Lync detects that a user is sharing, Lync automatically assigns the user
a Presenting status. This status blocks all incoming communications unless the sender is assigned the
Workgroup privacy relationship. If the user is using the sharing feature entirely on a secondary
monitor, Lync does not assign a Presenting status.
• Presentation Mode. In an A/V conference, the presenter can set the conference state so that all other
participants, including anybody who subsequently joins the meeting, are muted. While the
conference is in this state, individual participants cannot unmute themselves. The presenter can later
change the conference state, for example, to open the conference for questions. At that time, users
receive a notification that they can now unmute themselves.
Join Launcher
Lync Server 2013 updates the Join Launcher to
validate each meeting before launching a client,
and to provide support for opening a meeting in
the following clients:
• Windows Phone 7
• Android devices
• Windows 8
• Internet Explorer 10
You should start the web client where the Organizer is homed, because this provides the appropriate
experience (Lync 2010 or Lync 2013). The closer you get to the server, the better is the experience and
performance for the end-user.
the specific pool where the organizer is installed. The request is therefore proxied to the proper Front-End
server.
In-Conference Collaboration
Previously, when a PowerPoint presentation was
shared, the client converted the PowerPoint into a
lower format (PowerPoint 1997-2003) version.
That version was sent to the server. The server
then instructed all the clients to download a copy
of that PowerPoint. The embedded PowerPoint
viewer of the client would then be able to view it.
The server at this point only sends instructions (go
back, go to slide #, go forward). This native viewer
had limitations.
When the request is made to present a file, the base URL is taken to encode a few things such as file ID,
meeting ID, unique identifier of the actual front-end server hosting the meeting) and sends it to the client.
Additional security is also provided by a session lifetime token and is put in the URL. After the viewer
client gets the URL, the client connects to the provided URL to view the presentation from the WAC
server. The WAC server then makes the request to the Lync Server and the file is provided through the
filecontent server. Then, the presentation happens directly between the client and the WAC server.
Topology Impacts
Dial-out behavior for mobile users stays the same as with Lync 2010 Cumulative Update 4 (CU4) (when
mobility was introduced).
1. Exchange is the one place where you can configure archiving settings for the user for email, IM, and
Conference Archiving. In the past, without the Exchange integration, IM and Conference Archiving
had to be done on Lync.
2. Information captured from Lync sessions is put directly into the Exchange mail boxes. Discovery tools
provided by Exchange can then be used to search for the Lync communication records.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-9
Deployment Considerations
Determining which conferencing capabilities to
deploy depends not only on the features you want
available to your users, but also on your network
bandwidth capabilities. You should consider the
following factors when you want to deploy
conferencing.
Note A complete Enterprise Voice solution is not necessary for A/V conferencing. If you enable A/V
conferencing, users can add audio to their conferences if they have audio devices, even if you use a
private branch exchange (PBX) for your telephone solution.
Enabling Users to Join the Audio Portion of Conferences When Using a PSTN Phone
If you want to enable users to join the audio portion of conferences when using a PSTN phone, you
should deploy and enable dial-in conferencing. Invited users, both inside and outside your organization,
can then join the audio portion of conferences by using a PSTN phone.
Enabling External Users with Lync Server 2013 Clients to Join the Conference
If you want to enable external users with Lync Server clients to join the types of conferences that you have
enabled, you should deploy Edge Servers. Allowing external participation in meetings maximizes an
MCT USE ONLY. STUDENT USE PROHIBITED
5-10 Conferencing in Lync Server 2013
organization’s investment in Lync Server. For example, users with laptops with Lync Server 2013 can join
conferences from wherever they are—at home, in an airport, or at customer sites—without the need for a
PSTN connection.
Additionally, if you deploy Edge Servers, you can create federated relationships with other organizations—
such as your customers or vendors—and users from those organizations can more easily collaborate with
your users.
Migration Considerations
You should also consider the following factors when migrating users.
• Meetings already scheduled by the user. This only includes Communicator conference calls (conf: URL
scheme). Live Meetings are not migrated to Lync 2013. Users will need to reschedule these meetings
as new Lync meetings. This is discussed in more detail later in the course.
• The user’s PIN. The user’s current PIN continues to work until it expires or the user requests a new
PIN.
The following information does not move to the new server:
• Meeting content. You should advise meeting organizers to reload content into their scheduled
meetings, after migration.
Note Existing dial-in conferencing numbers work whether the meeting is hosted on Office
Communicator 2007 R2/Lync 2010 server or a Lync Server 2013 server. However, the latest Office
Communicator 2007 R2/Lync 2010 cumulative update is required on the Office Communicator 2007
R2/Lync 2010 server pools.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-11
Lesson 2
Designing for Audio/Video and Web Conferencing
Before you design for audio/video and web conferencing in a Lync Server 2013 deployment, you must
consider the business and compliance requirements. Designing for web conferencing will require you to
select between hosted and on-premises conferencing. You should be able to design audio/video and web
conferencing, design conferencing policies, and calculate network requirements for audio/video and web
data.
Lesson Objectives
• Assess detailed business and compliance requirements.
As an infrastructure architect, you need to choose between on-premises and hosted services based on the
features and scalability that are required by the organization. Before choosing between on-premises and
hosted services, you need to analyze the following criteria:
• Scalability. The service should enable hosting large multinational conferences by using Lync Online.
• Support. The service should support users from many time zones and nationalities.
• Time to deploy. The service should take less time to deploy. A hosted web conferencing service
solution needs less time to plan and design than an on-premises service solution.
• Flexibility in deployment. The service should be easily deployable, for example, the head office on-
premises, and certain branch offices online.
• If audio is enabled, anonymous users cannot dial out from meetings. To allow anonymous users to
dial out, you need to select the Allow anonymous users to dial out check box.
• If schedule meetings are allowed, both application sharing and desktop sharing are allowed.
Scaling
Meeting size Each pool can host a meeting If you require the system to
for one through 250 users at a host large conferences, add
time. While the meeting is in a separate pool for
progress, the pool can also conferencing. Alternatively,
host other smaller conferences you can apply a user-specific
for up to 125 users. conferencing policy to allow
Lync Server 2013 can support a limited group of users to
large meetings up to 1,000 create large conferences.
participants. Supporting large
meetings of up to 1,000 users
requires creating an
appropriate topology,
meeting hardware and
software prerequisites, and
configuring the environment
appropriately.
Security
Application and You can allow participants to The security risk involves a
desktop sharing share your desktop and malicious user who can
applications during a share the content of the
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-15
Content download and You can allow all users to You need to control files
file transfer download the content from entering and leaving your
conferences that can be network because of malware
authenticated, federated, and detection and
anonymous. A similar security confidentiality. You should
option is to allow peer-to- discuss this with the
peer file transfers. concerned stakeholders of
the organization, and then
set policies accordingly.
Preventing recording of The meetings can be recorded You should discuss this
meetings only on the local machines concern with the security
from where the presenter or organization. You must plan
attendee is joining the whether the recording is to
meeting or audio call. be enabled for all
presenters, participants,
authenticated participants,
and anonymous users.
Question: Describe how security designs can drive the collaboration solution of an
organization?
• Simple URL:
https://meet.adatum.com/bill/VT9IKTHG
• SIP URI:
sip:bill@adatum.com;gruu;opaque=app:conf:f
ocus:id:VT9IKTHG
• Meet. It is used as the base URL for all conferences in the site or organization. You can define a
different meet URL per SIP domain.
• Dial-in. It enables access to the Dial-in Conferencing Settings webpage. This page displays conference
dial-in numbers with their available languages, assigned conference information, and in-conference
Dual Tone Multi-Frequency (DTMF) controls. This simple URL supports management of PIN and
assigned conferencing information.
• Admin. It enables quick access to the Lync Server 2013 Control Panel. The design for simple URLs
applies to the Admin URL also. This simple URL is only used internally.
Using a split brain DNS, you can host a DNS zone on various networks with different DNS records.
Therefore, the fully qualified domain name (FQDN) can point the Internet to your reverse proxy, but the
same FQDN points to the pool in your internal deployment.
G.722 64.0
Siren 16.0
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-17
The following table outlines the video codec, resolution, and video payloads for conferencing.
The following table outlines an example from the Lync Server 2013 user models that you can use to
profile network requirements for conferencing data.
Conferencing Model
Category Description
Category Description
Server 2013 Web App: 5 percent
http://go.microsoft.com/fwlink/?LinkId=273835
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-19
Lesson 3
Dial-In Conferencing in Lync Server 2013
Lesson Objectives
• Describe the dial-in conferencing features in Lync Server 2013.
• Describe the deployment steps for dial-in conferencing in Lync Server 2013.
Note Enterprise users who dial-in from an office IP phone or from Lync 2013 are not prompted for
their phone number because they are already authenticated.
unless the meeting policy allows users dialing in to bypass the lobby. Unauthenticated anonymous users
are also prompted to record their name. The recorded name identifies unauthenticated users in the
conference.
Note Enterprise users who choose not to enter their phone number and PIN are not authenticated,
and thus, are prompted to record their name.
Dial-In Participants
Dial-in participants hear music if they are waiting to be admitted to the conference. After they are
admitted to a conference, dial-in users can participate in the audio portion of the conference and can
exercise dual-tone multi-frequency (DTMF) commands by using the phone keypad.
Dial-in participants, whether or not they dial from the PSTN, hear personal announcements during the
conference, such as whether:
Dial-in Leaders
Dial-in leaders and some client users can exercise DTMF commands to turn participants' ability to unmute
on or off, lock or unlock the conference, admit people from the lobby, and turn entry and exit
announcements on or off. Leaders and some client users can also use a DTMF command to admit
everyone from the lobby, which changes the permissions of the meeting to allow anyone who
subsequently joins.
Note Participants who join the conference by clicking a link, instead of dialing in, do not hear
personal announcements.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-21
Note We recommend that you install Windows Media Format Runtime before you run Setup because
Windows Media Format requires you to restart your computer after it is installed.
Port Requirements
If you use a load balancer, ensure that the load balancer is configured for the ports used by any
applications that will run in the pool. These ports are default settings that you can change by using the
Set-CsApplicationServer cmdlet.
Note All instances of the same application in a pool use the same SIP listening port.
The following table lists and describes the ports that are used by dial-in conferencing.
Port
Description
number
• 16-bit mono
• 48 kbps 2-pass constant bit rate (CBR)
Note If you have a strong business need that requires you to change the default voice prompt or music
file, you can customize your media files by following the procedure found in the article located at
http://go.microsoft.com/fwlink/?LinkId=210264.
Application Service
Application service provides a platform for
deploying, hosting, and managing unified
communications (UC) applications. Dial-in
conferencing uses two UC applications that
require Application service—Conferencing
Attendant and Conferencing Announcement.
Conferencing Attendant
Conferencing Attendant is a unified communications application that accepts PSTN calls, plays prompts,
and joins the calls to an A/V conference. When a user is prompted to enter their conference information,
Conferencing Attendant uses interactive voice response (IVR). When the call is connected to the
conference, Conferencing Attendant backs out and client access server (CAS) takes over.
Conferencing Announcement
Conferencing Announcement is a UC application that plays tones and prompts to PSTN participants on
certain actions, such as when participants join or leave a conference, participants are muted or unmuted,
someone enters the conference lobby, or the conference is locked or unlocked. Conferencing
Announcement also supports DTMF commands from the phone keypad.
• A PSTN gateway
• An IP-PBX
• A Session Border Controller (SBC) for an Internet telephony service provider to which you connect by
configuring a SIP trunk
Note If your Lync design includes Enterprise Voice, Mediation Servers and PSTN connectivity options
will already be part of the deployment. If you are not deploying Enterprise Voice, you will need to
deploy at least one Mediation Server and at least one PSTN connectivity option for dial-in conferencing
to function.
MCT USE ONLY. STUDENT USE PROHIBITED
5-24 Conferencing in Lync Server 2013
File Store
File store is used for recorded name audio files. File store is a standard component in every Enterprise
Edition or Standard Edition deployment.
User Store
User store is used to store user Lync Server 2013 PINs. PINs are encrypted. The user store is a standard
component in every Lync Server 2013 Enterprise Edition or Lync Server 2013 Standard Edition
deployment.
Note This step is required only if you do not deploy Enterprise Voice and do not collate the
Mediation Server with the Enterprise Edition front-end server or Standard Edition server. If you deploy
Enterprise Voice, you install and configure Mediation Servers and PSTN gateways as part of the
Enterprise Voice deployment. If you collate the Mediation Server, you install and configure the
Mediation Server as part of the front-end pool or Standard Edition server deployment.
• RTCUniversalServerAdmins Group
• CsVoiceAdminstrator
• CsAdminstrator
Use the Lync Server Control Panel or Lync Server Management Shell to set up dial plans as follows:
1. Create one or more dial plans for routing dial-in access phone numbers.
2. Assign a default dial plan to each pool. Set the Dial-in conferencing region to the geographic location
to which the dial plan applies. The region associates the dial plan with dial-in access numbers.
The following permissions are required to configure dial plans for dial-in conferencing:
• CsVoiceAdminstrator
MCT USE ONLY. STUDENT USE PROHIBITED
5-26 Conferencing in Lync Server 2013
• CsAdministrator
The following permissions are required to ensure dial plans for assigned regions:
• CsVoiceAdminstrator
• CsAdministrator
The following permission is required to configure conferencing policy for dial-in conferencing:
• CsAdministrator
Note After you create dial-in access numbers, you can use the Set-
CsDialInConferencingAccessNumber cmdlet to modify the display name of the Active Directory
contact objects, so that users can more easily identify the correct access number.
• CsAdministrator
• CsAdministrator
• CsViewOnlyAdministrator
• CsServerAdminstrator
• CsHelpDesk
• CsAdministrator
• CsAdministrator
• CsAdministrator
• CsUserAdminstrator
Step 12: Welcome Users to Dial-in Conferencing and Set the Initial PIN (Optional).
Use the Set-CsPinSendCAWelcomeMail script to set users' initial PINs and send a welcome email
message that contains the initial PIN and a link to the Dial-in Conferencing Settings webpage.
The following permissions are required to welcome users to dial-in conferencing and set the initial PIN:
• CsAdministrator
• CsUserAdminstrator
MCT USE ONLY. STUDENT USE PROHIBITED
5-28 Conferencing in Lync Server 2013
Lesson 4
Managing and Administering Conferencing
Most of the policy settings that determine Lync Server 2013 conferencing are configurable through Lync
Server Control Panel. However, there are several essential policies and settings that impact conferencing
and that can only be configured by using Lync Server Management Shell. You should, therefore, know
how to manage and administer conferencing policies by using Lync Server Control Panel and Lync Server
Management Shell.
Lesson Objectives
• Manage and administer conferencing by using Lync Server Control Panel.
4. In the New Conferencing Policy dialog box, in the Name box, type the policy name.
5. To modify the default policy settings, choose from any of the following options.
Setting
Enable recording
Audio/video
• Data collaboration:
• Allow external users to download content
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-29
Setting
• Allow users to transfer files
• Allow users to transfer files by using peer-to-
peer
• Enable the use of annotations
6. Click Commit.
Important Lync Server Control Panel cannot be used to manage users who are members of the
Active Directory Domain Admins group. For Domain Admin users, you can use Lync Server Control
Panel only to perform read-only search operations. To perform write operations as Domain Admin
users, such as enable or disable for Lync Server, change pool or policy assignments, telephony
settings, SIP address, or perform other tasks, you must use Windows PowerShell cmdlets while logged
on as a Domain Admin.
4. In the Edit Conferencing Policy dialog box, choose from any of the following options.
Setting
Enable recording
Audio/video
• Data collaboration:
• Allow federated and anonymous participants
to download content
MCT USE ONLY. STUDENT USE PROHIBITED
5-30 Conferencing in Lync Server 2013
Setting
• Allow participants to transfer files
• Enable annotations
• Enable polls
Application sharing
5. Click Commit.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-31
Get–CsConferencingConfiguration
Set-CsConferencingConfiguration
Note You can also create additional sets of conferencing configuration settings for specific sites. Use
the New-CsConferencingConfiguration cmdlet with a site identity. When you create new
conferencing configuration settings for sites, the site settings take precedence over the global
settings.
MCT USE ONLY. STUDENT USE PROHIBITED
5-32 Conferencing in Lync Server 2013
Content
The content-related setting includes:
• MaxContentStorageMb. Maximum amount of file space (in megabytes) allowed for the storage of
meeting content.
Media
The media-related settings include:
• ClientMediaPort. Represents the starting port number used for client media.
• ClientMediaPortRange. Indicates the total number of ports available for client media.
• ClientMediaPortRangeEnabled. When set to True, clients will use the specified port range for media
traffic. When set to False (the default value) any available port (from port 1024 through port 65535)
will be used to accommodate media traffic.
Audio
The audio-related settings include:
• ClientAudioPort. Represents the starting port number used for client audio.
• ClientAudioPortRange. Indicates the total number of ports available for client audio.
Video
The video-related settings include:
• ClientVideoPort. Represents the starting port number used for client video.
• ClientVideoPortRange. Indicates the total number of ports available for client video.
Application Sharing
The client application sharing-related settings include:
• ClientAppSharingPort. Represents the starting port number used for application sharing.
• ClientAppSharingPortRange. Indicates the total number of ports available for application sharing.
File Transfer
The client file transfer-related settings include:
• ClientFileTransferPort. Represents the starting port number used for file transfers.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 5-33
• ClientFileTransferPortRange. Indicates the total number of ports available for file transfers.
SIP
The SIP-related settings include:
• ClientSipDynamicPort. Represents the starting port number used for SIP traffic.
• ClientSipDynamicPortRange. Indicates the total number of ports available for SIP traffic.
Organization
The organization-related setting includes:
Help Desk
The help desk-related settings include:
• HelpDeskInternalUrl. URL where internal users who click Help during a conference will be directed.
• HelpDeskExternalUrl. URL where external users who click Help during a conference will be directed.
Console Download
The console download-related settings include:
Objectives
1. Deploy the Web Apps Component server for Microsoft Lync Server 2013.
Lab Setup
Estimated Time: 75 minutes
The goal of this lab is to:
• Introduce the new UC client and help build an understanding of its integration components.
• Create and configure policies to manage conferencing settings.
Important On all virtual machines, verify that all the services set to start automatically have started. Most
notably, check the Exchange, SQL Server®, and Lync Server 2013 services. To do so, click Start, click
Administrative Tools, and then click Services. In the Services console, verify that all services set to
Automatic start have started. If not, right-click the service, and then click Start.
Results: After completing this exercise, you should have configured dial-in conferencing, first by
configuring Regions for the dial plans, and then configuring US and UK dial-in access numbers. Then, you
used the Lync Server 2013 Management Shell to test the conferencing numbers.
• Site for London the Maximum meeting size should be 100, allow Recording, and enable PSTN dial-in
conferencing.
• Site for Redmond the Maximum meeting size should be 100, disallow Recording, and enable PSTN
dial-in conferencing.
• User with Description Adatum Unrestricted Conferencing Policy, allow Recording, allow federated and
anonymous participants to record, allow anonymous participants to dial out, allow federated and
anonymous participants to take control and Enable peer-to-peer recording
Assign users Adam Barr and Alex Darrow global conferencing policy and do the required testing. And
then assign them Unrestricted conferencing policy and do the required testing.
The main tasks for this exercise are as follows:
Results: After completing this exercise, you should have edited the global conferencing policy, created
two site policies and one unrestricted user policy.
Results: After completing this exercise, you should have tested and verified the dial-in conferencing
access numbers you earlier configured. You also tested and verified the application of conferencing
policies, and reviewed the features of Lync Server 2013 conferencing.
MCT USE ONLY. STUDENT USE PROHIBITED
5-38 Conferencing in Lync Server 2013
• For two-party calls, video resolution is the same as in the legacy pool.
• For multiparty conferences, video resolution and video conferencing features are the same as in the
legacy pool. Gallery View and high resolution are not available.
Legacy Pools
Users may experience the following when a Lync Server 2013 client is used in a legacy pool:
• For two-party calls, Lync Server 2013 clients can use new features such as:
o H.264, which is available if both participants use Lync Server 2013 clients.
• The Lync Server 2013 client uses the default value for TotalReceiveVideoBitRateKb, because the
legacy server does not send this information with in-band provisioning.
• For multiparty conferences, video resolution and video conferencing features are the same as
experienced by a legacy client in the legacy pool.
When a legacy server hosts a Lync Server 2013 client, it is possible to configure video conferencing
bandwidth so that all users in the pool receive only low-resolution video, but send high-resolution
video. An example of this is when MaxVideoRateAllowed is set to CIF-250K in the media configuration
and VideoBitRateKb is set to 2,000 kbps in the conferencing policy. The effect in this situation is that
high resolution is not possible for users in the pool.
Because MaxVideoRateAllowed is no longer used for Lync Server 2013 clients, it cannot prevent Lync
Server 2013 clients from requesting high-resolution video. Instead, set VideoBitRateKb in the
conferencing policy for all users in the pool to the same value as MaxVideoRateAllowed (that is, CIF is
set to 250 kbps, or VGA is set to 600 kbps, or HD is set to 1,500 kbps).
Review Question(s)
Question: What is another option for providing external access to Office Web Apps server?
Module6
Designing and Deploying External Access
Contents:
Module Overview 6-1
Module Overview
Microsoft® Lync® Server 2013 contains a number of external access components and capabilities, and
you need to use these components in you design, to meet the organization’s needs. You should be able
to design a solution for external scenarios that support a variety of internal and external users connected
to the Internet, so that they can access their corporate network or the public switched telephone network
(PSTN) for conferencing.
Objectives
• Describe the conferencing capabilities of Lync Server 2013.
• Design audio and video for web conferencing.
Lesson 1
Conferencing and External Capabilities of Lync Server
2013
Lync Server 2013 is a Unified Communications platform; therefore, conferencing is the main focus of the
software. While deploying Lync Server 2013, you need to plan for Presence and instant messaging (IM),
audio/video conferencing, and web conferencing. You will also need to consider users outside the firewall
who may be using the Extensible Messaging and Presence Protocol (XMPP) Gateway. To control the types
of communications that travel across the firewall, you can create global policies. You can also design the
various conferencing capabilities that comprise a Lync Server 2013 solution. You should also be able to
use the security features in conferencing and external scenarios.
Lesson Objectives
• Describe the conferencing capabilities of Lync Server 2013.
• Describe Public Instant Messaging in Lync Server 2013.
• Web conferencing
• Audio conferencing
• Video conferencing
• Integration with third-party audio/video Session Initiation Protocol (SIP) endpoints and multipoint
control units (MCUs)
Although there are a variety of access methods and client versions that provide varied conferencing
capabilities, Lync Server 2013 provides a rich conferencing experience. As part of your solution design,
you must assess the best solution for each of your user scenarios.
Question: In your opinion, are there any important conferencing modalities missing from
Lync Server 2013?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-3
At release, Lync Server 2013 will also provide PIC to the Skype service, and peer-to-peer instant
messaging, Presence, and audio collaboration.
• Managing any namespace collisions between existing Windows Live Messenger users and the Lync
Server 2013 implementation.
PIC does not support Domain Name System (DNS) load balancing for your Edge Servers.
Question: Lync Server 2013 provides security and compliance as long as communication is
internal to the organization. What happens after traffic leaves the Lync Server 2013 Edge
Server and travels to the PIC user? Is security still guaranteed?
MCT USE ONLY. STUDENT USE PROHIBITED
6-4 Designing and Deploying External Access
Question: Can you describe the available deployment models? In which scenarios are these
models most appropriate?
Previous versions of Lync Server and Office Communications Server provided an XMPP gateway that could
be deployed as a separate server role to allow federating with XMPP deployments. In Microsoft Lync
Server 2013, the XMPP functionality can be deployed as a feature. XMPP functionality is installed in two
parts: an XMPP proxy that runs on the Edge Server, and the XMPP gateway that runs on the front-end
servers.
XMPP Federation—Architecture
The following improvements have been made in
XMPP Federation:
• Google Talk is the tested scenario, but is prevented from opening to other XMPP gateways.
A conferencing policy defines the features and capabilities for users during a conference (also known as a
meeting). Conferencing policy settings encompass a wide variety of scheduling and participation options,
ranging from whether a meeting can include IP audio and video, to the maximum number of people who
can attend. Administrators can use the conferencing policy to manage security, bandwidth, and legal
aspects of meetings.
You can define a conferencing policy on three levels: global scope, site scope, and user scope. Settings
apply to a specific user from the narrowest scope to the widest scope. If you assign a user policy to a user,
MCT USE ONLY. STUDENT USE PROHIBITED
6-6 Designing and Deploying External Access
those settings take precedence. If you do not assign a user policy, site settings apply. If no user or site
policies apply, the global policy provides the default settings.
A global policy exists by default, so you cannot create a new global policy. You also cannot delete the
existing global policy, but you can change the existing global policy to customize your default settings.
By default, there are no policies configured to support external user access, including remote user access
and federated user access, even if you have already enabled external user access support for your
organization. To control the use of external user access, you must configure one or more policies,
specifying the type of external user access supported for each policy. The following policy scopes are
available for creation and configuration.
• Global policy. The global policy is created when you deploy your Edge Servers. By default, no external
user access options are enabled in the global policy. To support external user access at the global
level, you configure the global policy to support one or more types of external user access options.
The global policy applies to all users in your organization, but site policies and user policies override
the global policy. If you delete the global policy, you do not remove it. Instead, you reset it to the
default setting.
• Site policy. You can create and configure one or more site policies to limit support for external user
access to specific sites. The configuration in the site policy overrides the global policy, but only for the
specific site covered by the site policy. For example, if you enable remote user access in the global
policy, you might specify a site policy that disables remote user access for a specific site. By default, a
site policy is applied to all users of that site, but you can assign a user policy to a user to override the
site policy setting.
• User policy. You can create and configure one or more user policies to limit support for remote user
access to specific users. The configuration in the user policy overrides the global and site policy, but
only for the specific users to whom the user policy is assigned. For example, if you enable remote user
access in the global policy and site policy, you might specify a user policy that disables remote user
access and then assign that user policy to specific users. If you create a user policy, you must apply it
to one or more users before it takes effect.
Note: Lync Server policy settings that are applied at one policy level can override settings
that are applied at another policy level. Lync Server policy precedence is user policy (most
influence) overrides a site policy, and a Site policy overrides a global policy (least influence). This
means that the closer the policy setting is to the object that the policy is affecting, the more
influence it has on the object.
When configuring policies for external access, the following settings are available:
• Enable communications with federated users. You can select this option if you want to support user
access to federated partner domains. This setting configures the ability for users to communicate with
other SIP federated domains, and hosted providers like Microsoft Office 365. Selecting this setting
enables you to select the option to allow communication with XMPP federated domains.
As an option, you can select Enable communications with XMPP federated partners if you first select
Enable communications with federated users. XMPP federation is a federation with organizations that
use XMPP.
Note: If you enable XMPP federation, you must also select to deploy XMPP federation in
the Edge pools configuration section of Topology Builder.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-7
• Enable communications with remote users. You can select this option if you want users in your
organization who are outside your firewall, such as telecommuters and users who are traveling, to
connect to Lync Server over the Internet.
• Enable communications with public users. You can select this option if you want internal users to
communicate with public IM provider contacts, such as those provided by Windows Live and Skype.
Question: What are the options you have for blocking unwanted users from participating in
web and audio/video conferences?
Note: The role of the Director server in the Lync Server 2013 topology has not changed. It
still hosts web services and pre-authenticates incoming user requests, and directs external users
to their home pool. Changing the Director from a recommended role to an optional role does
not diminish the value of the Director, but emphasizes reducing server count and other hardware
requirements (for example, hardware load balancers for the Director) without compromising
features and functionality. Because the front-end servers can do the same job as the Director with
no impact to services provided, you can choose to optionally deploy Directors. You can safely
exclude the Director with confidence that the front-end servers will provide the same services in
their place.
• Set the conferencing policies to prevent unsupported usage scenarios. Consider the scenario of
downloading material for attendees and transferring of files.
• Keep the default security settings that require Transport Layer Security (TLS) or Secure Sockets Layer
(SSL) in all signaling and media.
• Evaluate the need for using applications that help prevent attack from malicious software, such as
Forefront Security for Lync Server 2013.
Note: At the writing of this document, ForeFront for Lync Server 2013 was still in
development.
• Avoid deployment of your Edge Servers in an internal domain. You can use the workgroup or
perimeter domain, instead.
MCT USE ONLY. STUDENT USE PROHIBITED
6-8 Designing and Deploying External Access
• Deploy the Edge Server between an internal firewall and an external firewall.
• Evaluate the need for anonymous or federated access to your organization. You must trust the
authentication that your partners implement in their organizations.
Question: In which scenarios do you have security concerns in a Lync Server 2013 solution?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-9
Lesson 2
Planning for IM and Presence Federation
When you plan for IM and Presence federation, you need to be aware of the different federation scenarios
available for federation with partners running Lync Server 2013. IM and Presence federation may also
require Lync Server 2013 to interoperate with non-Microsoft environments. You should be familiar with
the federation and interoperability scenarios, and the public instant messaging provisioning process to
plan for IM, including the supported functionality.
Lesson Objectives
• Describe federation scenarios.
Some of the federation options available to partners running Lync Server 2013, Lync Server 2010, Office
Communications Server 2007, Office Communications Server 2007 R2, or Microsoft® Office Live
Communications Server are as follows:
Direct Federation
In this option, you can allow federation only with specific SIP domains and certain servers at these SIP
domains. Organizations federating with a limited number of partners or enabling very high volume SIP
traffic between two large federated organizations can benefit from this federation option.
Enhanced Federation
In this option, you can allow federation with specific SIP domains. Servers are auto-resolved through DNS
service records. Organizations that federate with a limited number of partners who use open federation or
enable very high volume of SIP traffic between two large federated organizations can benefit from this
federation option.
MCT USE ONLY. STUDENT USE PROHIBITED
6-10 Designing and Deploying External Access
Open Federation
In this option, Lync Server 2013 automatically identifies the federation partners. This federation option
works in combination with a block list, where you can lock certain domains for communication. It is the
most user-friendly federation option. However, you must initiate a process to monitor the Event Viewer to
add partners to the list of Enhanced Federation partners or SIP domains that you want to block.
Note: Currently, the XMPP services in Lync Server 2013 only provide instant messaging and
Presence between Lync clients and XMPP-based contacts.
You can enable federation with Google Talk and Jabber by using Lync Server 2013 Edge as an XMPP
proxy and the Lync Server 2013 front-end as an XMPP gateway.
Besides Google Talk and Jabber, Lync Server 2013 also supports federation with certain third-party
Presence solutions such as IBM® Lotus® Sametime® and Cisco Presence. Integration with Cisco Presence
allows integration for IM and Presence with Lync Server 2013 by using specific adaptive security
appliances and gateways. These are some of the interoperability options. The interoperability program is
an ever evolving program, and keeps adding new interoperability scenarios.
Note: At the writing of this document, we cannot confirm which versions of IBM SameTime
and Cisco Presence have been tested with Lync Server 2013.
For more information about the Unified Communications Open Interoperability Program
http://go.microsoft.com/fwlink/?LinkId=273836
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-11
As part of the provisioning process, you need to provide the following details to Microsoft:
• SIP domains
• Contact information
The information provided by you is tested, your credibility is established, and then you are provided
access to the environment. After testing, you will be notified and the provisioning process for each PIC
domain will begin.
• IM and Presence. Users can send instant messages and view Presence status without using a virtual
private network (VPN) to log on to the internal network. They can add users from federated partners
and users of supported public IM service providers to their contact list, and they can view those users’
Presence status, even while they are signed in remotely.
• Web conferencing. Users can participate in web conferences as if they were logged on to the internal
network.
• Audio/video conferencing. Users can participate in audio/video conferences as if they were logged on
to the internal network.
• IM and Presence only. Users can participate in IM conversations with individual Lync Server 2013 users
in the organization and access Presence information. However, they cannot participate in Lync Server
2013 multi-party conferences, and they are restricted to peer-to-peer conferencing. You can choose
this option whether or not you deploy conferencing support internally.
• IM and Presence, web conferencing, and A/V conferencing. Users can participate in IM conversations
with individual Lync Server 2013 users in the organization and access Presence information. They can
also participate in web conferences and audio/video conferences, if you have planned for it in your
Lync Server 2013 deployment. Federated users have access to the full feature set, except the Lync
Server 2013 Address Book.
• IM and Presence only. Users can participate in IM conversations with individual Lync Server 2013 users
in the organization and access Presence information. However, they cannot participate in Lync Server
2013 multi-party conferences, and they are restricted to peer-to-peer conferencing.
Question: Do you perceive opportunities for business usage for audio sessions between Lync
Server 2013 and Skype?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-13
Lesson 3
Designing Edge Services
To design Edge services, you should be familiar with firewall requirements for external scenarios, identify
Edge network requirements, define filters, and determine your deployment options for Edge Services.
In a Lync Server 2013 deployment, DNS is a core infrastructure component without which the Lync Server
2013 infrastructure cannot function. You should know about the uses of DNS, required DNS records, and
requirements for DNS servers.
You should also know about Public Key Infrastructure (PKI) and certificates, and how to use TLS and
Mutual Transport Layer Security (MTLS or Mutual TLS) in your Lync Server 2013 environment. In addition,
you should know about the uses of PKI, subject names, and subject alternative names, including the types
of certificates and certificate providers.
Lesson Objectives
• Describe how to design firewall requirements for external scenarios.
• Describe Edge network requirements.
• Define filters.
Question: Which other tool can you use to help you with this design?
Question: How important are the modalities that require the 50.000–59.999 port range?
Question: How do you think your security or firewall organization will respond to these
requirements?
In Lync Server 2013, if you use NAT, you always have to use either routable IP addresses or a 1:1 relation,
where one routable IP address corresponds exactly to one private IP address.
Depending on the following deployment scenarios, routable IP addresses or NAT must be used:
• The internal interface of the Edge Server must always be routable. It can still be an internal IP address;
however, an internal client must be able to reach the IP address of the internal Edge interface without
any NAT.
• A single Edge Server requires a 1:1 NAT. In Office Communications Server 2007 R2, we required a
routable IP. However, the 1:1 NAT scenario is tested, and therefore, supports the deployment
scenario. You must configure symmetric NAT for incoming and outgoing traffic.
Depending on your DNS architecture, you may need to set up a hosts file for resolution of internal hosts
on your network. The recommended approach is to point DNS to your internal DNS servers. However, this
works if your internal DNS forwards unresolved requests to public DNS servers.
Question: Can you use NAT to translate the internal network interface of the Edge Server?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-15
Defining Filters
When you allow content to be published to
external users and content to be sent from
external users to internal users, you might want to
control this situation. The options in Lync Server
2013 include controlling specific versions of clients
allowed, defining file filters based on extensions
and URL filters—allowing or disallowing certain
URLs.
File Filters
File filters can be applied either on a global level or on a site level. You can use these filters to block all
files or only block certain types of files from entering your network. By default, the following files are
blocked.
Blocked Files
URL Filters
With URL filters, you can block certain URLs from being clicked, and you can define this at a global level
or at a site level. For example, you can block ftp, gopher, news, and similar filters, or just enable URL filter
and provide a warning message.
To configure how hyperlinks are handled in instant message conversations, you select one of the
following options under Hyperlink prefix:
• Do not filter. URLs in messages are sent through the server. When you choose this option, the Allow
message box appears. In the Allow message box, specify the notice that you want to insert at the
beginning of each instant message containing hyperlinks. This notice can consist of no more than
65,535 characters.
• Block hyperlinks. Delivery of instant messages containing active hyperlinks is blocked by Lync Server,
and an error message is displayed to the sender.
• Send warning message. Lync Server permits active hyperlinks in instant messages, but includes a
warning. When you choose this option, the Warning message box appears. In the Warning
MCT USE ONLY. STUDENT USE PROHIBITED
6-16 Designing and Deploying External Access
message box, you must type the warning that you want to include with instant messages containing
valid hyperlinks. For example, the warning might state the potential dangers of clicking an unknown
link, or it might refer to your organization’s relevant policies and requirements. The warning can be
no more than 65,535 characters.
For more advanced filtering capabilities, you should look at solutions from Microsoft® ForeFront® or
third-party solutions that look at the actual file content to determine the type of file being sent, and
provide more granular policy options.
• AllowWithUrl. The user will be allowed to log on, and a message will be displayed pointing the user to
a URL where the latest version of Lync can be downloaded and installed. The URL must point to a
website that you have created yourself; no such site is created for you when you install Lync Server.
• Block. The user will not be allowed to log on.
• BlockWithUrl. The user will not be allowed to log on, but a message will be displayed pointing him or
her to a URL where the latest version of Lync can be downloaded and installed. The URL must point
to a website that you have created yourself; no such site is created for you when you install Lync
Server.
• Client version rules are collected in client version policies; you can configure these policies at the
global scope, the site scope, the service scope (Registrar service), or the per-user scope. You can use
the Set-CsClientVersionPolicyRule cmdlet to modify the properties of an existing client version rule.
Question: Can you get any inspiration for policies from other applications/usages in your
organization?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-17
• Enable external servers and clients to connect to Edge Servers or the HTTP reverse proxy for instant
messaging (IM) or conferencing.
• Enable external UC devices to connect to Device Update web service through Edge Servers or the
HTTP reverse proxy and obtain updates.
• Enable mobile clients to automatically discover web services resources without requiring users to
manually enter URLs in device settings.
Typically, the DNS server is based on Windows Server, but other DNS implementations are also supported
if they are able to support the requirements for Lync Server 2013. To plan for the installation of Lync
Server 2013 and the DNS required records, you can use the Lync Server 2013 Planning Tool. After
finalizing your topology design, you can access the external and internal DNS records listed under the
DNS Report tab, in Edge Admin Report, under the Planning Tool Report option.
Split-brain DNS is known by a number of names, for example, split DNS or split-horizon DNS. It describes
a DNS configuration where there are two DNS zones with the same namespace—DNS zone services
internal-only requests, and DNS zone services external-only requests. However, many of the DNS SRV and
A records contained in the internal DNS will not be contained in the external DNS. The reverse is also true.
In cases where the same DNS record exists in both the internal and external DNS (for example,
www.contoso.com), the IP address returned will be different based on where (internal or external) the
query was initiated.
In a Lync Server 2013 deployment, DNS is important. If you host your own external DNS servers, while
planning and designing the topology, you must focus on the availability of these services, both internally
and externally. Deploying a Standard Edition front-end server in a remote location for survivability may
not be beneficial, if the DNS resolution is dependent on a remote wide area network (WAN) connectivity.
You must note that Survivable Branch Appliances (SBA) and servers can use Dynamic Host Configuration
Protocol (DHCP) for survivability, but only for the SIP registrar and Mediation Server role included in Lync
Server 2013.
You can choose the Simple URL option where there is a DNS host name for each supported SIP domain
for federation, and provide remote access to company users. This way, users can work with the
litwareinc.com domain, but you need to add extra DNS records.
If you need to support multiple SIP domains and if the list of supported DNS domains is changing on a
regular basis—for example, every six months—then, it is easier to use the Simple URL option where the
DNS host name stays the same. In this option, the DNS domain names stay the same on the reverse proxy.
You still need to change the Access Edge certificate.
The preceding examples only show the external records required. In the following example, only one SIP
domain is supported in the same environment.
In addition, you need some more internal DNS records, the first for the internal Edge interface and the
next for device time synchronization and device updates.
To support conferences internally, you need to use a split-brain DNS solution, including some records on
the same DNS zone that you publish externally. These are as follows.
DNS records are required for different services and you must have knowledge of these records. However,
considering the amount of DNS records required, it is an important part of your project to create a proper
design that not only includes all important aspects, but also a plan for maintaining the records required,
and decommissioning those records that are no longer required. The given example of 20 DNS records
only shows a simple design. If you deploy high availability and Directors with support for multiple SIP
domains, then your design would be more complex and will require thorough planning and maintenance.
Question: Can you provide some examples for how you record your DNS design?
MCT USE ONLY. STUDENT USE PROHIBITED
6-20 Designing and Deploying External Access
• All server certificates contain a Certificate Revocation List (CRL) Distribution Point (CDP).
• Auto-enrollment is supported for internal servers running Lync Server 2013.
• When you submit a web-based certificate request to a Windows Server 2003 CA, you must submit it
from a computer running either Windows Server 2003 with SP2, or Windows XP.
Note: Although KB922706 provides support for resolving issues with enrolling web
certificates against a Windows Server 2003 Certificate Services web enrolment, it does not make it
possible to use Windows Server 2008, Windows Vista, or Windows 7 to request a certificate from
a Windows Server 2003 CA.
• The default hash algorithm is RSA. The ECDH_P256, ECDH_P384, and ECDH_P521 hash algorithms are
also supported
During deployment, certificates have been one of the greatest challenges with the previous versions of
Lync Server 2013. Although, Lync Server 2013 helps get the certificate configuration right, because of its
built-in functionality, you need to consider the certificate requirements when designing Lync Server 2013
solutions.
Question: Can you use an external third-party certificate authority for all certificates in a
Lync Server 2013 deployment, thereby negating the requirement for an internal PKI
implementation?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-21
Subject Names
The Subject Name of a given X.509 certificate is
the primary name of the certificate. This is the
most basic type of certificate name used and is
supported by all PKIs and CA implementations,
including all commercial third-party certificate
authorities.
In a Lync Server 2013 implementation, the following places use certificates with SAN:
• Edge Servers (typically used for the Access Edge role). On the Edge Servers, the same certificate may be
used for more than one server role. The subject name may be used for web conferencing Edge as a
SAN with the Access Edge FQDN for each supported SIP domain.
• Front End servers and Directors. SAN certificates are used on the servers or pools that perform user
authentication. SAN certificates are used for the SIP connectivity.
Correlation between certificate subject name and the subject alternative names
Both subject names and SAN are correlated as some systems require that the first SAN in a certificate
should be the same as the subject name. Although this is not a requirement when using systems that are
fully compliant with SAN certificates, it is still considered a best practice for certificates.
Question: Is there a limit on the number of SAN entries that can be included in a certificate?
PKI considerations
In comparison to the Office Communication Server
2007 R2, Lync Server 2013 provides a smoother
process for requesting and applying certificates.
However, you need to consider the complexity
that is involved in designing, implementing,
MCT USE ONLY. STUDENT USE PROHIBITED
6-22 Designing and Deploying External Access
If you choose to deploy public certificates, you need to consider the following:
• CRL Download Locations. CRL download locations do not typically need further consideration because
they are handled by the public certificate provider. However, you need to ensure that all servers that
use public certificates are able to access the CRL download location URLs for these certificates. Also
ensure that the Edge Server can access CRL download URLs for the certificates presented by
federation partners.
• Root Certificate Support. You need to ensure that any public certificate provider that you use has its
root certificate included as standard with Windows clients. If the root certificate of the provider that
you use is not supported on Windows clients such as Windows 7, Windows Vista, or Windows XP, you
will need to import this root certificate to the clients, either as part of a deployment image, or by
using Group Policy.
You need to apply the same considerations for clients that will use mobile clients to access the Lync Server
2013 infrastructure. The way in which you import root certificates to mobile devices varies from platform
to platform. Therefore, you should either ensure that the devices you use trust the root certificates, or use
the method supported by the specific device or platform to import the relevant root certificates to that
device.
As new types and models of mobile devices and client operating systems are introduced, root certificate
support is an issue that will require ongoing planning and awareness.
If you choose to deploy private certificates that are preferably issued from a Windows Server Certificate
Authority for some purposes, you need to meet some requirements to ensure that the Lync Server 2013
environment functions as intended.
When a front-end server or Director Server communicates with the Edge Server, the latter will process the
certificate presented by the front-end server or Director Server. The Edge Server then attempts to retrieve
the CRL to determine if the certificate presented has been revoked by the issuing CA. If the Edge Server
fails to retrieve the CRL, it considers the certificate invalid, and communication does not proceed.
Therefore, in practice, you should publish both full and delta CRL to a web server URL, which the Edge
Server can access on its internal interface. You should then add this address to the list of CRL download
locations on the CA. You need to perform this task before requesting certificates for the Lync Server 2013
environment, because the CRL download location list is not updated for certificates that have already
been issued.
You should be aware of this critical issue when operating internal PKI, because an incorrectly configured
or poorly maintained PKI can pose major problems when deploying Lync Server 2013. In addition, the
need to troubleshoot certificate issues is a very common occurrence in many deployments and you need
to ensure that this does not become an issue in your deployment.
Although deploying a Windows Server Certificate Authority is a simple task with newer versions of
Windows Server, you cannot get a fully configured PKI that is immediately usable for Lync Server 2013 just
by deploying this server role. You need to properly design, configure, and maintain the PKI as per
Microsoft best practices or of other vendors, if deploying a non-Microsoft PKI.
• By default, install the root certificates of the providers in the client operating systems that will be
used. This is applicable for both computers and mobile devices.
• The provider supports SAN in X.509 certificates. The actual number of supported SANs in a given
certificate must be sufficient for your usage.
• The provider supports certificate key lengths of at least 2,048 bytes for higher security.
• Be cautious of providers who merely issue certificate authorities to the Root CAs of other providers.
Ideally, you need to use a CA that has full control of both their Root CAs and any intermediate or
issuing CAs in the certification path.
The cost of obtaining certificates can vary among providers because of various factors such as support
plans and certificate types. You should choose the provider whose services best suit the organizational
needs, while keeping the above points in mind.
Question: If you use federation in Lync Server 2013, can you federate with organizations that
use their own (private) certificates, instead of public certificates on their Access Edge Server
of either Office Communications Server or Lync Server 2013?
MCT USE ONLY. STUDENT USE PROHIBITED
6-24 Designing and Deploying External Access
As part of provisioning, the SBA gets a certificate installed on it, and this certificate is used for client
authentication when the client connects to register to the SBA. The SBA looks at the SIP domain part of
the SIP URI of the client attempting to register, and compares it to the installed certificate. If the domain
part of the SIP URI matches the domain that is present in the SBA certificate, either in the form of a
Canonical Name (CN) or SAN entry, the client is allowed to register to the SBA.
To ensure that the clients are registered, you should plan for all potential SIP domains to be listed in the
SBA certificate. A client might be refused registration if the SIP domain cannot be matched by the SBA
certificate. In addition, if you add additional SIP domains after deploying SBA, these may need to have
their certificates updated to include the new SIP domains.
Web services also require the use of certificates in Lync Server 2013. However, typically, this is covered by
the server certificate installed on each Lync front-end server.
Question: If you have a domain controller available in a remote location where clients are
signing in to an SBA, does this remove the reliance on certificates for client authentication?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 6-25
In this exercise you will add Edge server to the deployment with following configurations:
• Edge pool FQDN : lon-edge01.adatum.com
Results: After completing this exercise, you should have defined a new Edge Pool, defined internal and
external FQDNs and IP addresses, and then published the topology. You should have also exported the
configuration for Edge Server role deployment.
Once configured edit Global External access policy with following configuration:
• Enable federation
Review Question(s)
Question: What has changed regarding Public IM Connectivity User Subscription License?
Tools
Changes in Lync Server 2013 That Affect Edge Server Planning
http://go.microsoft.com/fwlink/?LinkId=282227
MCT USE ONLY. STUDENT USE PROHIBITED
7-1
Module7
Deploying Microsoft Lync Server 2013 Persistent Chat
Contents:
Module Overview 7-1
Module Overview
In any organization, employees need to interact with each other in the course of their work. This
interaction can be a one-to-one meeting or a meeting that involves several participants across many
locations. To ensure smooth interaction of employees in an organization, you need to plan, design, and
deploy Lync Server 2013 Persistent Chat in the enterprise.
Objectives
• Describe the features and concepts for Persistent Chat in Lync Server 2013.
• Design Lync Server 2013 to include Persistent Chat.
Lesson 1
Overview of Persistent Chat Architecture in Lync Server
2013
In Lync Server 2013, Persistent Chat Server enables you to participate in multiparty, topic-based
conversations that persist over time. You can use various components that are necessary to deploy
Persistent Chat within your Lync 2013 deployment.
Lesson Objectives
• Describe the Persistent Chat server.
• Improve information awareness. By using client-side filters, users can define conditions—such as
keywords in message content, or the value of the "from" field in a message—to receive notification
when those conditions are met in Persistent Chat instant messages or chat room messages. This way,
users can stay up-to-date with the content that interests them most.
• Improve communication with their extended organization. By making it easy to collaborate over long-
running topics with others in the organization, and by providing a persistent place to share
information, Persistent Chat helps improve communication.
• Reduce information overload. Users can follow chat rooms and messages of most interest by using
client-side filters, and they can add chat rooms that they want to follow, to their contact list.
• Increase dispersion of important knowledge and information. Documents and links can be included
within conversations for access by all the team members. By posting questions to a broader team,
users can benefit from responses by subject matter experts. Integration with other information
systems enables important organizational data to be easily communicated to large groups.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-3
• Multiple-Server Topology
You can add Persistent Chat Server to your Lync Server 2013 deployment by using Topology Builder. You
can add a single server or multiple servers to the Persistent Chat Server pool in your topology.
Single-Server Topology
The minimum configuration and simplest deployment for Persistent Chat Server is a single Persistent Chat
Server front-end server topology. This deployment requires a single server that runs Persistent Chat
(which, optionally, runs the Compliance service, if compliance is enabled). This server hosts both the SQL
Server database, and if compliance is required, the SQL Server database that stores the compliance data.
Multiple-Server Topology
To provide greater capacity and reliability, you can deploy a multiple-server topology. The multiple-server
topology can include as many as four active computers running Persistent Chat Server (high availability
and disaster recovery configurations will allow up to eight, but only four can be active and the remaining
four are standby). Each server can support as many as 20,000 concurrent users, for a total of 80,000
concurrent users connected to a Persistent Chat Server pool with four servers. A multiple-server topology
is the same as the single-server topology, except that multiple servers host Persistent Chat server, and can
scale higher. Multiple computers running Persistent Chat Server should reside in the same Active Directory
Domain Services (AD DS) domain as Lync Server and the Compliance service.
• If compliance is enabled, a server(s) that host the SQL Server back-end database for hosting the
Persistent Chat compliance database.
MCT USE ONLY. STUDENT USE PROHIBITED
7-4 Deploying Microsoft Lync Server 2013 Persistent Chat
Each computer that hosts the Persistent Chat Server must have access to an existing Lync Server 2013
topology, which includes a Lync Server 2013, front-end server. The front-end server is the foundation for
Session Initiation Protocol (SIP) routing, which makes communication between computers running
Persistent Chat Server and the Persistent Chat functionality possible. Before you begin to deploy Persistent
Chat Server, verify the deployment of Lync Server 2013, Standard Edition, or a Lync Server front-end pool
and any other internal computers running Lync Server, as appropriate to your organization.
The Persistent Chat Server uses the Persistent Chat database to store chat history, configuration, and user
provisioning data. Optionally, it uses the Persistent Chat compliance database to store compliance data.
Note: The Persistent Chat database (mgc) and the compliance database (mgccomp) can be
located in the same instance of SQL Server or on different SQL Servers.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-5
Lesson 2
Designing Lync Server 2013 Persistent Chat
Designing your Persistent Chat deployment properly for your organization is as important as any other
Lync 2013 system. You need to ensure that organizational productivity is not adversely affected. In
addition, you must ensure compliance with legal requirements and standards. To design a Persistent Chat
deployment, you should be familiar with the elements in a Persistent Chat infrastructure.
Lesson Objectives
• Define the organization’s requirements for Persistent Chat Server.
Organizational Requirements
Before you deploy the Persistent Chat Server for
your organization, you must consider the
following key questions to optimize your
deployment:
1. Who (user profile) should be enabled for
Persistent Chat server? Persistent Chat Server
is enabled by a policy that can be set at a
global, site, pool or user level.
2. How many users (scale) should be enabled for
Persistent Chat Server? Persistent Chat Server
supports 150,000 provisioned users (enabled
by policy), and a maximum of 80,000
concurrent users of the Persistent Chat Server. A single Persistent Chat Server can support 20,000
connected users, and a single Persistent Chat Server pool can have up to four active servers for a total
of 80,000 concurrently connected users.
3. Are you migrating from a previous version of Group Chat Server, or are you deploying Persistent Chat
Server for the first time?
4. Are there compliance requirements? Persistent Chat Server supports compliance. The compliance
service runs collocated on the Persistent Chat Server front-end server, as opposed to the requirement
for a separate computer in previous Group Chat Server deployments. Compliance is optional, and if
chosen, requires a compliance database that must be configured to store compliance data and
events. You may also want to configure an adapter to take the data from the compliance database
and convert it to another format (such as XML files or Exchange-hosted archives).
5. How do you want to control scopes, ethical boundaries, and access? You can define categories to
segregate these boundaries, and choose who is allowed to be in rooms that are created in each of
these categories.
6. How do you want to control who can create rooms? You can configure creators, appropriate to your
categories, who can create rooms. Creators can assign other members as Chat Room Managers for
ongoing management of the rooms (adding or removing additional members), according to the
scope for AllowedMembers/DeniedMembers configured by the category.
MCT USE ONLY. STUDENT USE PROHIBITED
7-6 Deploying Microsoft Lync Server 2013 Persistent Chat
7. How do you want to create rooms? Persistent Chat Server provides a web-based feature for creating
and managing rooms, from the Lync 2013 client. You can choose to define a custom solution (by
using the Persistent Chat Server Software Development Kit (SDK)) that implements your business
requirements and workflows, and configures Persistent Chat Server to direct users to your custom
solution.
8. What kind of add-ins do you want to provision? Add-ins enhance the in-room experience by taking
advantage of the extensibility pane in the Lync 2013 client to provide context that is relevant to the
room. You can choose what general add-ins might be most useful (for example, your company
website, internal collaboration documents, and so on). Chat room managers can choose one of the
registered add-ins and associate it with their rooms, if required.
9. What kind of high availability and disaster recovery requirements do you have? Persistent Chat Server
supports SQL Server mirroring for high availability and supports up to eight servers (four active and
four standby) in a stretched pool with SQL Server log shipping for disaster recovery.
10. Are there regulatory requirements? If your company is in a country/region where data needs to be
kept globally, you may need to deploy multiple Persistent Chat Server pools, each local to a specific
geography. A room, category, or add-in does not span pools—it belongs to only one Persistent Chat
Server pool. Users can be configured to have access to rooms in one or more pools, depending on
how you design your categories.
Server Infrastructure
In Lync Server 2013, Persistent Chat Server is part
of the Lync Server 2013 infrastructure.
Persistent Chat Server is available with Lync Server
2013 Enterprise Edition as a separate pool (not
collocated with the Enterprise Edition front-end
servers). Persistent Chat Server requires a SQL
Server back-end server in your Enterprise Edition
pool to store the chat room content and other
relevant metadata. We recommend that you install
the PersistentChatStore on a dedicated SQL Server
back-end server, although collocating Lync Server
2013 back-end server and PersistentChatStore on
the same SQL Server instance is supported.
Persistent Chat Server can be deployed with Lync Server 2013 Standard Edition. In this case, the
PersistentChatService front-end server is collocated on the Standard Edition computer, and the
PersistentChatStore back-end server can be deployed on the local SQL Server Express instance.
Note: We do not support high availability for Persistent Chat Server Standard Edition.
Performance and scale will be limited. Furthermore, we support only new Persistent Chat Server
Standard Edition servers. We do not support upgrading Lync Server 2010, Group Chat Server to a
Lync Server 2013 Persistent Chat Server Standard Edition.
If your organization requires compliance support, you can enable the Persistent Chat Server Compliance
service on the Persistent Chat Server front-end server. A separate database is required for compliance. At
a minimum, each topology requires a server with Lync Server 2013 installed and a server with SQL Server
database software installed.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-7
The Persistent Chat Server front-end server, PersistentChatService, can be deployed on one or more
stand-alone computers in a Lync Server 2013 Enterprise Edition pool. They cannot be collocated on the
Lync Server Enterprise Edition front-end servers. Persistent Chat Server can be deployed by the
Bootstrapper, just like other Lync Server roles. The Persistent Chat Web Services for File Upload/Download
and Persistent Chat Web Services for Chat Room Management are web components deployed on the
Lync Server 2013 front-end servers.
A single Persistent Chat Server front-end server can support 20,000 active users. You can have a Persistent
Chat Server pool with up to four active front-ends supporting a total of 80,000 concurrent users. The
Persistent Chat back-end server, PersistentChatStore, stores the chat rooms and categories. We
recommend that you install the PersistentChatStore on a dedicated SQL Server back-end server in your
Enterprise Edition pool; although we support collocating Lync Server 2013 back-end server and
PersistentChatStore on the same SQL Server instance.
• Create a variety of add-ins that help enhance the experience of chat rooms by bringing in other
business data into chat rooms. Administrators must register the add-ins that they want to allow in the
system. Chat room managers and creators can choose from the list of allowed add-ins for the ones
most relevant to their respective rooms.
and chat room managers/creators have to associate rooms with one of the registered add-ins before users
can see this upgrade in their Lync 2013 client.
Add-ins are used to extend the in-room experience. A typical add-in might include a URL pointing to a
Silverlight application that intercepts when a stock ticker is posted to a chat room, and shows the stock
history in the extensibility pane. Other examples include embedding an OneNote 2013 URL in the chat
room as an add-in to include some shared context, such as "Top of mind" or "Topic of the day."
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-9
Lesson 3
Deploying and Configuring Lync Server 2013 Persistent
Chat
After you have designed and planned Persistent Chat in your Lync 2013 system, you can deploy it and set
up the chat room. You should be familiar with the deployment process and the tool used to configure
and manage chat rooms.
Lesson Objectives
• Deploy a Persistent Chat Server infrastructure.
for Persistent Chat Server by policy, then the Persistent Chat Server environment appears in that user’s
Lync 2013 client.
Note: In the topology, Persistent Chat Server site policies apply globally, per user’s pool, or
per user’s site, or per user.
To make changes to an existing Persistent Chat Server room use the following:
Persistent Chat Server enables users to collaborate by posting messages into Persistent Chat rooms. The
data is persisted on the server, and members of the room have access to the data, including historical
data. However, users with different roles have different access to the persisted data.
When a message is deleted, you cannot undo the action. However, deleted messages can be restored if
there is a backup. If a Persistent Chat Compliance server is enabled, old messages are persisted in the
compliance database.
Note: This chat room data usage applies to the Lync Server 2013, Persistent Chat Server API
application, except for the case when the administrator role is involved. The Persistent Chat Server API
cannot be used to perform any of the administrator’s operations. You must perform these operations in
the Lync Server Management Shell.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-11
• Enable Compliance
Results: After completing this exercise, you should have published the persistent Chat pool to the
topology.
2. Set up components.
• Enable user : Allie Bellew for Lync and make her part of lon-pool.adatum.com
• Description : this is the war room for the sales team of Adatum
• Members : try and add both “Allie Bellew” and “Dan Park”
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 7-13
1. Enable users.
Task 3: Create the Persistent Chat room for the Sales employees.
Create the Persistent Chat Room for Sales
MCT USE ONLY. STUDENT USE PROHIBITED
7-14 Deploying Microsoft Lync Server 2013 Persistent Chat
Persistent Chat Server supports a stretched pool architecture that enables a single Persistent Chat
Server pool to be stretched across two sites. It is important to remember here that SQL Server
mirroring is used to provide high availability for the Persistent Chat Server content database and
Persistent Chat compliance database within a data center (same location), and that SQL Server
Log Shipping is used for cross-site disaster recovery.
Review Question(s)
Question: What additional software is required for Persistent Chat front-end servers?
Question: Does Lync Server 2013 allow for chat rooms to have contacts outside the
immediate organization to join in and participate in the room?
While Lync 2013 clients can be used against a Lync Server 2010 pool, they cannot be used against Lync
Server 2010, Group Chat. If you roll out the Lync 2013 client first during a migration, you need to leave
the Lync 2010 Group Chat client installed because Lync 2013 clients are not compatible with Lync Server
2010, Group Chat.
Additionally, the Lync 2013 client does not support the file transfer feature in Persistent Chat. You will
need to use the legacy Group Chat client to take advantage of the file transfer feature in Lync Server 2013
Persistent Chat.
MCT USE ONLY. STUDENT USE PROHIBITED
8-1
Module8
Monitoring and Archiving
Contents:
Module Overview 8-1
Lab: Configuring and Using Archiving and Monitoring in Lync Server 2013 8-16
Module Review and Takeaways 8-19
Module Overview
In Microsoft® Lync® Server 2013, the Archiving service provides a solution for archiving the content of
instant messages (IM) and web conferencing communications in support of your compliance
requirements.
The Monitoring service collects numerical data about the quality of calls on your network, and details
about participants, device names, drivers, IP addresses, and endpoint types involved in calls and sessions.
This Quality of Experience (QoE) data enables you to monitor the quality of real sessions and perform
troubleshooting in response to end-user issues. In addition, these types of call detail statistics are useful
for monitoring usage trends and calculating your organization’s overall return on investment (ROI).
You should, therefore, know about the features and configuration of both the Monitoring and Archiving
services. In addition, you should know how to interpret the QoE reports and use this information to better
manage and deliver high-quality user experience for Lync Server 2013.
Objectives
• Describe the Archiving service.
• Describe the Monitoring service.
Lesson 1
The Archiving Service
Corporations and other organizations are subject to an increasing number of industry and government
regulations that require the retention of specific types of communications. With the Archiving server
feature, Lync Server 2013 provides a way for you to archive IM content, web conferencing (meeting)
content, or both that are sent through Lync Server 2013. The Archiving service provides various
components that you can use to archive meeting content. To do this, you should be aware of the process
for configuring the Archiving service and the capabilities offered by the Archiving server role.
Lesson Objectives
• List the features and components of the Archiving service.
• Explain IM archiving.
• Describe conferencing compliance in Lync Server 2013.
Features
The new archiving features in Lync Server 2013
include:
• Collocation on front-end servers. In previous
versions of Microsoft Lync Server, the
Archiving Role was deployed as a separate
Archiving Server Role. In Lync Server 2013,
Archiving is an optional feature available on all Front End Servers.
• Exchange integration option. Data storage for Archiving can be integrated into Exchange Server 2013
for all users who have mailboxes on Exchange 2013 and have their mailboxes put on In-Place Hold.
This removes the need to deploy separate SQL databases for archiving.
• Searchable transcript of archived information. Data archived to Exchange 2013 is searchable and
discoverable. If Exchange 2013 integration is not used, Lync Server 2013 provides a session export
option that you can use by running the Lync Server 2013 cmdlet Export-CsArchivingData.
• SQL store mirroring. If Exchange 2013 integration is not being used, Lync Server 2013 Archiving will
use SQL databases, and includes the ability to provide availability for the archiving SQL databases by
using SQL mirroring. This is an optional topology in which you deploy two Back End Servers for a
Front End pool, and set up synchronous SQL mirroring for all the Lync databases running on the Back
End Servers. SQL Mirroring will be discussed in detail later in this module.
Components
The Archiving service includes the following three components:
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 8-3
• Unified data collection agents. The agents are responsible for capturing the messages to be archived.
These agents are installed and activated automatically on every front-end pool and Standard Edition
server. However, no messages are captured unless archiving is enabled and appropriately configured.
Archiving can be enabled at the global level, site level, or for specific users.
• Archiving data storage. Archived data can be stored in the following locations:
o Exchange Server 2013 storage. When Exchange integration is enabled, user mailboxes placed on
Exchange Server 2013 use the user’s Exchange Mailbox for data storage, but only if the mailboxes
have been put on In-Place Hold.
o SQL Server storage. When users mailboxes are saved on Lync Server 2013, and Exchange 2013
integration is not enabled (or desired), archiving data is stored in a SQL database.
IM Archiving
If you deploy Archiving, you can set it to archive
instant messages and conferences, and specify the
users for whom archiving is enabled.
When you deploy Archiving, a global policy is
created by default. You can use the global policy
to enable archiving of internal communications
(communications between internal users) and
external communications (communications that
include at least one external user). You can also
specify the users for whom archiving is enabled by
creating policies for specific users or sites.
If Exchange Server 2013 integration is configured, you can control archiving for the user by configuring an
In-Place Hold on the user’s mailbox in Exchange. Additional control is available by using the following
cmdlet. ExchangeArchivingPolicy parameter of Set-CsUser
Conferencing Compliance
Lync Server 2013 consolidates conferencing
compliance storage and management to make it
easier for you to administer. In Lync Server 2013:
When you enable archiving for a particular user, all instant messages and meeting content in both IM
conferences and web conferences that the user participates in, are archived.
Group conferences are archived if one of the following policies is configured to enable archiving:
• At least one of the participants has a user policy configured to require archiving.
• The global policy or site policy is configured to enable archiving of all group conferencing.
• Content of web conferences, including uploaded content (such as handouts) and events (such as
joining, leaving, uploading, sharing, and changing visibility)
• Whiteboards and polls shared during a conference
Note: You can record A/V or application sharing or both in the Lync 2013 client.
Archiving Configuration
You can control the configuration of archiving for
your organization by configuring policies at three
levels:
• Global
• Site
• Pool (Service)
For each archiving configuration, you can specify
whether archiving is enabled, whether to archive
IM, or IM and web conferencing, enable exchange
integration, and configure purging.
• Site
• User
For each archiving policy, you can specify whether
to archive only IM sessions or to archive both IM
and conferencing sessions.
The global policy can specify that instant messages from all multiparty conferences are archived, even if
you have set archiving policies for specified users and sites.
Note: By default, archiving is not enabled for either internal communications or external
communications. Also, the global policy cannot be deleted.
For example, to disable archiving support for specific users at a site, you can:
• Set the global archiving policy to not archive internal and external communications.
• Create a site policy for the site to enable archiving for the site.
MCT USE ONLY. STUDENT USE PROHIBITED
8-6 Monitoring and Archiving
• Create a user policy that disables archiving support for the users.
If you create both site and user policies, user policies override site policies.
Exchange Archiving
Additionally, you can configure Exchange 2013 integration for Archiving. When Exchange 2013
integration is configured, and the user’s mailbox is located on an Exchange 2013 Mailbox Server, the value
for ExchangeArchivingPolicy determines how Lync will handle archiving.
You can choose to enable or disable archiving support for specific users by using the Set-CsUser cmdlet,
setting the –ExchangeArchivingPolicy parameter to:
Uninitialized. Indicates that archiving will be based on the In-Place Hold settings configured for the user's
Exchange mailbox. If In-Place Hold has not been enabled on the user's mailbox, the user will have his or
her messaging and web conferencing transcripts archived in Lync Server.
UseLyncArchivingPolicy. Indicates that the user's instant messaging and web conferencing transcripts
should be archived in Lync Server, rather than in Exchange.
NoArchiving. Indicates that the user's instant messaging and web conferencing transcripts should not be
archived at all. Note that this setting overrides any Lync Server archiving policies assigned to the user.
ArchivingToExchange. Indicates that the user's instant messaging and web conferencing transcripts should
be archived to Exchange, regardless of the In-Place Hold settings that have (or have not) been assigned to
the user's mailbox.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 8-7
Lesson 2
The Monitoring Service
In Lync Server 2013, the Monitoring service collects performance metrics and provides you with reporting
capabilities to help ensure the quality of your Lync Server 2013 communications system. You can use the
Quality of Experience (QoE) and Call Detail Records (CDR) features and the capabilities offered by the
Monitoring service.
Lesson Objectives
• List the features and components of the Monitoring service.
• IM messages
• A/V conversations
• Meetings
• Application sharing
• File transfers
Components
The Monitoring service is collocated on the existing front-end servers, and includes the following four
components:
• Unified data collection agents. The CDR and QoE agents are installed automatically on every front-end
server.
• Monitoring databases. To store and collect data, the Monitoring service requires databases that use
SQL Server. The databases can be collocated on the back-end SQL instance, or on a different
computer. Separate databases are required for CDR and QoE information. They both always run on
the same instance of SQL Server.
• Microsoft Systems Center Operations Manager (SCOM) Management Pack. This is an optional
component. The Call Reliability and Media Quality Monitoring component of SCOM use Monitoring
server CDR and QoE data to generate near real-time alerts showing the health of call reliability and
media quality.
MCT USE ONLY. STUDENT USE PROHIBITED
8-8 Monitoring and Archiving
• Monitoring Server Reports. This is also an optional component. It contains out-of-the-box reports on
usage, call diagnostic information, and media quality information based on the data stored in the
CDR and QoE databases. The reports are generated by using SQL Server Reporting Services.
Supported Topologies
Each Monitoring database can capture data from one or more Enterprise Edition pools, and Standard
Edition servers.
The only real requirement with SQL Server instances is that any one instance of SQL Server is limited to
the following:
• One instance of the Lync Server 2013 back-end database. (As a general rule, we do not recommend
that your monitoring database be collocated in the same SQL instance, or even on the same
computer, as the back-end database. Although technically possible, you run the risk of the
monitoring database using up disk space needed by the back-end database.)
QoE
QoE records not only capture numerical data
about the quality of calls on your network, but
also capture information about participants, device
names, drivers, IP addresses, and endpoint types
involved in calls and sessions. These quality metrics
are collected at the end of every VoIP call and every video call from the participant endpoints, including
IP phones, Lync Server 2013, some legacy clients, and A/V conferencing servers and Mediation Servers. For
Mediation Servers, metrics are gathered from both the path between the Mediation server and UC
endpoints, and the path between the Mediation Server and the media gateway.
You can run the following query against the QoEMetrics database to get jitter and packet loss average for
all audio streams.
CDR
CDRs capture usage information related to VoIP calls, IM messages, A/V conversations, meetings, file
transfers, application sharing, and remote assistance.
Note: The actual content of IM messages is not captured in CDR data. To preserve IM
content for compliance reasons, use the Archiving server feature.
CDR data is frequently used for billing purposes and is therefore very important in many deployments. In
Lync Server 2013, CDR data is captured for both peer-to-peer and multiparty conferences.
The CDR database in Lync Server 2013 includes new usage and diagnostic data for Lync Server 2013
features, including conferencing, registration, and device diagnostics. There is also comprehensive data for
usage tracking and voice-quality diagnostics.
For example, using SQL Server Management Studio, you can run the following query against the LcsCDR
database to find the total number of public switched telephone networks (PSTNs) to Unified
Communications (UC) calls.
You must install the Monitoring server reports on the instance of SQL Server running the Reporting
Services.
Lync Server 2013 supports the following 64-bit versions of SQL Server:
• Standard or Enterprise Edition of SQL Server 2008 R2. Latest service pack is recommended.
• Standard or Enterprise Edition of SQL Server 2012. Latest service pack is recommended.
MCT USE ONLY. STUDENT USE PROHIBITED
8-10 Monitoring and Archiving
3. On the web services URL page, click the URLs listed under Report Server Web Service URLs to verify
that the link can be opened.
You deploy Monitoring server reports to this link. You are given the option to use either HTTP or HTTPS
to deploy the reports. If both are available, Reporting Services is installed to HTTPS.
• Click the Call Detail Recording tab to enable or disable Call Detail Recording and configure Call
Detail Recording purging settings.
• Click the QoE Data tab to enable or disable QoE and configure QoE purging settings (as seen on the
slide).
Lesson 3
Configuring Archiving and Monitoring
To enable archiving of IM and web conferencing content that is sent through Lync Server 2013, you must
add Archiving to the topology and publish the new topology. To enable CDR and QoE data collection and
reporting, you must add Monitoring to the topology and publish the new topology.
You can perform specific steps to implement the Archiving and Monitoring service for Lync Server 2013.
Lesson Objectives
• Identify the steps for implementing the Archiving service.
Scope
You can specify policies to control the archiving of
specific content at the global, site, and user levels.
Your scope should include which policies are
required, whether archiving is to be enabled for
internal communications, external
communications, or both, and which workloads are to be archived.
Critical Mode
You can specify that the Archiving configuration should run in critical mode if archiving is mission-critical
in your organization. In critical mode, if instant messages and conferencing content cannot be archived,
Lync Server 2013 blocks specific functionality. For example:
• If the Archiving service is temporarily unable to send a message to the Lync Storage Service, IM
functionality is blocked until archiving support is restored.
• If a web conferencing user uploads a file, but the file cannot be copied to the Archiving file store, all
active conferences hosted in the pool are switched to restricted mode, and new conferences cannot
be activated.
The blocking of IM and conferencing does not affect any other Lync Server 2013 feature and functionality
because it is primarily intended to ensure that compliance requirements are met.
Lync Server 2013 provides a session export tool that you can use to export archived data and create
searchable transcripts of the archived data. The Lync Server 2013 Data Session Export Tool can create
searchable transcripts of archived data. The session export tool can be used to:
• Create transcripts from archived data such as multi-part email messages as a multi-part MIME
formatted Microsoft Office Outlook® Express Electronic Mail (EML) format .eml file. The content
consists of the IM or conference transcript, the conference activity file (as an attachment), and
uploaded conference files, including handouts (as attachments). Transcripts can be created for all
users or specific users.
The Data Session Export Tool creates a single transcript for each completed communications session that
occurred within the specified date range.
To run the Data Session Export Tool, you use the following Lync Server 2013 cmdlet.
Purge Mode
You can specify if archiving data should be purged. By default, purging is not enabled. If you enable
archiving data purge mode, you must specify one of the following options:
• Purge archiving data after a specific number of days, regardless of whether it has been exported. The
minimum number of days is 1, the maximum is 2,562 days.
• Purge archiving data only after it is exported (which also includes data that has been uploaded to
Exchange). This option purges those records that have been exported by the session export tool and
marked as safe to delete.
You configure purge settings by using the Archiving Configuration tab in Lync Server Control Panel.
If Exchange integration is enabled, purging is controlled by Exchange for users who have mailboxes stored
on Exchange 2013 Mailbox Servers and put on In-Place Hold. The exception is for conferencing files,
which are stored in the Lync File Share.
If Exchange 2013 integration is being used, server-to-server authentication must be configured. Prior to
configuring server-to-server authentication, you must assign appropriate certificates to each server, and
configure each server to be a partner application of the other server.
To configure Lync Server 2013 to be a partner application for Exchange Server 2013, use the Configure-
EnterprisePartnerApplication.ps1 PowerShell script, which is provided with Exchange Server 2013.
To configure Exchange Server 2013 to be a partner application for Lync Server 2013, use the New-
CsPartnerApplication cmdlet in Lync Management Shell.
The configuration in the site policy overrides the global policy, but only for that specific site covered by
the site policy. For example, if you enable archiving of internal and external communications in the global
policy, you might specify a site policy that disables archiving for internal communications, external
communications, or both, for that one site.
Note: You cannot delete the global policy. If you attempt to delete it, the configuration
resets to the default value.
You can create an archiving policy to control whether archiving for specific users is enabled or disabled
for internal communications, external communications, or both.
The configuration in the user policy overrides the global policy and site policies, but only for the specific
users covered by the user policy. For example, if you enable archiving of internal and external
communications in the global policy, you might specify a site policy that disables it for internal
communications, external communications, or both for that one site. You may then specify a user policy
that enables archiving for a specific group of users at that site.
For example, to configure a user account so that instant messaging and web conferencing transcripts are
always archived to Exchange, you can use a command similar to the following code example.
Step 1: Install SQL Server and Microsoft SQL Server Reporting Services
SQL Server is required for the Monitoring service to store the collected QoE and CDR data. Monitoring
server describes this data by using a standard set of reports published by SQL Server Reporting Services.
To view these reports, you must install an instance of SQL Server Reporting Services.
Install SQL Server on the computer that will host the Monitoring server database. This can be a dedicated
database server, or it can be collocated on the same SQL instance used for the Enterprise Edition front-
end pool.
You should install the same versions of SQL Server Reporting Services and SQL Server.
For more information about SQL Server, see the SQL Server Tech Center at:
http://go.microsoft.com/fwlink/?LinkId=129045
For more information about SQL Server Reporting Services, see “Install Reporting Services
Native Mode Report Server (SSRS)” at:
http://go.microsoft.com/fwlink/?LinkId=275645
You can configure the reporting service while installing the SQL Server Reporting Services, or you can use
the Reporting Services Configuration Tool to configure the Report server after installation is complete.
For more information about configuring the Reporting Services, see “Reporting Services
Configuration Manager” at:
http://go.microsoft.com/fwlink/?LinkId=204090
For more information about how to configure Reporting Services, click this link:
http://go.microsoft.com/fwlink/?LinkId=187488
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 8-15
For more information about how verify Reporting Services installation, see “How to: Verify a
Reporting Services Installation” at:
http://go.microsoft.com/fwlink/?LinkId=187490
Data Purge
By default, both CDR data and QoE data are
purged after 60 days. You can specify whether you want to retain the data for a longer or shorter period
of time. If you disable either CDR or QoE, data that was captured while CDR or QoE was enabled will also
be subject to purging.
Note: You should configure CDR and QoE to retain data for the same number of days. Each
call in the Call Detail Reports, available from the Monitoring Server reports home page, includes
CDR and QoE information. If the purging duration for CDR and QoE is different, some calls may
only include CDR data, while others may only include QoE data.
MCT USE ONLY. STUDENT USE PROHIBITED
8-16 Monitoring and Archiving
Lab Setup
Estimated Time: 80 minutes
Important We recommend that the steps in this and every lab be split between the two students in your
pod. The students can determine when to share tasks so that both students gain an understanding of the
concepts of each lab. If you need help, please inform the instructor. Please note that if you both try to do
tasks at the same time, you may overwrite each other’s work and possibly lose data.
4. Configure Exchange Server 2013 to be a partner application for Lync Server 2013.
5. Configure Lync Server 2013 to use Exchange Server 2013 for archiving.
6. Generate traffic to be archived.
Task 3: Configure Lync Server 2013 to be a partner application for Exchange Server
2013.
Configure Lync Server 2013 to be a Partner Application for Exchange Server 2013.
Task 4: Configure Exchange Server 2013 to be a partner application for Lync Server
2013.
Configure Exchange Server 2013 to be a Partner Application for Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 8-17
Task 5: Configure Lync Server 2013 to use Exchange Server 2013 for archiving.
Configure Lync Server 2013 to use Exchange Server 2013 for archiving.
Results: After completing this exercise, you should have configured archiving settings, including polices,
configurations and Exchange integration for Adatum. You should also have generated some IM and web
conferencing traffic to be archived. Finally, you will have viewed the archived data by using Exchange
Control Panel.
Exercise 2: Configuring the Monitoring Server Role and the Lync Server
Monitoring Reports
Scenario
In this exercise you will be enabling the Monitoring server role and Monitoring Reports in your Lync
deployment with backend SQL lon-sql02.adatum.com and Named Instance: LYNC
Results: After completing this exercise, you should have defined Monitoring in the Topology, and
successfully published the changes. Then, you should have deployed the Lync Server Monitoring Reports.
Task 2: Connect to Lync Server Monitoring Reports and review the Dashboard.
Connect to Lync Server Monitoring Reports and review the Dashboard.
Results: After completing this exercise, you should have reviewed the collected CDR and QoE data
displayed on the Dashboard. You should have also reviewed several reports from each of the four
categories of reports, including manipulating the data displayed and understanding how to export the
reports to different formats.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 8-19
Consider the following scenario. An organization wants migrate from a legacy Lync version where
archiving compliance is required. The organization plans to migrate to Exchange 2013 and have
Exchange legacy compliance enabled. In such a scenario, you should consider configuring and
enabling both Archiving to Exchange 2013 and to Lync Server 2013, to maintain compliance
requirements. After the migration of users is complete to both Exchange Server 2013 and Lync
Server 2013, you should then disable Lync Server 2013 Archiving.
We recommend that you deploy Monitoring and Monitoring Server Reports, especially when you
deploy Enterprise Voice, because the monitoring data and reports are valuable in
troubleshooting call quality issues.
Review Question(s)
Question: In Lync Server 2013, which server roles are no longer separate roles, but are now
product features?
Question: Can multiple central sites share Archiving or Monitoring that has been deployed
in only one central site?
2. When Exchange and Lync Server are located in different forests, you must configure the
ExchangeArchivingPolicy property for each user by using Set-CsUser.
MCT USE ONLY. STUDENT USE PROHIBITED
8-20 Monitoring and Archiving
MCT USE ONLY. STUDENT USE PROHIBITED
9-1
Module9
Administration and Maintenance of Lync Server 2013
Contents:
Module Overview 9-1
Lesson 4: Introduction to analyzing Lync Server 2013 logs and traces 9-22
Lab: Administration and Maintenance of Lync Server 2013 9-26
Module Review and Takeaways 9-29
Module Overview
Lync Server 2013 provides various administration tools and operational best practices needed to maintain
Lync Server 2013 in the enterprise. You can also use a number of basic techniques and tools when
troubleshooting Lync Server 2013.
Objectives
• Describe and use the Lync Server 2013 troubleshooting tools.
• Describe the daily, weekly, and monthly maintenance tasks.
Lesson 1
Introduction to Lync Server 2013 troubleshooting tools
Before you embark on the tasks needed to maintain Lync Server 2013, you must become familiar with the
administrative tool that Lync Server 2013 offers.
Lesson Objectives
• Describe the capabilities of the Lync Server Deployment Wizard.
Download Windows Installer 4.5 from the Microsoft Download Center at:
http://go.microsoft.com/fwlink/p/?linkid=197395
Ensure that you review the infrastructure, operating system, software, and administrator rights
requirements before you install or use the Lync Server 2013 administrative tools.
Note: If your organization requires that you locate Internet Information Services (IIS) and
all web services on a drive other than the system drive, you can change the installation location
path for the Lync Server files in the Setup dialog box. If you install the Setup files to this path,
including OCSCore.msi, the rest of the Lync Server 2013 files will be deployed to this drive also.
3. If you are prompted to install the Microsoft Visual C++ 2008 distributable, click Yes.
4. On the Microsoft Lync Server 2013 Installation Location page, click OK. Change the path to another
location or drive if you need to have the files installed to another location.
5. On the End User License Agreement page, review the license terms, click I accept, and then click
OK. This step is required before you can continue.
6. On the Microsoft Lync Server 2013 – Deployment Wizard page, click Install Administrator Tools.
Publishing. Each time you use Topology Builder to build your topology, you must publish the topology to
a database in the Central Management Store (CMS) so that the data can be used for deployment of Lync
Server servers. Use the following procedure to publish your topology:
5. When the status indicates that database creation succeeded, do the following:
Certificates. A task that Administrators will face is the process of creating, installing, and assigning
certificates to internal pool servers. If you need to make changes to your topology after your initial
deployment (for example, to add a server to your topology), you must run Topology Builder to make the
changes. Then, publish the topology again, prior to deploying the new component in your topology. Use
the following procedure to open Topology Builder to make changes to your topology.
Note: You can define a topology by using an account that is a member of the local users
group, but to read, publish, or enable a topology, which is required to install a Lync Server 2013
server, you must use an account that is a member of the Domain Admins group and the
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-5
RTCUniversalServerAdmins group. This account must have full control permissions (that is,
read, write, and modify) on the file share that you are going to use for the archiving file store.
This will enable the Topology Builder to configure the required discretionary access control list
(DACL), or an account with equivalent user rights.
2. Start Topology Builder. Click Start, click All Programs, click Microsoft Lync Server 2013, and then click
Lync Server Topology Builder.
2. Start Topology Builder. Click Start, click All Programs, click Microsoft Lync Server 2013, and then click
Lync Server Topology Builder.
• Users
• Clients
• Devices
• Security
• Persistent Chat
• Enterprise Voice
• Conferencing
• Network Configuration
• Topology
Lync Server Control Panel is automatically installed on every Lync Server front-end server or Standard
Edition server. In Lync 2013, you administer Edge Servers remotely. You can also install Lync Server
Control Panel on another computer, such as a management console from which you want to centrally
manage Lync Server.
Note: To configure settings by using Lync Server Control Panel, you must be logged on by
using an account that is assigned to the CsAdministrator role.
To configure settings by using Lync Server Control Panel, you must also use a computer with a minimum
screen resolution of 1,024 x 768.
• Proactively check and verify that the configuration is set according to recommended best practices
• Generate a list of issues, such as sub-optimal configuration settings, unsupported options, missing
updates, or practices that we do not recommend
• AlwaysOn
• MediaConnectivity
• ApplicationSharing
• AudioVideoConferencingIssue
• HybridVoice
• IncomingAndOutgoingCall
• VoiceMail
• IMAndPresence
• AddressBook
• DeviceUpdate
• LYSSAndUCS
• CLS
• SP
• WAC
MCT USE ONLY. STUDENT USE PROHIBITED
9-8 Administration and Maintenance of Lync Server 2013
• UserReplicator
• HostedMigration
• MonitoringAndArchiving
• LILRLegacy
• LILRLYSS
• MeetingJoin
• RGS
• CPS
• XMPP
• CAA
The AlwaysOn scenario is special. CLS is designed to have that scenario running by default. This way, when
an issue occurs, you do not have to turn on logging, reproduce the issue and then view your logs. The
expectation is that there is enough logging occurring with AlwaysOn; so when an issue occurs, you will
already have the logs available. If AlwaysOn does not provide you with enough logs, you can turn on a
particular scenario to get a more detailed set of logs.
CLS is implemented by agents and a controller used by the Lync Administrator to interact with CLS.
The Lync Server Centralized Logging Service Agent service (also known as ClsAgent) runs on all Lync 2013
Preview servers in the deployment. The purpose of the agent is to respond to requests to enable/disable
logging, and to respond to search requests.
The Lync Administrator controls the agents through the ClsController interface. ClsController is a program
default installed into C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent. You can
specify different parameters to ClsController, and you can see detailed usage information about
parameters and their values by just running ClsController without parameters.
The typical sequence of commands that you want to run are as follows.
For example, to investigate an issue with UCS for a user on the lync.contoso.com pool, you can run the
following commands.
The last invocation of ClsController will write the resulting log entries to standard output, so you might
want to re-direct it to a file by using >.
You can get an understanding of which components are included in which CLS scenarios by using the
following Lync Management Shell command.
Get-CsClsScenario
To find the components or providers in the CPS scenario, you can use the following commands:
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-9
• Automatic parsing of event messages described by Event Tracing for Windows (ETW) manifests
• Summarized grid display–top level is “operations” (requests matched with responses)
• Ability to browse for logs of different types (.cap, .etl, .txt), and import them together
• Ability to import text logs, and parse them into key element/value pairs
• Support for “Trace Scenarios” (one or more message providers, filters, and views)
MCT USE ONLY. STUDENT USE PROHIBITED
9-10 Administration and Maintenance of Lync Server 2013
To use the tool, you must first specify the test method:
• Test remote client connectivity to Office Communications Server by specifying the FQDN of the
Access Edge Server and the port.
• Test remote client connectivity to Office Communications Server by using auto-discovery to find the
Access Edge Server and port to which to connect.
After you select one of the two test methods you want to use for the test, you specify the required
information, including the user account to be used in the test. Then, the application attempts to connect
to the Access Edge Server and complete the following test steps:
• Resolve the host name in DNS.
• Remotely sign in the remote user to Office Communications Server through the Access Edge Server
on the appropriate port.
The tool can indicate where the test was successful, provide details about the results of each test step and
if any test step failed, identify which step failed, and provide information about how to resolve the issue.
The tool can identify DNS name resolution issues for both the manual transport layer security (TLS) and
automatic client sign-in, including DNS configurations issues, TLS connectivity issues, and domain
credential issues for remote user sign-in.
Because the test results identify exactly what failed and provide detailed information about the problem,
this tool can help streamline the testing and troubleshooting processes.
Note: For security reasons, you should create a separate test account to use for your tests,
instead of using an actual account in your organization.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-11
Lesson 2
Understanding Lync Server 2013 Operational Tasks
Operations management involves administering an organization’s infrastructure components, and
includes the day-to-day administrative tasks, both planned and on-demand, that are required to keep an
IT system operating smoothly.
In a Lync Server 2013 environment, typical system administration tasks include enabling users, moving
Lync Server 2013 users (if required), backing up data, managing settings, monitoring system status and
performance, and managing connectivity.
You can use various resources to help you define what standard procedures are required in the
organization, and how to perform them. Because each organization is unique, you may have to further
customize and adapt these resources to suit everyday requirements.
We recommend that operational tasks be separated into manageable workloads, where tasks are
performed on a daily, weekly, and monthly basis. Daily tasks should focus efforts on aspects that are
critical to the functioning of a system; and monthly tasks should focus more on ensuring the long-term
health of a system. The tasks that must be performed can be separated into the following categories:
• Common Lync Server 2013 Operational Tasks
• Daily Tasks
• Weekly Tasks
• Monthly Tasks
Lesson Objectives
• Describe Common Lync Server 2013 operational tasks.
• Describe the required daily maintenance tasks.
Managing Users
You can use the Lync Server 2013 Control Panel
and Lync Server 2013 Management Shell to
manage the following user accounts in Lync Server
2013:
• Active Directory Contacts and User Accounts
• User Contacts
• Configure file transfer and URL filtering for Instant Messaging (IM).
• Conference disclaimer
• Conferencing Server information
• configuration settings for meetings
• Conferencing policies
• Meeting rooms
• Mobile Phones (Policy/Push notifications/MCX configuration/Autodiscover)
• Test devices
• Media configuration
• Monitoring Reports
Managing Archiving
You can perform the following tasks to manage Archiving in Lync Server 2013 Control Panel and Lync
Server 2013 Management Shell:
• Manage Archiving configuration options for your organization, sites, and pools.
• Change Archiving database options.
• Manage replication.
• Manage Quality of Service (QoS).
Managing Lync Server 2013 Disaster Recovery, High Availability, and Backup Service
Administrators can perform the following procedures for disaster recovery operations, and for maintaining
the backup service, which synchronizes the data in paired front-end pools.
Disaster recovery procedures, both failover and failback, are manual. If there is a disaster, the
administrator must manually invoke the failover procedures. The procedure for failback after the pool is
repaired is also manually performed.
• Fail over the Edge pool used for Lync Server federation.
• Failing back the Edge pool used for Lync Server federation or XMPP federation.
Daily Tasks
then use the Import-CsConfiguration cmdlet to read that .zip file and restore the topology,
configuration settings and policies to the Central Management Store. After that, the replication services of
Lync Server will replicate the restored information to other computers running the Lync Server services.
enables you to verify the replication status for any (or all) of the Lync Server computers in your
organization.
To test these two services, you can use Synthetic transactions in Windows PowerShell by typing the
following command.
Test-CsAddressBookService
For each Enterprise pool and Standard Edition server pool, you can view information about pool status,
and the status of other components used by the pool through the Lync Server 2013 Control Panel.
Alternatively, you can run a synthetic transaction by using actual user accounts. For example, if two users
are unable to exchange instant messages, you can run a synthetic transaction by using those two user
accounts (as opposed to a pair of test accounts), and then try to diagnose and resolve the problem. If you
decide to conduct a synthetic transaction by using actual user accounts, you will need to use the logon
names and passwords for each user.
MCT USE ONLY. STUDENT USE PROHIBITED
9-18 Administration and Maintenance of Lync Server 2013
Weekly Tasks
The following tasks are the required weekly
maintenance tasks that you should perform to
maintain a healthy Lync Server environment.
Monthly Tasks
Monthly tasks are tasks that are not required on a
frequent or regular basis, but you still need to
perform the monthly tasks to maintain the
solution over time.
Lesson 3
Developing Lync Server 2013 Troubleshooting Techniques
An organization must be prepared to deal with unexpected problems and should have a procedure to
manage problems from the point at which they are reported until their resolution. You should, therefore,
record information about how support staff diagnosed a problem so that you can use that information in
the future to avoid unnecessarily repeating completed work. Recording such information will also enable
you to troubleshoot Lync Server issues and use those tools that would best assist you in the
troubleshooting effort.
Lesson Objectives
• Describe the fundamental troubleshooting approach for Lync Server 2013 issues
• Describe which tools to use when troubleshooting a Lync Server 2013 issue.
IM and Presence
You should know which tools are best to used
when troubleshooting IM and Presence. The
following tools should be used to maintain and
troubleshoot Lync Server 2013 IM and Presence:
• Synthetic Transactions
• Lync Central Logging Service
• Event Viewer
• DbAnalyze
• LyncParser
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-21
• Monitoring Server
Enterprise Voice
To troubleshooting Enterprise Voice, you can use the following tools:
• Router Helper
• SEFAUtil
• SBASetupAnalyzer
• Synthetic Transactions
• Event Viewer
• Lync Client Logs
• Snooper
Lesson 4
Introduction to analyzing Lync Server 2013 logs and traces
In this lesson we discuss SIP and Session Description Protocol (SDP) with the aim of making students
familiar with basic concepts so that they can begin to explore SIP logs when troubleshooting.
Lesson Objectives
• Describe SIP components.
SIP Components
The following is a list of the components that form
entities used to transmit and receive SIP.
• A SIP entity receives or transmits a SIP request.
• Start Line. The first line in a SIP request. Indicates the type of transaction, for example, INVITE.
• Via. Indicates the path taken by the request thus far, and the path that needs to be taken when
routing the response.
• SIP dialog. Contains certain pieces of state needed to further the message transmission. A SIP dialog
must contain the following:
o From tag
o To tag
o Call ID
o Contact URI
o Route set
• Contact. Provides a SIP URI that can be used to contact the specific User Agent for subsequent
requests.
• User Agent. Provides detailed information about the User Agent client such as software version.
• Allow. Lists the methods or request types supported by the User Agent generating the SIP message
• Options. Is a method of discovering the capabilities of another party without actually calling that
party.
• Supported. Lists features supported by the User Agent that are beyond the core SIP capabilities.
SIP Requests
The following table lists the SIP Request Methods. These requests are followed by SIP Responses.
Request Description
ACK Confirms that the client has received a final response to an INVITE
request.
BYE Terminates a call and can be sent by either the caller or the called
party.
REGISTER Logon. Registers the address listed in the To header field with a SIP
server.
SUBSCRIBE Subscribes for an Event of Notification from the Notifier. Request for
Presence.
INFO Sends mid-session information that does not modify the session state.
UPDATE Modifies the state of a session without changing the state of the
dialog.
SIP Response
The following table lists the type of possible SIP responses offered by Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
9-24 Administration and Maintenance of Lync Server 2013
Session description
v= (protocol version)
o= (owner/creator and session identifier).
s= (session name)
i=* (session information)
u=* (URI of description)
e=* (email address)
p=* (phone number)
c=* (connection information - not required if included in all media)
b=* (bandwidth information)
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-25
Time description
t= (time the session is active)
r=* (zero or more repeat times)
Media description
m= (media name and transport address)
i=* (media title)
c=* (connection information—optional if included at session-level)
b=* (bandwidth information)
k=* (encryption key)
a=* (zero or more media attribute lines)
• Weekly tasks
• Monthly tasks
• As needed tasks
Task 4: Use Lync Server Management Shell to get user data and replication status.
Use Lync Server Management Shell
Task 5: Use Network Monitor to view Real Time Protocol (RTP) traffic.
Use Network Monitor to view RTP traffic
Results: At the end of this exercise, you will see how Microsoft Network Monitor with Lync Parsers can be
a useful tool for troubleshooting. However, you will need to practice this regularly to gain more familiarity
with this tool.
Important Before starting this lab, install the Lync Server 2013 Debugging Tools on 20336B-LON-FE1-03.
To do this, first mount the ISO needed.
7. On 20336B-LON-FE1-03, in Windows Explorer, browse to the newly mounted drive (likely D:\)
double-click LyncDebugTools.msi. Install the file by accepting all the defaults.
4. Use Snooper from the Lync Debugging Tools to view the log file output.
Task 4: Use Snooper from the Lync Debugging Tools to view the logfile output.
Use Snooper from the Lync Debugging Tools to view the logfile output.
Which server in the Adatum Lync Server deployment hosts the Master Central Management
Store?
Question:
On which protocol and port is the Mediation Server listening for signaling and traffic
Question:
Which audio codec is being used here? G711, RTA WB, RTA NB, Siren or G722?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 9-29
o When was the last change implemented in the environment, and what was changed?
Next, establish the scope of the problem. Is it related to a single user, multiple users, a single
location, or is it an enterprise wide issue or outage? The larger the scope, the higher the priority
becomes in resolving the problem.
You can investigate network issues by performing some “go-no-go” checks by using Ping, Telnet,
NSLookup, and Internet Explorer. For example, if a Lync user cannot log on, it may be because of
a wrong connection to the server, provided the account is not locked and is enabled. A Lync
2013 client attempts automatic discovery of the Lync pool by querying DNS for the DNS records
in a particular order, so is the client able to resolve the required DNS records? Running
IPCONFIG /DisplayDNS will show the current client DNS cache on the local computer. Is the Lync
client surfacing an error message in the user interface? This may provide a clue.
Check the event logs and client logs.
The example is not inclusive because there can be other causes, but is provided to start down a
path of understanding the issue to be resolved, ruling out the client side, and determining if it is
a network infrastructure issue, or server-side issue.
Review Question(s)
Question: Besides the Best Practices Analyzer, which Lync Server cmdlets can be used to
verify service activation and group permissions for your installation of Lync Server?
Question: What can you use to verify that users are able to successfully complete tasks such
as logging on to Lync, exchanging instant messages, or making calls to the public switched
telephone network?
Question: For Centralized Logging Service to work, the Controller must be able to contact
each Lync Server CLS Agent. Which ports must be opened inbound on every Lync Server,
including the Lync Edge Server?
Additionally, Lync Server Control Panel provides the capability to import and export the Enterprise Voice
Routing configuration. Review the product documentation to become familiar with the usage scenarios
for these cmdlets.
Tools
NextHop Community
Familiarize yourself with the NextHop Community portal. It has a wealth of information around Microsoft
Lync Server all in one place. http://go.microsoft.com/fwlink/?LinkId=208446
You can also search the Lync Blogs for information for more detailed technical articles, troubleshooting
articles, technical references, and related information that can help you ramp up, solve specific issues, and
acquire tips from other Lync experts.
Performance Counters
Windows operating systems include a tool called Perfmon.exe, which can be used to display a detailed
view of counters within the server, and of any applications installed. Lync Server 2013 has a plethora of
application-specific counters that can be used to determine the health of your Lync Server.
You can get a list of all performance counters on a server by running TypePerf.exe -q > counters.txt.
You can reference an article on using Lync PowerShell to view performance counters:
http://go.microsoft.com/fwlink/?LinkId=287057
Take advantage of the performance counters and the information they provide by deploying System
Center Operation Manager and the Lync Management Packs. This will provide real-time information
about the overall health of your environment and enable you to configure real-time alerts, so that you are
aware of potential issues before your users call you to resolve any issue.
MCT USE ONLY. STUDENT USE PROHIBITED
10-1
Module10
High Availability in Lync Server 2013
Contents:
Module Overview 10-1
Module Overview
After you migrate voice communications to Microsoft® Lync® Server 2013, you should provide high
availability and disaster recovery procedures that minimize downtime, speed recovery, and achieve the
appropriate level of application availability in the event of a failure. You should be aware about the
requirements for high availability with Lync Server 2013. You should also be able to plan and design for
load balancing with Lync Server 2013.
Objectives
• Describe high availability in Lync Server 2013.
Lesson 1
High Availability in Lync Server 2013
Providing high availability in Lync Server 2013 includes the new Distributed Pool Architecture, back-end
server availability through SQL mirroring, file sharing with Distributed File System (DFS), and Persistent
Chat availability. You can select from various infrastructure options to provide additional fault tolerance.
Lesson Objectives
• Describe high availability in Lync Server 2013.
The scaling of the infrastructure depends on the interpretation of high availability by the organization. If
performance must not be in any way impacted, even if part of the environment is unavailable, this could
necessitate a certain degree of over-provisioning during normal operation.
Often, with Lync Server 2013, high availability is considered to be within a physical site, while disaster
recovery is considered to be between physical sites. Your focus should be on the high availability aspects
within a site.
Question: Which edition of Lync Server will you install for a high availability solution?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 10-3
High availability for the back-end server is provided through the deployment of two SQL Servers, using
synchronous (also called high safety mode) SQL mirroring. Any reference to SQL mirroring, in the context
of Lync Server 2013, always refers to synchronous mirroring; asynchronous mirroring is not supported as
part of back-end server high availability in Lync Server 2013.
Note: SQL Server 2012 offers a feature called AlwaysOn Availability Groups, which is meant to be a
replacement for SQL mirroring (which is still supported on SQL Server 2012, although it is deprecated).
This feature is not supported in Lync Server 2013. Additional details about AlwaysOn Availability Groups
can be found at: http://go.microsoft.com/fwlink/?LinkId=287059
http://go.microsoft.com/fwlink/?LinkId=134606
MCT USE ONLY. STUDENT USE PROHIBITED
10-4 High Availability in Lync Server 2013
The recovery time objective (RTO) for automatic back-end SQL failover is five minutes, and data loss is not
anticipated because of the synchronous configuration. The recovery point objective (RPO) is also five
minutes.
The user experience depends on whether a SQL witness is deployed along with the SQL mirror. With a
witness deployed, when the principal fails, fail over happens automatically, and users should not notice
much interruption in ongoing sessions. When a SQL witness is not deployed, the administrator must
manually invoke the failover process. During the time it takes for administrative action, users can be
affected—active sessions can continue for about 30 minutes. After that time, or if the user attempts to
perform a persistent change (such as adding a contact) during that time, that user will be placed into a
resiliency mode.
http://go.microsoft.com/fwlink/?LinkId=275025
When using DFS, you must remember that DFS replication is a best-effort file replication mechanism. As
such, there are no published RTO (Recovery Time Objective)/RPO (Recovery Point Objective) numbers.
Generally, failover between DFS servers happens quickly; however, data replication delays may possibly
prevent users from being able to continue work in progress when a failover occurs.
If data that is contained on the file store is critical, it should be backed up frequently. DFS replication does
not protect against accidental data deletion or corruption, so backing up the data is advisable.
• Lync Server 2013 Standard Edition server and Persistent Chat server on separate servers, using
Standard Edition server as the next hop server
Persistent from a high availability perspective, a multiple-server pool should be deployed. This pool will
also require SQL Server to host the backend databases—these databases can be collocated on an existing
back-end SQL Server (used by the front-end pool), or a dedicated SQL instance can be used. Additionally,
the SQL databases can utilize SQL mirroring to provide availability.
• Stretched Persistent Chat server pool when data centers are geo-located with high bandwidth/low
latency. In this case, there would be four servers in each data center (for a total of eight), and two
servers would be active in each data center (because you have high bandwidth and low latency).
• Stretched Persistent Chat server pool when data centers are geo-located with low bandwidth/high
latency. In this case, there would be four servers in each data center (for a total of eight). However, all
four active servers would be in one data center only (because you have low bandwidth and high
latency).
SQL log shipping is used to provide replication of the data between the SQL instance in data center one,
and the SQL instance in data center two. This is discussed further in the Disaster Recovery module.
MCT USE ONLY. STUDENT USE PROHIBITED
10-6 High Availability in Lync Server 2013
Lesson 2
Configuring High Availability in Lync Server 2013
This lesson discusses the configuration of Lync Server 2013 high availability features.
Lesson Objectives
• Configure high availability for the back-end server.
Requirements
In general, setting up SQL mirroring between the
two back-end servers with a witness requires the
following:
• The primary server’s version of SQL Server
must support SQL mirroring.
For more information about which
features are supported by various editions of
SQL Server 2012, see:
http://go.microsoft.com/fwlink/?LinkId=151940
• The primary, mirror, and the witness (if deployed) must have the same version of SQL Server.
• The primary and the mirror must have the same edition of SQL Server. The witness may have a
different edition.
http://go.microsoft.com/fwlink/?LinkId=116096
1. On the Define the SQL Store page, next to the SQL store box, click New.
2. On the Define new SQL Store page, specify the primary store, select This SQL instance is in
mirroring relation, specify the SQL mirroring port number (the default is 5022), and then click OK.
3. Return to the Define the SQL store page, and select Enable SQL Store mirroring.
4. In the Define new SQL Store page, specify the SQL store to be used as the mirror. Select This SQL
instance is in mirroring relation, specify the port number (the default is 5022), and then click OK.
b. On the Define the SQL Store page, select Use SQL mirroring witness to enable automatic
failover, and specify the SQL store to be used as the witness.
c. Specify the port number (the default is 7022), and then click OK.
6. After you have defined your front-end pool and all other roles in your topology, use Topology Builder
to publish the topology. When the topology is published, if the front-end pool that hosts Central
Management Store has SQL mirroring enabled, you will see an option to create both primary and
mirror SQL store databases. Click Settings, and then type the path to use as the file share for the
mirroring backup.
Click OK, and then click Next to create the databases and publish the topology. The mirroring and
the witness (if specified) will be deployed. You can use Topology Builder to edit the properties of an
already existing pool to enable SQL mirroring.
1. In Topology Builder, right-click the pool, and then click Edit Properties.
2. Select Enable SQL Store Mirroring, and then, next to Mirroring SQL Store, click New.
3. Specify the SQL store that you want to use as the mirror.
4. Select This SQL instance is in mirroring relation, specify the SQL mirroring port number (the
default port is 5022), and then click OK.
5. If you want to configure a witness, select Use SQL mirroring witness to enable automatic failover,
and then click New.
6. Specify the SQL store that you want to use as the witness.
7. Select This SQL instance is in mirroring relation, specify the SQL mirroring port number (the
default port is 7022), and then click OK.
8. Click OK.
9. Publish the topology. When you do so, you will be prompted to install the database.
You must then install the database before starting the next procedure.
You should keep the following in mind when you set up SQL mirroring:
• If a mirroring endpoint already exists, it will be re-used with the ports defined there, and will ignore
the ones you specify in the topology.
• Any port already allocated for other applications on the same server, including those for other SQL
instances, should not be used for the installed SQL instances at hand. This implies that if you have
more than one SQL instance installed on the same server, they must not use the same port for
mirroring. For more information, refer to the following articles:
"Specify a Server Network Address (Database Mirroring)" in the MSDN Library at:
http://go.microsoft.com/fwlink/p/?LinkId=247346
http://go.microsoft.com/fwlink/p/?LinkId=247347
MCT USE ONLY. STUDENT USE PROHIBITED
10-8 High Availability in Lync Server 2013
Deployment Planning
In Lync Server 2013, the recommendation is to
deploy a minimum of three front-end servers in a
pool. When two servers are involved, the
preference is to install two Standard Edition pools,
and pair them together, rather than building a
front-end pool with only two front-end servers. If
such a pool is deployed, use the following
guidelines:
o The best practice is to restart both front-end servers at the same time.
o If the two servers cannot be restarted at the same time, you should re-start them in the reverse
order of the order in which they were stopped.
o If you cannot re-start them in that order, run the following cmdlet before starting the pool.
Pool Management
When deploying a front-end pool, it is critical that a minimum number of front-end servers are up and
running, to ensure that the pool is functional. The following table shows the details of pool size, and the
minimum running servers for the pool to be functional.
Total number of front-end servers in the Number of servers that must be running
pool for the pool to be functional
1–2 1
3–4 2
5–6 3
7–8 4
9–10 5
11–12 6
If the number of servers running falls below the functional level as shown in the preceding table, the
remaining servers in the pool go into survivability mode, and you will see the following message in the
event log: “Local Pool Manager has been disconnected from Pool Fabric Manager. (Id: 32163)”. After five
minutes, if the number of running servers is still below the threshold level, the remaining servers in the
pool will stop all Lync Server services, and the following messages will appear in the event log: “Pool
Manager failed to connect to Fabric Pool Manager (id: 32170) Server is being shut down because fabric
pool manager could not be initialized (id: 32173)”.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 10-9
If servers are added to, or removed from the pool configuration in Topology Builder, and then published
successfully, the existing front-end servers must be restarted.
The recommendation is to restart the servers one at a time. In the unlikely event that the entire pool was
offline when the configuration change occurred, you will need to run the following cmdlet.
Lesson 3
Planning for Load Balancing
Load balancing refers to the distribution of client connections among the servers in a server pool.
Deploying load balancing is based on the organization’s resiliency requirements. Lync Server 2010
introduced Domain Name System (DNS) load balancing, which Lync Server 2013 continues to utilize. You
can use DNS load balancing to reduce the administration overheads for load balancing on your network
and balance Session Initiation Protocol (SIP) traffic and media traffic.
You should be aware about the requirements so that you can assess the need for load balancing, the
types of load balancing, and the components in the infrastructure that do not support DNS load
balancing. Then, you will be able to plan for load balancing services and servers. You will also be able to
plan for the coexistence of load balancing with the earlier versions of Lync 2013 clients.
Lesson Objectives
• Describe DNS load balancing and hardware-based load balancing.
• Plan for load balancing infrastructure components.
The SIP client holds transactions of a longer duration because it registers with a server in the front-end
server pool, and retains the connection over an extended time period. Handling such long-term
transactions can be difficult for some hardware load balancing implementations. Lync Server 2010
introduced DNS load balancing to meet the need for load balancing SIP traffic, and this continues in Lync
Server 2013. DNS load balancing for SIP facilitates the deployment of Hardware load balancers, which are
required for all HTTP(S) traffic in Lync Server.
FQDN. The front-end server pools, Edge Server pools, Director pools, and stand-alone Mediation Server
pools support DNS load balancing.
Differences between Using Hardware Load Balancing and DNS Load Balancing
The difference in DNS registrations between using hardware load balancing and DNS load balancing is
illustrated in the following table.
Question: How does DNS load balancing simplify the deployment of hardware load
balancers with Lync Server 2013, when compared with the earlier versions of the product?
MCT USE ONLY. STUDENT USE PROHIBITED
10-12 High Availability in Lync Server 2013
• A former Office Communications Server R2 front-end server pool in the Lync Server 2013 topology.
• Instant message exchange with users of various public instant messaging (IM) services, such as
Microsoft® Windows Live® Messenger, America Online, and Yahoo!, and Extensible Messaging and
Presence Protocol (XMPP)–based providers and servers, such as Google Talk and Jabber.
• An IP private branch exchange (PBX) or IP-public switched telephone network (PSTN) as specified in
the Open Interoperability Program.
You need to consider scenarios where these systems connect to a Lync Server 2013 front-end server pool.
If all servers in the Lync Server 2013 pool are operational, these systems will function without any issues.
During the planning process, you should identify the components that do not support DNS load
balancing and plan the mitigation strategies. For example, some hardware devices might have firmware
updates that enable support for DNS load balancing.
In some scenarios, you may have to migrate from the earlier versions of servers and clients. However, you
need to closely match this inability with organizational requirements or any service level agreements
(SLAs) that specify the need for high availability, which might have an impact on the affected services. In
such scenarios, you might need to use hardware load balancing during the transition period to ensure
that load balancing and resiliency work as required, to support users.
Question: Does DNS load balancing in Lync Server 2013 remove the need for hardware load
balancers in your solution?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 10-13
While planning for coexistence, you need to be aware that server draining, which allows you to drain all
active connections from a server, is only possible in DNS load balancing. In this situation, the hardware
load balancer will continue to direct clients to a server targeted for draining.
Whether you decide to upgrade Office Communications Server 2007 R2 or to deploy hardware load
balancing to accommodate SIP traffic, ensure that the selected solution is aligned with the long-term
goals of the Lync Server 2013 deployment and the long-term needs of the organization.
Question: How will selecting hardware load balancing for SIP traffic affect the management
of a Lync Server 2013 Enterprise front-end server pool in a production environment?
MCT USE ONLY. STUDENT USE PROHIBITED
10-14 High Availability in Lync Server 2013
Lesson 4
Designing Load Balancing
While load balancing a Lync Server 2013 deployment, you need to plan and design the servers and
services that need to be load balanced and the load balancing technology to be used. Then, you need to
manage the coexistence for the previous versions of Lync Server 2013. You should, therefore, know how
to design for load balancing for a Lync Server 2013 solution.
Lesson Objectives
• Design DNS-based load balancing.
• Describe the guidelines for deploying DNS load balancing for front-end server pools.
• Design load balancing for coexistence with earlier versions of clients and devices.
The following table provides a list of IP addresses for each pool member and the individual A records for
the server FQDNs in the sample topology.
Question: Can you use DNS load balancing for a server running Lync Server 2013 Standard
Edition?
• Front-end pools
• Edge Server pools
• Director pools
• The regular pool FQDN that is used by DNS load balancing (for example, pool1.contoso.com) and
that resolves to the physical IPs of the servers in the pool
• Another FQDN for the web services of the pool (for example, web1.contoso.com), which resolves to a
hardware load-balanced virtual IP address of the pool
• Create DNS A host records to resolve the pool FQDN to the IP addresses of all servers in the pool.
2. In the console tree, expand the Enterprise Edition Front End pools node.
3. Right-click the pool, click Edit Properties, and then click Web Services.
4. Under Internal web services, select the Override FQDN check box.
5. Type the consolidated front-end pool FQDN that resolves to the hardware load-balanced virtual IP
addresses of the servers in the pool.
6. Under External web services, type the external pool FQDN that resolves to the hardware load-
balanced virtual IP addresses of the pool, and then click OK.
7. In the console tree, select Lync Server 2013, and then, in the Actions pane, click Publish Topology.
8. Start the Deployment Wizard on each Lync Server 2013 server that is impacted, and then run Setup
again.
To create DNS Host (A) Records for all internal pool servers
For each front-end server in your pool, create a DNS Host (A) record that maps the pool FQDN to the IP
address of that front-end server. For example, if you had a pool named, pool1.contoso.com, and three
MCT USE ONLY. STUDENT USE PROHIBITED
10-16 High Availability in Lync Server 2013
front-end servers with IPs of 192.168.1.1, 192.168.1.2, and 192.168.1.3, you would create the following
DNS entries.
• Can support a rich set of metrics (round robin, least connections, weighted, and so on); we
recommend a least connections-based load-balancing mechanism for the HLB
MCT USE ONLY. STUDENT USE PROHIBITED
10-18 High Availability in Lync Server 2013
• Must detect service availability by port (often called a heartbeat, or monitor); the polling interval must
be a configurable value with a minimum value of at least five seconds
• Must allow for adding and removing servers to the pool without shutting down
• If port monitoring is configured and one or more ports are generating errors in the event log, modify
the port monitoring rule(s) to allow a full TCP handshake (SYN/SYN-ACK/ACK) versus marking the
service as UP if it returns a SYN-ACK (that is, a partial TCP handshake (SYN/SYN-ACK); this is
sometimes referred to as TCP-half open
• The Lync Server 2013 server behind the HLB must have a registered FQDN. The IP address registered
for this FQDN must be publicly accessible from within the enterprise.
• The network adapter must have exactly one static IP address. This IP address will be used for the
incoming load-balanced traffic.
In addition, if you plan to use Exchange Server Unified Messaging, you should remember that only
Microsoft® Exchange 2010 SP1 interoperates with Lync Server 2013 DNS load balancing. If you use a
previous version of Exchange Server, you will be unable able to provide failover capabilities for users who
are using Exchange Server Unified Messaging capabilities, such as listening to their voice mail through
their mailbox.
Design Guidelines for DNS Load Balancing for Edge Server Pools
To deploy DNS load balancing on the external interface of your Edge Server pool, you need relevant DNS
entries. For the Access Edge service, you need one entry for each server in the pool. Each entry must
resolve the FQDN of the Access Edge service, such as sip.contoso.com, to the IP address of the Access
Edge service on one of the Edge Servers in the pool. For the web conferencing Edge service, you need one
entry for each server in the pool. Each entry must resolve the FQDN of the web conferencing Edge service,
such as webconf.contoso.com, to the IP address of the web conferencing Edge service on one of the Edge
Servers in the pool. For the audio/video conferencing Edge service, you need to add an entry for each
server in the pool. Each entry must resolve the FQDN of the audio/video conferencing Edge service, such
as av.contoso.com, to the IP address of the audio/video conferencing Edge service on one of the Edge
Servers in the pool.
To deploy DNS load balancing on the internal interface of your Edge Server pool, you need to add a DNS
entry for each Edge Server in the pool. Each entry should resolve the internal FQDN of the Edge Server
pool, such as sip.internal.com, to the IP address of one of the Edge Servers in the pool.
Question: Which considerations should you remember while deciding on the servers or
services that need load balancing?
Guidelines for Deploying DNS Load Balancing for Front-End Server Pool
The following are the guidelines for deploying
DNS load balancing in your Lync Server 2013
solution:
• When interaction occurs with many servers running earlier versions of Office Communications Server,
we recommend that you use hardware load balancing.
• If you are using Exchange Server 2010 SP1 or later versions, use DNS load balancing.
MCT USE ONLY. STUDENT USE PROHIBITED
10-20 High Availability in Lync Server 2013
• If Exchange Server Unified Messaging prior to Exchange 2010 SP1 is used, we recommend that you
use hardware load balancing.
Question: Can you name some examples where DNS load balancing is not supported?
• Provide load balancing for Lync Server 2013 clients and server only.
If you choose not to provide load balancing for clients prior to Lync 2010, combine it with a strategy for
moving from coexistence into Lync Server 2013 environment.
Question: How will previous versions of Lync Server 2013 interact in an environment where
DNS load balancing is used for SIP traffic?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 10-21
Lab Setup
Estimated Time: 30 minutes
• LON-CL1 as Adatum\Adam,
with the password, Pa$$w0rd
• RED-CL1 as Adatum\Alex,
with the password, Pa$$w0rd
We recommend that the steps in this and every lab be split between two students in your class. The
students can determine when to share tasks so that both students gain an understanding of the concepts
of each lab. If you need help, please inform the instructor. Note that if you both try to do tasks at the
same time, you may overwrite each other’s work and possibly lose data.
• Add : Administrators;SQLSvc
Note: On all virtual machines, verify that all of the services set to start automatically have started. Most
notably, check the Microsoft SQL Server® and Lync Server 2013 services. To do so, click Start, click
Administrative Tools, and then click Services. In the Services console, verify that all services that are set
to Automatic start have started. If not, right-click the service, and then click Start.
2. Create and assign permissions for the SQL mirroring file share.
Task 2: Create and assign permissions for the SQL mirroring file share.
Create SQLMirrorShare folder
Adjust sharing settings for SQLMirrorShare folder.
Adjust permissions for SQLMirrorShare folder to enable Full Control for the SQLSvc user account and
Administrators group.
Results: After completing this exercise, you should have used Topology Builder to establish database
mirroring between two defined SQL instances, and verified the configuration by using the SQL
Management Studio tool.
Results: After completing this exercise, you should have used the Lync Server 2013 Management Shell to
perform manual failover of the databases from the primary SQL instance to the mirror SQL instance, and
back.
Results: After completing this exercise, you should have observed the automatic failover process between
mirrored databases in Lync Server 2013, by using the Lync Management Shell to verify.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 10-25
Review Question(s)
Question: What option do you use to provide back-end high availability in Lync Server
2013? Do you use SQL Server Always-on Availability Groups, Synchronous SQL Mirroring,
SQL Clustering, or SQL Log Shipping?
Question: When servers are added to, or removed from the pool configuration in Topology
Builder, and the topology is successfully published, what additional action must be taken?
Question: If you deploy an Enterprise Edition front-end pool that contains only two front-
end servers, and both servers need to be stopped at the same time, what is the sequence of
steps to bring them back online?
The front-end servers in an Enterprise Edition pool are organized into upgrade domains. These are subsets
of front-end servers in the pool. Upgrade domains are created automatically by Topology Builder. We
recommend that when you upgrade front-end servers, you perform the upgrades one server at a time.
Stop one server first, upgrade it, and then restart it before you upgrade another server. Ensure that you
keep a track of which servers you have upgraded so far.
If the value of PoolUpgradeState is Busy, wait for 10 minutes, and then try Get-
CsPoolUpgradeReadiness again. If you see Busy for at least three consecutive times, after waiting 10
minutes between each attempt, or if you see any result of InsufficientActiveFrontEnds for
PoolUpgradeState, then there is a problem with the pool. If this pool is paired with another front-end
pool in a disaster recovery topology, you should fail the pool over to the backup pool, and then update
the servers in this pool.
MCT USE ONLY. STUDENT USE PROHIBITED
10-26 High Availability in Lync Server 2013
The Get-CsPoolUpgradeReadiness cmdlet also returns information about each upgrade domain in the
pool, and about which front-end servers are in each upgrade domain. If the ReadyforUpgrade value is
True for the upgrade domain that contains the server you want to upgrade, you can safely upgrade that
server now. To do so, perform the following steps:
1. Stop new connections to the front-end server by using the Stop -CsWindowsServices -Graceful
cmdlet.
5. After updating the front-end servers in the pool, you are ready to proceed with the steps to update
the back-end servers.
First, you should determine which back-end database is the principal, and which is the mirror, by typing
the following cmdlet.
Note If more than one type of Lync database is hosted on the back-end, you should get and verify the
database mirror state for each of them.
Important If the Central Management Store is hosted in this pool, determine the primary and mirror, and
fail it over first.
Perform the fail over of the user database by typing the following cmdlet.
Note If more than one type of Lync database is hosted on the back-end, you should fail over each of
them.
Important If the Central Management Store is hosted in this pool, determine the primary and mirror, and
fail it over first.
After the failover of the Lync databases is complete, perform the updates and restart server/services, if
required. Execute the cmdlet to verify the CsDatabaseMirrorState.
Note If the mirror state shows as suspended, you may need to start SQL Server Management Studio and
connect to the SQL Server. Then, for each database that shows as suspended, select it, right-click and
select Tasks, then select Mirror, and on the Database Properties page for Mirroring, click Resume.
Repeat for any additional databases.
When Get-CsDatabaseMirrorState shows mirroring status as synchronized, fail back to the principal
database by running the following cmdlets for each database type.
Module11
Disaster Recovery in Lync Server 2013
Contents:
Module Overview 11-1
Lesson 2: Tools for Backing Up and Restoring Lync Server 2013 11-10
Lesson 3: Critical Lync Server 2013 Data to Back Up and Restore 11-12
Lesson 4: Critical Lync Server 2013 Data to Export and Import 11-15
Lesson 5: Designing Branch Site Resiliency 11-18
Lab: Configuring Disaster Recovery in Lync Server 2013 11-24
Module Overview
After you migrate voice communications to Microsoft® Lync® Server 2013, you should provide high
availability and disaster recovery procedures that minimize downtime, speed recovery, and achieve the
appropriate level of application availability in the event of a failure. Lync Server 2013contains a number of
new disaster recovery features. You can use the tools and methods available for successfully backing up
and restoring a Lync Server 2013 environment, and back up, restore, export, and import critical Lync
Server 2013 data. You can also use Lync Server 2013 to design for branch site resiliency.
Objectives
• Describe the high availability options in Lync Server 2013.
• Describe the tools for backing up and restoring Lync Server 2013 data.
Lesson 1
Disaster Recovery in Lync Server 2013
Lync Server 2013 provides a number of disaster recovery options, such as front-end pool pairing, the Lync
Backup Service, and Persistent Chat stretched pools. You can use various commands to manage disaster
recovery in Lync Server 2013.
Lesson Objectives
• Describe the high availability and disaster recovery life cycle for Lync 2013.
Lync Server 2013 High Availability and Disaster Recovery Life Cycle
The following table shows the life cycle of high
availability and disaster recovery in Lync Server
2013. The table lists the various scenarios, the
associated tasks, and the Lync Server 2013 tool or
tools that you can use in each scenario.
o The same platforms should be paired to each other (Physical to Physical, and Virtual to Virtual).
• There is no distance restriction between pools that are paired to each other. However, we recommend
that you keep paired pools within the same world region.
• Each pool in a pair should be sized to handle the capacity of both pools combined, if one of the pools
fails.
• Even though backup relationships between two front-end pools must be 1:1 and symmetrical, each
front-end pool can still also be the backup registrar for any number of Survivable Branch Appliances
(SBA) or Survivable Branch Servers (SBS), just as in Lync Server 2010. However, disaster recovery
support is not extended to these appliances. For example, if we have Pool1 and Pool2 paired, and
SBA1 is using Pool1 for its backup registrar, when Pool1 fails, and the administrator invokes failover to
Pool2, SBA1 will not be able to then use Pool2 for user services. The administrator must redefine the
relationship in Topology Builder for SBA1.
• For pool failover and pool failback, the engineering target for recovery time objective (RTO) is 30
minutes. This is the time required for the failover to happen, after administrators have determined
there was a disaster and initiated the failover procedures. It does not include the time for
administrators to assess the situation and make a decision, nor does it include the time for users to
sign in again, after failover is complete.
• For pool failover and pool failback, the engineering target for recovery point objective (RPO) is 30
minutes. This represents the time measure of data that may be lost because of the disaster, due to
replication latency of the Backup Service. For example, if a pool goes down at 10:00 A.M., and the
RPO is 30 minutes, data written to the pool between 9:30 A.M. and 10:00 A.M. might not have
replicated to the backup pool, and would be lost.
• All RTO and RPO numbers assume two data centers within the same world region with high-speed,
low-latency transport between them.
• The Central Management Store (CMS) will be protected with pool pairing, assuming the pool that is
paired is the CMS Master.
http://go.microsoft.com/fwlink/p/?LinkId=275029
When a pool fails, the administrator must perform a pool failover manually, using Lync Management Shell
cmdlets. These are discussed in the “Managing Disaster Recovery” topic of this lesson.
During a pool failure, users will be in Resiliency Mode.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-5
• The Lync Backup Service contains multiple backup modules, including one for the Central
Management Store (CMS), file store, and user store. Each module interacts with the Lync Backup
Service to send data to the peer in the secondary site.
Get–CsBackupServiceConfiguration
To set the Backup Service synchronization interval, type the following command.
For example, the following command sets the interval to three minutes:
Note: Although you can use this cmdlet to change the default synchronization interval for the
Backup Service, you should not do so unless it is absolutely necessary, because the sync interval has a
great impact on the Backup Service performance and the recovery point objective (RPO).
To get the Backup Service status for a particular pool, type the following command.
Note: The Backup Service synchronization status is defined unidirectional from a pool (P1) to its
backup pool (P2). The synchronization status from P1 to P2 can be different than the one from P2 to P1.
For P1 to P2, Backup Service is in a “steady” state if all the changes made in P1 are completely
replicated over to P2 within the synchronization interval. It is in the “final” state if there are no more
changes to be synchronized from P1 to P2. Both states indicate a snapshot of the Backup Service at the
time the cmdlet is run. This does not imply that the state returned will stay as is afterward. In particular,
the “final” state will continue to hold only if P1 does not generate any changes after the cmdlet is run.
This is true in the case of failing P1 over to P2 after P1 is placed into the read-only mode as part of the
Invoke-CsPoolfailover execution logic.
MCT USE ONLY. STUDENT USE PROHIBITED
11-6 Disaster Recovery in Lync Server 2013
To get information about the backup relationship for a particular pool, type the following command.
Database Requirements
The following list shows the database requirements:
• One dedicated database instance is located in the same physical data center in which the home front
end of the Persistent Chat Server service is located. This database will serve as the SQL Server mirror
for the primary Persistent Chat database. Optionally, designate an additional SQL Server to serve as
the mirroring witness, if you want an automated fail over to the mirror database.
• One dedicated database instance is located in the other physical data center. This database will serve
as the SQL Server Log Shipping secondary database for the database in the primary data center.
• One dedicated database instance serves as the SQL Server mirror for the secondary database.
Optionally, designate an additional SQL Server to serve as the mirroring witness. Both of these must
be located in the same physical data center as the secondary database.
• If Persistent Chat Server compliance is enabled, an additional three dedicated database instances are
required. Their distribution is the same as those previously outlined for the Persistent Chat database.
While it is possible for the compliance database to share the same SQL Server instance as the
Persistent Chat database, we recommend stand-alone instances for high availability and disaster
recovery.
Data Replication
Data is replicated between the two SQL instances by using SQL Log Shipping. As a result, file share
locations will be required and designated for the SQL Server Log Shipping Transaction Logs. This share is
not defined as part of a File Store role in the topology.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-7
http://go.microsoft.com/fwlink/p/?LinkId=216765
Deployment
Deployment of Persistent Chat in a stretched pool requires the following:
• Creating a pool in Topology Builder, and designating specific Persistent Chat servers as Active versus
Passive.
• Configure SQL Log Shipping between the primary SQL instance, and the secondary SQL instance (or
primary mirror and secondary database, if you use SQL mirroring).
For more information about setting up log shipping for the primary SQL database, see:
http://go.microsoft.com/fwlink/p/?LinkId=275030
For more information about setting up log shipping between the primary mirror and the log
shipping secondary database, see:
http://go.microsoft.com/fwlink/p/?LinkId=275031
Export-CsConfiguration –FileName
c:\CsConfigurationFile.zip -Verbose
Export-CsLisConfiguration –FileName
c:\CsLisConfigurationFile.zip –Verbose
If the Central Management Store is not available, use the –LocalStore option:
2. Locate the Central Management Server. If the pool that has failed owns the Central Management
Server, this must be failed over first.
Invoke-CsManagementServerFailover -WhatIf
3. When failing over the Central Management Server, first determine if the pool that hosted the Central
Management Server was using database mirroring, and which back-end server is the principal.
MCT USE ONLY. STUDENT USE PROHIBITED
11-8 Disaster Recovery in Lync Server 2013
6. Fail over the users from Pool1 to Pool2 by using the Invoke-CsPoolFailover cmdlet.
7. If applicable, change the Edge Server to use the new next hop pool.
2. You can use the Get-CsBackupServiceStatus cmdlet to check the process status, typing the
following code.
Lesson 2
Tools for Backing Up and Restoring Lync Server 2013
This lesson covers the native Microsoft Windows® and Lync Server 2013 tools that can be used to back
up and restore the critical data.
Lesson Objectives
• Describe the Windows tools for backing up and restoring critical data.
• Describe the Lync Server 2013 tools for backing up and restoring critical data.
For example, to retrieve help from the command prompt on the New-CsVoicePolicy cmdlet, type the
following command.
Note: If you open a Windows PowerShell window, rather than the Lync Server Management Shell,
by default you will not be able to run the Lync Server 2013 cmdlets. To run the Lync Server 2013
cmdlets from within Windows PowerShell, first type the following at the Windows PowerShell command
prompt.
Import-Module Lync
The Lync Server Management Shell is automatically installed on every Lync Server 2013 Enterprise Edition
front-end server or Standard Edition server.
• Import-CsRgsConfiguration. This cmdlet indicates success or failure when importing the Response
Group configuration that was generated by Export-CsRgsConfiguration to a specified pool (passed
as a parameter).
To prevent major outages in case of disaster, you should perform a daily backup of the Response Group
configuration. In case of a dramatic event that destroys all the Lync Server 2013 data, the administrator
can restore the full Response Group configuration as soon as the replacement servers are functional.
Topology Builder
Topology Builder facilitates the definition of a topology and its components, and it is essential for the
deployment of Lync Server 2013 servers. Topology Builder can use the XML topology file provided by the
Planning Tool to start the initial design of the topology, or the wizards in Topology Builder can be used to
design the deployment. Lync Server 2013 publishes the Topology Builder results to a Central
Management Store that is used to configure all Lync Server 2013 servers in the organization.
Topology Builder enables you to export your published topology to an XML file that can be used to
publish a new topology elsewhere.
Note: You cannot install Lync Server 2013 servers without using Topology Builder or the XML
output of the Topology Builder and manually publishing the information by using Lync Server
Management Shell.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-11
Lesson 3
Critical Lync Server 2013 Data to Back Up and Restore
This lesson discusses the data that must be backed up and then restored in Lync Server 2013.
Lesson Objectives
• Backup and restore SQL Server databases.
• RGSConfig. Lync Server Response Group service data file for the configuration of services.
• LcsLog. The archiving database.
• LcsCdr. Data store for the Call Detail Recording (CDR) process of the Monitoring server.
• QoEMetrics database. Quality of Experience (QoE) data file stored from the Monitoring server.
• Mgc. Persistent Chat data, which is the actual chat content posted in chat rooms.
Backing Up RgsConfig
To back up Response Group configurations for a
pool, run the following command.
MCT USE ONLY. STUDENT USE PROHIBITED
11-12 Disaster Recovery in Lync Server 2013
For example, you type the following code to back up Response Group configurations.
Restoring RgsConfig
To back up Response Group configurations for a pool, run the following command.
For example, you type the following code to restore the Response Group configurations.
Get-CsService –ApplicationServer
This command returns the Universal Naming Convention (UNC) path of the Application server (\\mia-
sql1\mcs) where the music-on-hold file is stored (\\mia-sql1\mcs\Miami-ApplicationServer-
1\AppServerFiles\CPS\CpsMoH.wma). Because this is a simple file, it can be backed up by using any
backup method.
Lesson 4
Critical Lync Server 2013 Data to Export and Import
This lesson discusses the data that must be exported and then imported in Lync Server 2013.
Lesson Objectives
• Export and import Lync Server 2013 Config.
3. Select the local file and then select the exported ZIP file.
After any changes are made to the LIS configuration, ensure that you republish the settings by using
Lync Server Management Shell (Publish-CsLisConfiguration).
For example, you can type the following code to export user data.
For example:
Lesson 5
Designing Branch Site Resiliency
In a Lync Server 2013 deployment, you can use many components to provide resiliency for the voice
infrastructure. When designing site resiliency, you will also need to plan the rerouting of incoming and
outgoing PSTN calls, in case of PSTN connectivity failures. You should know about site resiliency options,
rerouting inbound and outbound PSTN calls, and the guidelines for creating a resilient network design
and voice design. You will also become familiar with the best practices for designing site resiliency.
Lesson Objectives
• Describe the site resiliency options.
For a smaller site, you can deploy a local SBA and designate the SBA as the backup registrar for users.
Under normal circumstances, the users register with a front-end server or pool in a central site. During a
WAN outage, users can use the SBA for registration. Using SBA for registration ensures availability of
limited local functionality, along with the ability to make and receive calls over the PSTN.
If there are between 500 and 1,000 users in a site, you can choose to use a Survivable Branch Server (SBS)
instead of an SBA. An SBS is basically an SBA, deployed on separate hardware. You can then connect the
SBS to a local gateway. By using more powerful hardware than what the SBA can provide, you can achieve
greater scalability.
SIP Trunking
The ability of Lync Server 2013 to use SIP trunks for PSTN connectivity helps provide resiliency in some
scenarios. By deploying redundant trunks in single locations or connecting multiple trunks in different
sites, you can route calls even if the primary connection is unavailable.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-17
Media Bypass
Media bypass enables clients to send media directly to the Mediation Server peer, which can improve
audio quality and reduce the bandwidth consumption on WAN links. Users in branch sites with PSTN
connectivity but no server infrastructure can benefit from this functionality. It ensures that the topology
uses WAN links efficiently.
Consider a scenario where two sites have a dedicated multiprotocol label switching (MPLS) connection,
and the Lync Server Edge Servers in both locations connect to the Internet. You can configure CAC to
reroute calls across the Internet link if CAC denies the calls across the MPLS link. You need not use the
MPLS link; you divert the traffic between the Edge Servers. Similarly, you can reroute calls, which CAC
denies, because of a congested link or calls that cannot reach their gateway because of WAN outage,
through local PSTN connectivity.
You can use a number of different ways to accommodate various degrees of site resiliency in the Lync
Server 2013 infrastructure. Choose the resiliency methods based on the network layout of your
environment and the workloads that require resiliency.
Question: Do you consider an SBA sufficient for the resiliency requirements of a branch site?
• You provide easier PSTN resiliency or high availability in a few central sites.
• You benefit from cost efficiency if branch sites are well-connected to a central site with PSTN
connectivity
• You need not handle least-cost routing, because with centralized PSTN connectivity, the IP telephony
provider is normally responsible for this task.
Centralized PSTN access, however, has the following disadvantages:
• It may require additional investment in WAN links to provide the needed availability.
MCT USE ONLY. STUDENT USE PROHIBITED
11-18 Disaster Recovery in Lync Server 2013
• You enjoy greater flexibility in the choice of PSTN connectivity for branch sites.
• You can provide local PSTN connectivity for sites with poor WAN connections
• You combine distributed PSTN access with central SIP trunking infrastructure greater flexibility.
• Distributed PSTN access works easily with analog devices such as alarm systems and fax machines at
branch sites.
The disadvantages of distributed PSTN access are:
• It requires more hardware such as Mediation Servers and gateways, compared to centralized PSTN
connectivity
• It involves higher administrative overhead (more PSTN providers and administrator-configured least-
cost routing)
For some larger deployments, you may need to provide centralized PSTN access in some regions and use
a distributed model in other regions.
In most cases, similar to other design decisions in your Lync Server 2013 environment, network
infrastructure may govern your choices. The network infrastructure also dictates the possible
implementations.
Question: When should an organization choose to switch from a decentralized PSTN access
topology to a centralized access topology, or from a centralized access topology to a
decentralized PSTN access topology?
When you plan for rerouting of incoming PSTN calls, you should consider the following:
• If the SIP trunk provider is able to hand off calls to your Mediation Server, the provider may have
multiple Session Border Controllers (SBCs) for a given trunk. Each of these connects to individual
Mediation Servers.
• The SIP trunk provider may route the call to a SIP trunk in some other site based on the connectivity
of redundant links to sites. Additionally, we recommend that the SIP trunk should use a dedicated
MPLS connection for connectivity to your environment.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-19
• While using advanced gateways or IP-PBX with capabilities that can provide rerouting of incoming
calls, a popular failover method that you can adopt is to reroute incoming calls to mobile phones of
users.
While considering rerouting of inbound calls from the PSTN, all stakeholders must agree on an acceptable
definition of rerouting. For example, you can consider routing calls to cell phone numbers available to
users, if Lync Server 2013 Enterprise Voice is unavailable to fulfill the requirements. Otherwise, you must
plan for rerouting calls to alternative PSTN entry points in other Lync Server 2013 sites. If you require
rerouting of calls to alternative PSTN entry points, you will need to have the same telephony provider for
all the affected PSTN connection points. In any case, the ability to reroute incoming PSTN calls requires
some coordination with the chosen telephony provider.
• Ensure that the alternative PSTN gateways and their associated PSTN connections are scaled to
handle the additional call volume if the primary gateways are unavailable.
• Ensure that the rerouting of outgoing PSTN calls through a gateway located in another country is not
accidental. Rerouting should be evaluated for both resiliency provided and potential costs.
• Ensure that the rerouted calls meet the legal requirements for Voice over IP (VoIP) calling.
You can configure outgoing rerouting of PSTN calls within the Lync Server 2013 Control Panel after your
Enterprise Voice topology is deployed. The incoming rerouting will require configuration outside the Lync
Server 2013 environment.
Question: What are the usage scenarios where the ability of an advanced gateway or IP-PBX
to reroute inbound calls to mobile phones of users could be a viable option?
• Consider the procedure to handle call rejection on a bandwidth-constrained WAN link when
employing CAC.
• Use Lync Edge Servers because they can help provide alternative paths for access to services.
MCT USE ONLY. STUDENT USE PROHIBITED
11-20 Disaster Recovery in Lync Server 2013
• Consider that a resilient distributed network is highly dependent on your WAN providers.
The components of a resilient network design can vary from one organization to another. While designing
your Lync Server 2013 topology, you must consider the organization’s requirements.
• Consider the available network infrastructure and deploy local PSTN connectivity to sites with non-
resilient WAN connections, in the form of SBAs.
• Network layout
You should consider the following best practices for designing site resiliency:
• Be aware that business requirements should form the basis of your site resiliency design.
• Be aware that the required workloads are more relevant than the number of users in a site.
Question: Which factor has the most impact on how a resilient site topology will look in
Lync Server 2013?
MCT USE ONLY. STUDENT USE PROHIBITED
11-22 Disaster Recovery in Lync Server 2013
Lab Setup
Estimated Time: 50 minutes
• LON-CL1 as Adatum\Adam,
with the password, Pa$$w0rd
• RED-CL1 as Adatum\Alex,
with the password, Pa$$w0rd
Important We recommend that the steps in this and every lab be split between two students in your
class. The students can determine when to share tasks so that both students gain an understanding of the
concepts of each lab. If you need help, please inform the instructor. Please note that if you both try to do
tasks at the same time, you may overwrite each other’s work and possibly lose data.
Results: After completing this exercise, you should have used Topology Builder to configure pool pairing
between two existing pools.
3. Start a Lync Online Meeting on LON-CL1 and join the meeting from RED-CL1.
Task 3: Start a Lync Online Meeting on LON-CL1 and join the meeting from RED-CL1.
Start a Lync Online Meeting on LON-CL1 and join from RED-CL1
MCT USE ONLY. STUDENT USE PROHIBITED
11-24 Disaster Recovery in Lync Server 2013
Results: After completing this exercise, you will have observed client behavior during a pool failure. You
will have also used Lync Management Shell to invoke failover to the backup pool, to restore services for
the users on the failed pool.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 11-25
Implementing disaster recovery steps to fail over a pool can seem daunting, or you may wonder what
state the topology is in, after someone else has started the steps. This may also cause some confusion
on next steps. You should keep the following guidelines in mind to help you perform the correct steps.
First, determine where the Central Management Store is located. Does it need to be failed first, if it is in
the affected pool.
Get-CsManageStoreReplicationStatus -CentralManagementStoreStatus
If CMS is on Lync Server 2010 in a coexistence scenario, then the Lync Server 2010 failover procedures
prevail, otherwise if CMS is on a pool running Lync Server 2013, follow the product documentation
steps at http://go.microsoft.com/fwlink/?LinkId=282343
Has the pool been failed over by someone else? To determine this, you can use the following
command.
Get-CsRegistrarConfiguration
This cmdlet returns the state of Lync 2013 pools in the environment. The PoolState will either be Active
or FailedOver. When running cmdlets, include the -Verbose parameter to ensure that information
about the cmdlet execution, including eventual failure or success of the test and location of any logs or
reports generated by the cmdlet is displayed on the screen. To do this, you can use the following
cmdlet.
Get-CsPoolBackupRelationship -PoolFqdn
This cmdlet returns information about the backup pool associated with a Microsoft Lync Server 2013
pool.
Review Question(s)
Question: By which method in Lync Server 2013 provides disaster recovery?
Question: When you configure and enable front-end pool pairing for disaster recovery, what
additional Lync service is installed?
Question: For pool failover and pool failback, the engineering target for recovery time
objective (RTO) is 30 minutes. What is the meaning of RTO?
Answer:
They should deploy two Standard Edition pools with a paired backup relationship.
MCT USE ONLY. STUDENT USE PROHIBITED
11-26 Disaster Recovery in Lync Server 2013
Contoso has deployed the two Standard Edition pools with a paired backup relationship and now want to
understand the Lync Backup Service.
1. The Lync Backup service synchronizes user data and conference content between paired Enterprise
Pools or Standard Edition servers. The synchronization cycle occurs every two minutes (by default).
Changes are exported in batches to ZIP files in the Backup pool. Source pool signals the Backup pool
to import the changes. When changes have been imported, The ZIP file is removed and a cookie is
returned to the Source pool.
At the beginning of the next synchronization cycle, the Source pool uses the cookie as a starting point for
exporting the changes to the Backup pool. Additionally, when the Backup-CsPool or Invoke-
CsPoolFailover cmdlets are run, they trigger the Backup Service to check for changes and send them to
the paired pool. The same process is simultaneously running to replicate the changes from the Backup
Pool to the Source Pool. Replication of UserServices.PresenceFocus and ConfServices.DataConf modules is
bi-directional between pools. Replication of CentralMgmt.CMSMaster module is one-way only (Active ->
Passive).
ActiveMachineFqdn : L2013FE01.contoso.com
OverallExportStatus : ErrorState
OverallImportStatus : NormalState
BackupModules : {UserServices.PresenceFocus:[ErrorState,NormalState],
ConfServices.DataConf:[FinalState,NormalState]}
FinalState All changes have been successfully exported from the Source pool and
successfully imported to the Backup pool.
SteadyState The Backup module in the Source pool is able to export all changes to the
Backup pool in a single batch.
NonSteadyState The Backup module in the Source pool is not able to export all changes to
the Backup pool in a single batch (too many changes result in a backlog).
ErrorState The Backup module in the Source pool is unable to export the changes to
the Backup pool because of failure.
Module12
Planning a Migration to Lync Server 2013
Contents:
Module Overview 12-1
Module Overview
The process of migration requires that you know about coexistence and migration in Microsoft Lync
Server 2013. You should be able to design the infrastructure migration strategy and the migration
strategy for Lync Server 2013 clients and devices.
Objectives
• Describe the migration process.
• Describe migration and coexistence topologies.
Lesson 1
Overview of Coexistence and Migration
In Microsoft Lync Server 2013, migration refers to migrating users and devices. Before successfully
migrating to Lync Server 2013, you need to plan the migration approach and the voice migration
strategies. You also need to ensure that the prerequisites for the existing infrastructure are fulfilled.
Lesson Objectives
• Describe the migration concept.
Overview of Migration
Lync Server 2013 migration refers to migrating
users and devices, but not upgrading them. This is
because, with each product release, a product
evolves from its earlier version and there are major
changes. For example, from Microsoft Office
Communications Server 2007 to Office
Communications Server 2007 R2, the product
changed from a 32-bit product to a 64-bit
product. More changes occurred from Office
Communications Server 2007 R2 to Lync Server
2013, where the management architecture was
redesigned extensively.
While some organizations find migration a challenge because they find it difficult to upgrade a server
from one major version to another, other organizations perceive it to be easier. There are many benefits
of migration over upgrading, because the former involves a clean installation, and there is no remaining
data from earlier versions. In migration, the hardware platform can evolve to a virtualized environment,
where provisioning new servers is not considered a major issue.
Lync Server 2013 migration may also involve migrating from an existing voice infrastructure to Lync Server
2013. Although, the approach here is to migrate users and direct inward dialing (DID), you need to design
a device strategy. This strategy might involve tasks such as:
• Examining whether the existing devices can be re-used by using support for these from Lync Server
2013 and gateway vendors.
Some other migration tasks that are more complex may have dependencies on existing infrastructure
components. An example is Domain Name System (DNS) load balancing that is not compatible with
earlier version endpoints, be it devices, phones, or other servers. Another example is a situation where
Office Communications Server 2007 R1 or Office Communications Server 2007 R2 co-exist with private
branch exchange (PBX) that is already implemented in some form. For Remote Call Control (RCC)
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-3
gateways from vendors, it is possible that a certain gateway version only supports Office Communications
Server R1, but not Office Communications Server R2. Also, some gateway versions support Office
Communications Server R2, but not Office Communications Server R1, thus complicating the migration
procedure.
Terms
Migration. Refers to moving your production deployment from a previous version of Lync Server 2010 to
Lync Server 2013.
Upgrade. Refers to installing a newer version of software on a server or client computer.
Coexistence. Is the temporary environment that exists during migration when some functionality has been
migrated to Lync Server 2013 and other functionality still remains on a prior version of Lync Server 2010
Interoperability. Is the ability of your deployment to operate successfully during the period of coexistence.
Question: What are the benefits of a migration approach versus an upgrade approach, and
vice versa?
Migration Approach
In nearly every migration, you should use the side-
by-side migration path. In a side-by-side
migration, you deploy a new server with Lync
Server 2013, alongside a corresponding server that
is running Lync Server 2010, and then transfer
operations to the new server. If it becomes
necessary to roll back to Lync Server 2010, you
only have to shift operations back to the original
servers. Be aware that in this situation any new
meetings scheduled with upgraded clients will not
work, and the clients would also need to be
downgraded. In this approach, you build a full
Lync Server 2013 environment running side-by-side with an Office Communications Server 2007 R2/Lync
2010 environment. This approach is different from Office Communications Server R2, where you migrate
inside out—front-end servers, and then Edge Servers.
The new approach emphasizes on continuity of service. The approach also advocates running a pilot first,
and then moving to production. This would build your confidence to move from an end-user-experience
perspective to an administrator-perspective. Developing confidence is important because you need
people to be confident and provide good feedback as you migrate and roll out the Lync Server 2013
solution.
The other benefit of this approach is that it minimizes the impact of change. For example, if you are
running a trial to migrate the users, the impact will be minimal when compared with the outside-in or
inside-out approach. One of the features of this approach is the flexibility of speed and scaling to meet
the specific migration needs of your environment.
After you have deployed Lync Server 2013 in parallel with Lync Server 2010, the deployment represents a
coexistence testing state of Lync Server 2013 and Lync Server 2010. While in this state, you must test and
ensure that services are started, that each site can be administered, and clients can communicate with
current and legacy users. Prior to the migration of all users, you must understand the state of each
deployment and ensure that each deployment is functional and working properly. Typically, the
coexistence testing phase exists throughout the pilot testing of Lync Server 2013. Legacy users are moved
MCT USE ONLY. STUDENT USE PROHIBITED
12-4 Planning a Migration to Lync Server 2013
to Lync Server 2013 for a period of time to ensure that application compatibility, features, and functions
are working properly. After pilot testing, users and applications are moved to the production version of
Lync Server 2013, and the legacy pools and applications of Lync Server 2010 are retired.
Note: You must migrate the Edge Servers and Director servers in Lync Server 2013 in
parallel. This implies that they must be the same version. You should always check the
compatibility of Open Interoperability Program with Lync Server 2013.
You must thoroughly consider the design options because they have an impact on your migration plan.
Using the side-by-side approach, you can pilot each of your sites. If they are geographically, culturally, or
organizationally different—such as factory workers, office workers, and traveling sales force—you can
avoid any unwanted experience during the pilot of each site. The approach allows speeding up the
migration process, if everything works smoothly and user feedback is good.
You must also note that user perception is the key to their evaluation of the migration process. A
challenging experience will affect their overall evaluation of the entire project, and Lync as a Unified
Communications platform.
Support Boundaries
Lync Server 2013 supports migration from either
of the following:
• Microsoft Lync Server 2010
For details about the ability of Lync Server 2013 clients to coexist and interact with clients from earlier
versions of Lync Server and Office Communications Server, see “Client Interoperability in Lync 2013”, in
the Planning documentations.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-5
Topology Requirements
Lync Server 2013 supported topologies have
changed, which may also affect your deployment.
The Archiving and Monitoring server roles have
been moved to the front-end servers. You must
evaluate your current topology against the new
capabilities of the Lync 2013. If your current
topology does not match up to the new planned
deployment, then you must change your
migration strategy.
Office Communications Server 2007 R2/Lync 2010 Server and Client Updates
To migrate from Office Communications Server 2007 R2 to Lync Server 2013, you require some minimum
security update levels. The following table specifies the update details.
You must identify dependencies in the planning and design phases to avoid challenging situations during
actual deployment. You can use the latest version of the Lync Server 2013 supportability guide to identify
dependencies and supported versions of software and hardware.
Telephony prerequisites
The dependencies and migration options can be more complex for telephony interoperability. You must
check for references in the Microsoft Unified Communications Open Interoperability Program website.
You can find a list of all qualified and supported IP PBXs, gateways, and Session Initiation Protocol (SIP)
trunk providers, including the minimum firmware or software required to support Lync Server 2013.
While designing and planning Lync Server 2013, identify and prepare your solution for interoperability.
Note that if an IP PBX is not interoperable with Lync Server 2013, you can usually achieve interoperability
by using a gateway qualified through the Microsoft Unified Communications Open Interoperability
Program.
Question: Does Lync Server 2013 support Edge topology?
• Office Communications Server server-side functions to extend Enterprise Voice to cellular phones
(Outside Voice Control)
In a migration scenario, you need to migrate Response Groups and Conferencing Services.
Response Groups
The Response Group settings, such as agent groups, queues, and workflows that you create on Lync
Server 2010, can directly migrate to Lync Server 2013. When you migrate Response Group settings, all the
configuration settings, audio files, and contact objects are moved from the Office Communications
Servers 2007 R2 pool to the Lync Server 2013 pool. Lync Server 2013 handles all calls to migrated
response group phone numbers.
To migrate Response Group settings from Office Communications Server 2007 R2 to Lync Server 2013,
you need to run a migration cmdlet and then update the Uniform Resource Locator (URL) that users need,
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-7
to log on. Clients running on the legacy client versions can use the Lync Server 2013 Response Groups,
and they need to log on manually to the Response Group webpage if they are in a Formal Agent Group.
The Response Group tab in Communicator 2007 R2 will no longer function with the Lync Server 2013
Response Groups. This could be a reason to move clients that are in a Response Group to the Lync 2013
client with priority.
Dial-in Conferencing
During migration, you must plan the timing to move dial-in conferencing services from Office
Communications Server 2007 R2 to Lync Server 2013.
Dial-in access numbers migrate in a two-step process when migrating from Office Communications Server
2007R2. You need to run the Import-CsLegacyConfiguration cmdlet to migrate dial plans and other
dial-in access number settings. When you are ready to move the dial-in conferencing services to Lync
Server 2013, you run the Move-CsApplicationEndpoint cmdlet to migrate the contact objects.
• Grant Lync Server permission to read Unified Messaging Active Directory Domain Services (AD DS)
objects.
• Create Unified Messaging IP gateways.
• Create Unified Messaging hunt groups.
Question: Can you directly migrate Response Groups from Office Communications Server
2007 R2 to Lync Server 2013?
2013. Keep this in mind when performing migrations—because you will not be able to decommission
the old OCS 2007 R2 pool as long as you have OCS 2007 R2 Mediation Servers deployed.
3. SBAs—the new 2013 SBA cannot use a Lync 2010 Pool as a backup registrar. Lync 2010 SBA can use a
Lync 2013 pool.
Users are migrated by using either Lync Control Panel or PowerShell (Move-CsUser).
If you have applications from other third-party vendors or if you developed applications within your
environment by using the Unified Communications Managed API (UCMA), the merge will also move those
customer server entries for those applications, so that they can communicate between OCS 2007 R2 and
Lync Server 2013 servers. Another consideration is when you have applications from another third-party
vendor, you can reach out to those vendors prior to migration and investigate their plans about how they
are going to implement the integration with Lync Server 2013 during the coexistence period.
It is important to know that the Move-CsLegacyUser cmdlet relies on information imported by Import-
CsLegacyConfiguration. That means that, when running Move-CsLegacyUser, you might receive an
error message informing you that you must run Import-CsLegacyConfiguration before proceeding. If
that happens, you must re-run Import-CsLegacyConfiguration before you will be able to move the
Legacy user. The parameter, ReplaceExisting, instructs Import-CsLegacyConfiguration to overwrite any
previously imported policies or settings that have changed since the last time the cmdlet was run.
For migrating user accounts:
Users can be moved with Lync Server Control Panel. If you want to use Lync Management Shell—
recommended if you move a large number of users—the following cmdlets can be used.
Move-CSLegacyuser This is the preferred command for moving users from OCS 2007 R2 pools to Lync
Server 2013 pools.
Move-CSUser This is used to move users from a Lync Server 2013 pool back to an OCS 2007 R2 pool.
Again, there will be some data loss, which is to be expected because it is not a perfect scenario, but it is a
way of recovering if something happens on the Lync Server 2013 pool that your end-users do not expect.
There are also other “move” cmdlets that you can use.
Move-CSApplicationEndpoint This is the cmdlet that your vendors will run if they need to move the
application endpoints themselves, being the contact objects stored in Active Directory. The cmdlet is also
used, when moving dial-in conferencing numbers from OCS 2007 R2 to Lync.
Move-CSRgsConfiguration This is the cmdlet that you use to move the Response Groups from your OCS
2007 R2 environment to a Lync Server 2013 pool. (This is described later, , along with what Response
Group Service (RGS) interoperability capabilities will be available to you.)
Move-CsExUmContact You use this cmdlet to move your Exchange unified messaging contact objects—
the subscriber access and the auto attendant—from OCS 2007 R2 to Lync
Move-CsConferenceDirectory You use this cmdlet to move the conference directory from OCS 2007 R2
completely to Lync, and you need to do this before decommissioning your OCS 2007 R2 pool. If you fail
to move the directory before decommissioning your pool, dial-in conferences created on the old pool will
not work anymore. If the directory is moved while you still have active users on your OCS 2007 R2 pool, a
new conferencing directory will be created on the that pool.
MCT USE ONLY. STUDENT USE PROHIBITED
12-10 Planning a Migration to Lync Server 2013
Lesson 2
Migration Steps
To design a migration strategy for Lync Server 2013, you need to examine the migration strategy for sites
and servers, the process of migrating to Lync Server 2013, and how to deactivate and migrate from Office
Communications Server 2007 R2 to Lync Server 2013.
Lesson Objectives
• Describe the migration steps.
Plan to pilot first and more than from a pool perspective. You should also include piloting the Edge Server
role in your plan.
Because you have the Edge Server and Director coupled, there are features that are specifically dependent
on Edge Server and Director. We recommend that you set up those servers so that you can see and
experience the full value of Lync Server 2013 within your pilot deployment. Keep in mind, though, that the
Director role in Lync Server 2013 is now an optional role.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-11
If you deployed Archiving Server and Monitoring Server in your Lync Server 2010 environment, you can
deploy these servers in your Lync Server 2013 environment after you migrate your front-end pools. If
archiving and monitoring functionalities are critical to your organization, you should add archiving and
monitoring to your Lync Server 2013 pilot pool before you migrate, so that the functionality is available
during the migration process.
If you deployed Group Chat Server in your legacy Lync Server 2010 environment, you must deploy Lync
Server 2013 Persistent Chat Server. Group Chat Server and Persistent Chat Server can coexist, but content
(for example, chat rooms) is not shared across these servers. To access the legacy Group Chat Server
content from Persistent Chat Server, you must migrate the Group Chat Server to Persistent Chat Server.
In general, you must use the administrative tool that corresponds to the server version that you want to
manage. You cannot install the Lync Server 2010 and the Lync Server 2013 administrative tools on the
same computer. Also, the Lync Server 2013 Control Panel is not installed automatically on each server.
Lync Server 2013 supports multisite and multi-pool deployments.
MCT USE ONLY. STUDENT USE PROHIBITED
12-12 Planning a Migration to Lync Server 2013
At this stage, Lync Server 2013 can use the existing legacy topology for routing. This includes external
remote access and federation (through the legacy Edge/Director shown), including legacy voice
components (such as legacy Mediation Servers).
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-13
The goal in this phase is to test users located in the new Lync Server 2013 pool with both the new client,
and with the legacy clients. Ensure that you point out legacy client limitations against the new pool, but
do not go into detail. Additional details are discussed in the client interoperability section, later.
Functional tests should be carried out on the newly deployed pool, to ensure the pool has been properly
deployed. Additionally, interoperability tests should be performed, to ensure users in the legacy pools can
properly interact with users in the new Lync Server 2013 pool.
Remote Access. To ensure that the users in Lync Server 2013 pools use the Lync 2013 Edge Server for
signaling, you will need to configure the clients to connect manually. Automatic configuration is
controlled through the SRV record in DNS, and you cannot use DNS to direct clients to specific Edge
Servers based on the client version. From a Media Relay Authentication Service (MRAS) perspective, the
Lync Server 2013 pool can utilize the legacy Edge deployment, or the pool can be configured to use the
new Lync 2013 Edge Server.
MCT USE ONLY. STUDENT USE PROHIBITED
12-14 Planning a Migration to Lync Server 2013
Federation. This continues to use the legacy federation route (either Office Communications Server 2007
R2 or Lync 2010).
Additional Considerations
The preceding post-migrations tasks must be
completed to ensure that there are no issues with
the new setup.
In previous versions, you could modify the behavior of the meeting join page if you wanted to allow users
to join meetings with Office Communicator 2007 R2 or Lync 2010 Attendant. However, these settings
have been deprecated in Lync Server 2013—and Lync Web App (with the media plug-in) is the preferred
client.
If your legacy deployment contained an Archiving Server or a Monitoring Server, after migrating to Lync
Server 2013, those servers can be removed from the legacy environment, provided all users have been
removed from any remaining legacy pools. You can remove the Archiving Server or Monitoring Server in
any sequence. The key requirement is that all users have been removed from any remaining legacy pools.
In a mixed environment, if you create a new trusted application server, you must set the next hop pool to
be a Lync Server 2013 pool. In a mixed environment, both the legacy Lync Server 2010 pool and the Lync
Server 2013 pool appear in the drop-down list. Selecting the legacy pool is not supported
MCT USE ONLY. STUDENT USE PROHIBITED
12-16 Planning a Migration to Lync Server 2013
Before you begin the decommissioning process, you should ensure that all users have been migrated to
Lync Server 2013. You can do this by using the Office Communications Server 2007 R2 Administration
Console. While decommissioning, the users should be located in the legacy environment.
In addition, you can use Lcscmd.exe to back up the user data in the RTC database before
decommissioning the Standard Edition front-end servers or Enterprise pools. After backing up the user
data, you need to check the output file to ensure that it contains the required data.
• In an Enterprise Edition deployment, Microsoft Office Communications Server 2007 R2, front-end
Server
• In a Standard Edition deployment, Microsoft Office Communications Server 2007 R2, Standard Edition
server
• Microsoft Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core
Redistribution package
• Microsoft Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Speech
Redistribution package
• Microsoft Office Communications Server 2007 R2, Unified Communications Managed API 2.0
Windows Workflow Activities Redistribution package
If you are removing an Edge Server, a Mediation Server, an Archiving Server, or a Monitoring Server,
remove the Office Communications Server 2007 R2 components in the following sequence:
6. Microsoft Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core
Redistribution package
If you are removing only an A/V Conferencing Server or Web Conferencing Server, remove the Office
Communications Server 2007 R2 components in the following sequence:
After uninstallation, you need to manually remove file shares used by Office Communications Server 2007
R2, and databases and log files for both Standard Edition front-end servers and Enterprise pools.
Note: Archiving and Monitoring server databases should not be deleted, unless stipulated
by organizational policy. Because you cannot transfer monitoring and archiving data from an
Office Communications Server 2007 R2 environment to the Lync Server 2013 monitoring and
archiving databases, you must retain the legacy databases if you need to access data from these
after a migration.
Based on the organizational requirements, you can re-set the legacy Office Communications Server 2007
R2 servers for other purposes.
Lesson 3
Planning for Clients and Devices
During a Lync Server 2013 migration, the major transfer is related to clients and devices. The immediate
user interaction is with software clients and hardware devices. You must plan your migration to ensure a
smooth user experience. You should also examine related considerations while planning for client and
devices, such as device support and requirements.
Lesson Objectives
• Assess detailed business requirements for clients and devices.
• Describe how to plan for client version policies for Communications Server 2007 R2 and Lync Server
2013 clients.
• If the organization has deployed multiple Microsoft Office Communication Server 2007 or Microsoft
Office Communication Server 2007 R2 pools, examine the client and device usage in each individual
pool.
• Assess whether the features in use have deprecated or been replaced in Lync Server 2013.
While migrating to a Lync Server 2013 environment, the current usage patterns and the need to maintain
them governs the business requirements of client and devices. Usually, the users transition to new clients
and hardware devices, which are updated or replaced as part of a migration. However, based on the
specific business requirements, certain groups of clients may need to retain software such as the Live
Meeting client during and after a migration.
Question: Discuss a scenario where users may need to retain the Live Meeting client on their
computers even after migrating to Lync Server 2010?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-21
Legacy Clients
In addition to the new clients and devices introduced with Lync Server 2013, you can use certain clients
from previous versions of the software, for example, Lync 2010. The version you use determines the
features available to these clients. These clients will not receive up-level functionality, even if you use them
to connect to a Lync Server 2013 environment.
Analog Phones
Lync Server 2013 provides support for analog devices. The supported analog devices are analog audio
phones and analog fax machines. Analog devices can support other analog devices such as a pagers,
modems, or teletype/telecommunication devices for the deaf or hard of hearing (TTY/TDD), but that relies
on public switched telephone network (PSTN) gateway-specific support for the device.
You can configure the analog gateways and devices in your organization to use Lync Server 2013. This
enables the analog devices to use Lync Server 2013 to make and receive calls. Lync Server 2013 makes
routing decisions and logs calls in call detail records (CDRs) for analog devices, similar to the other
devices.
Lync Server 2013 handles IM, Presence, audio/video calls, and conferencing in a single client.
As a best practice, prior to migrating users to Lync Server 2013, to enable earlier version clients to sign in
to Lync Server 2013, apply the latest cumulative updates for Office Communications Server 2007 R2,
depending on the client in your environment. While migrating users to Lync Server 2013, the primary
consideration is the handling of meetings. Because Lync Server 2013 handles meetings differently, you
must evaluate the effect it has on users, and the client software that they can use to attend meetings in a
migration scenario.
In Lync Server 2013, all newly scheduled meetings use Lync 2013 as the primary client, and have a URL
prefix of https://. During migration, Lync Server 2013 fully supports earlier meeting types:
• Previously scheduled Lync meetings from Lync 2010 move to the new pool. However, if migrating
from OCS 2007 R2, Live Meetings will not be migrated, and must be manually rescheduled.
• Users, who have migrated to the Lync Server 2013 server but are using the Lync 2010 client, can
modify and create previous Lync online meetings.
Users, who do not have Lync 2013 installed, can use the Lync Web App with the A/V plug-in.
• The personal identification number (PIN) of the user. The current PIN works until expiry or until the
user requests a new PIN.
• Meeting content. After migration, meeting organizers must reload content into their scheduled
meetings.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-23
When you first use the Online Meeting Add-in for Lync Server 2013 to schedule new meetings, a new
default conference identifier is created. The HTTP address and the conference ID, which is re-used for all
scheduled meetings, create the default conference identifier. This can be an issue for organizers, who
memorize their conference identifier and share it with others. If for any reason an organizer wants to
change his or her default conference ID, he or she can do so through the dial-in webpage (accessed
through the simple URL, for example, https://dialin.adatum.com/.)
Most meeting attendees join by clicking the join link in the new meeting invitation. However, previously
scheduled Office Communications Server 2007 R2 Live Meetings will no longer work.
• All subsequently scheduled meetings use the new meeting format, which uses an https:// address.
• In an IT-managed deployment of Lync Server 2013, the administrator can uninstall the Conferencing
Add-in for Office Outlook that schedules Live Meeting server and service-based meetings. However,
there may be users who need to continue to schedule Live Meeting service meetings. In this case, the
administrator can allow both add-ins to coexist.
• To attend Live Meeting web conferences, Lync 2013 users must install the Live Meeting client. The
instructions for installing the Live Meeting client are provided in the invitation email.
The meeting join page defaults to the Lync Web App option. In addition to this option, you can opt to
show links for Lync 2010 Attendee or a previous version of Communicator. The scenarios are as follows:
• If no Lync Server 2013 client is installed, the meeting join webpage displays the following options to
the users:
o Use Lync Web App.
MCT USE ONLY. STUDENT USE PROHIBITED
12-24 Planning a Migration to Lync Server 2013
For the scenario in which Lync 2013 is not installed, you can configure the meeting join by using the
New-CsWebServiceConfiguration or Set-CsWebServiceConfiguration Windows PowerShell cmdlets
with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink
parameters. In Lync Server 2013, however, these options have been deprecated, and Lync Web App
should be the primary client used for meeting joins.
• Allow and Upgrade. Allows the client to log on and receive updates from Windows Server Update
Service or Microsoft Update. This option is available only when user agent OC is selected. Selecting
this option causes a notification to appear the next time users sign in to Lync 2013. The notification
states that an update is available, even if updates have not yet been released to Windows Server
Update Service or Microsoft Update. To avoid confusion, you should choose this action only after
updates become available.
• Allow with URL. Allows the client to log on and provides a message to the user that indicates that the
user can upgrade their client. The message contains the URL that you specify, and the user can click
the URL to access the page to upgrade their client.
• Block and Upgrade. Prevents the Lync 2013 clients from logging on, but allows them to receive
updates from Windows Server Update Service or Microsoft Update. This option is available only for
Lync Server 2013, and where User Agent is OC.
• Block with URL. Prevents the client from logging on, and presents a message to the user that indicates
that the user is using a client that is not supported. The message comes with the URL that you specify,
and the user can click the URL to access the page represented.
installed. Each pool maintains a client version control list that you can configure. The client version list
contains the rules that specify the client versions that you want to filter and the appropriate action for
each client version. The following are the major features of Client Version Check:
• Includes a configuration option that specifies the default actions for clients. These actions are not
included in the client version control list.
• User Agent Header. Is the name of the agent for the client version.
Windows Messenger WM
• Identity. Specifies the scope within which you can apply the rule. If multiple rules with different scope
levels are triggered, you should apply the scope with the lowest level of granularity. For example, if a
service level rule states that the client should be blocked, but a user level rule states that the client
should be allowed, the client will be allowed because the user level rule is the most granular.
MCT USE ONLY. STUDENT USE PROHIBITED
12-26 Planning a Migration to Lync Server 2013
However, anonymous users are affected by global-level policies only because they are not associated
with a user, site, or service.
• Client Version Number. Includes the major version number, the minor version number, the build
number, and the Quick Fix Engineering (QFE) number. The number is presented in the following
format: <major version>.<minor version>.<build number>.<QFE number>.
• Matching Rules. Specify the comparison operations that you need to perform to identify the specific
version or range of versions of the client to which the filtering action is to apply.
• Action to Take Based on Client Version. Within this, the available values are Allow, Block, Allow with
URL, Block with URL, Allow and Upgrade, and Block and Upgrade. To install a new client, local
administrator credentials are required.
• Client Download URL. Is used only for the Block with URL and Allow with URL options.
• Refer to the Office Communications Server 2007 R2/Lync 2010 Monitoring Server reports.
By determining the client versions that are currently in use, you can also uncover clients running very old
versions of Office Communications Server client software in your environment. If you identify such clients,
you need to bring these clients into compliance before starting a migration to Lync Server 2013.
When migrating your users to Lync Server 2013, you need to plan for deploying the new client software
to these users. Depending on the requirements of the organization, you can do this planning for selected
groups of users as they are migrated, or after completing the migration of all users. However, in both
cases, you can use client version policies to support your client software rollout.
After deploying Lync 2013 client software, you can build policies that disallow using the earlier versions of
clients outright, or direct these to download the links for updated client software. These policies are
especially useful for clients that are not managed, such as workstations that are not Active Directory
members, or may not be reachable by your normal software distribution framework, such as System
Center Configuration Manager.
When you complete the migration of all users to Lync Server 2013 and they start using Lync 2013 client
software, you need to adjust the client version policy to deny connections from all previous version clients.
This ensures that you do not risk a forgotten previous version client connecting to your environment and
potentially causing compatibility problems for the user.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-27
Question: Can you use client version policies to automatically update clients running specific
software versions?
• Provide basic and advanced phone features, including new voice features such as Enhanced 9-1-1
(E9-1-1) and the Call Park application
• Provide voice connections to Lync Server 2013 and Live Meeting Sessions (hosted on a Live Meeting
Service, or older Office Communications Server 2007 R2 pool only)
• Can access contacts, conversation history, and calendar information stored in Microsoft Exchange
email
Lync Server 2013 supports IP and USB phone devices. Lync Server 2013 also supports analog devices, but
they are not connected directly to Lync Server 2013. Analog devices are connected through supported IP-
PSTN gateways with analog ports.
• Conferencing Devices. Are hands-free IP or USB phones that are used in meeting rooms.
• Common Area Phones. Are handset IP phones that are used in shared areas such as lobbies, kitchens,
factory floors, and shared workspaces. You can customize these phones to provide different sets of
Lync Server 2013 features.
When planning to support devices in Lync Server 2013, only the IP phone devices have specific
requirements in relation to the infrastructure in which they are deployed. For Lync Server 2013 software
clients, USB phone devices basically function as headsets, and they do not require additional deployment
considerations, other than the ones done for the software clients themselves.
• Web Services. On each front-end server, the Device Update Service runs as a web service. You can
share the configuration between all front-end servers in the pool, but cannot replicate between pools
or Standard Edition servers.
MCT USE ONLY. STUDENT USE PROHIBITED
12-28 Planning a Migration to Lync Server 2013
• Enterprise Voice. If you want a Lync Server 2013 user to use a phone device, you need to enable the
user for Enterprise Voice. Also, like any Enterprise Voice deployment, you need to configure and test
the dial plans, voice policies, and outbound call routes before deploying Lync Server 2013 phone
devices.
• Contact Objects for Common Area Phones. You need to associate the phones that are not locked for
specific users, with a Microsoft Active Directory contact object. Similar to user accounts, you can
assign policies and voice plans to contact objects, thereby providing a method to manage the device.
• PIN Authentication and Policy. For deploying phones from the line of IP phones designed for Lync
Server 2013, you need to enable personal identification number (PIN) authentication on Lync Server
2013. You also need to have an appropriate PIN policy that allows automatic authentication on user
sign-in with a number of IP phones.
System and Infrastructure Requirements for Lync Server 2013 Phone Devices
When you deploy Lync 2013 phone devices, aside from the configuration within Lync Server 2013 itself,
the environment hosting the Lync Server 2013 servers and clients must also provide specific functionality.
You need to accommodate this functionality in your planning for device deployment:
When planning for the deployment of Lync phone devices, ensure that PoE is available in the locations
where you will be placing Lync 2013 IP phone devices. For this, you will need to clarify the requirements
with the network teams of the organization where you are deploying Lync Server 2013. Although you can
use a traditional power supply for each IP phone, it is much more convenient if PoE is available on the
network.
DNS Requirements
With regard to server discovery and sign-in, the Lync 2013 phone devices use the same DNS records as a
normal Lync 2013 client, and these are A and service (SRV) records.
However, for some older devices to receive device updates, you might need a separate A record, by using
the following code.
Additionally, you need to recognize that the DNS requirements for Lync 2013 phone devices are the same
as Lync Server 2010. As a result, many of these entries may already exist in the current environment when
performing a migration.
In Lync Server 2013 connectivity, you can use the following DHCP options:
• Option 120 (SIP servers). It is defined in RFC 3361 and is used to return a list of SIP servers.
• Option 43. It is a complicated option and has many sub-options, and sometimes many values. The
effective value for option 43 is the Lync Pool Certificate Provisioning Service URL. You can use the
utility, DHCPUtil.exe, to assist with configuring this option on your Windows DHCP servers.
• If you use a DHCP server that is included with the Lync Server 2013 Registrar, it results in unneeded
packets being sent to an additional DHCP server. Because there is no participation of DHCP in the
address acquisition process, these types of packets will be ignored.
• If you enable the DHCP server by using the Registrar, it adds one more responsibilities to the front-
end server or Director role. This can potentially affect the performance and the core functionality of
Windows Server.
• Ask for Option 120 or 43 by using the parameter request list of option 55.
If a branch office does not have an Enterprise DHCP server, you need the Registrar running the DHCP
server because of the following reasons:
• Because the branch does not have an Enterprise DHCP server, it relies on DHCP functionality provided
by routers. It is therefore not possible to configure DHCP options on these.
• All UC devices can be in the same subnet, depending on the branch size. In such a case, you do not
require relay configuration. However, if there are multiple subnets, it is likely that they are not many
in number and reconfiguration is manageable.
MCT USE ONLY. STUDENT USE PROHIBITED
12-30 Planning a Migration to Lync Server 2013
• You can more easily enable DHCP on the Registrar in comparison to configuring and deploying an
Enterprise DHCP server for the vender-specific Lync Server DHCP options.
Certificates
While deploying Lync Server 2013 phone devices, you need to ensure that the devices trust the certificates
presented by Lync Server 2013 and Microsoft Exchange Server Unified Messaging. For this, typically, you
will need to get the Root Certificate of your internal certificate authority on to the device.
However, when you migrate from Office Communications Server 2007 R2/Lync 2010 and have been using
Office Communicator 2007 R2/Lync 2010 Phone Edition devices, you already have the necessary
components in place for phone devices to function.
There are several ways in which you can import a Root Certificate on a Lync 2013 phone device. The most
used method involves adding the Root Certificate to the caCertificate attribute in Active Directory. You
can do this by running the following command.
However, for this method to work, you need to have the Root Certificate available in .cer format.
This method can make the Root Certificate available to the Lync 2013 phone devices, which are then able
to sign in to your environment.
When you use public certificates for your internal Lync Server 2013 deployment, you need to ensure that
the public certificate provider is one that the Lync 2013 phone devices support. This is because you would
not want to publish a third-party root certificate in the same manner as described above. You can get a
list of the supported public certificate authorities for Lync Phone Edition by referring to the Lync Server
2013 documentation.
You need to take into account a number of considerations in your Lync Server 2013 deployment to
deploy Lync phone devices. Even if you may have a well-functioning deployment that uses Lync software
clients, it does not guarantee that the deployment has been properly prepared for Phone Edition
deployment.
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-31
Lesson 4
Designing a Client Migration and Device Migration
Strategy
There are several considerations that you must examine while designing Group Policy, and policies and
devices. You should also know how to design a software deployment strategy, and the best practices for
migrating clients, devices, and users.
Lesson Objectives
• Design Group Policy.
• Describe the best practices for client, device, and user migrations.
If you have an existing Office Communications Server 2007 R2 deployment, Office Communications Server
2007 R2 clients will continue to use Group Policy during side-by-side migration. However, if you want
policy settings to be applied to Lync Server 2013 clients, you need to configure the equivalent Lync Server
2013 in-band provisioning settings.
When designing your migration to Lync Server 2013, you should review the Group Policy settings that are
used for client configuration in the legacy environment. You can then use these as a starting point for
choosing the in-band configuration settings, or build new client configuration settings. However, you
should evaluate the Group Policy settings before migrating clients and users. If you make changes to the
way the clients are configured on the Lync Server 2013 environment, you must communicate these
changes to users as a part of migration planning.
Although Lync Server 2013 transfers most client configurations to in-band provisioning, there are a
number of Group Policy settings that are required for client bootstrapping. These are policies that take
effect before the client logs on and begins receiving in-band provisioning settings from the server.
Because Office Communicator 2007 R2 client bootstrapping policies are used by Lync 2013, it is only
necessary to configure them if you want to change existing policies or if you want to set new policies. If
MCT USE ONLY. STUDENT USE PROHIBITED
12-32 Planning a Migration to Lync Server 2013
you do not plan to configure client bootstrapping policies or you want legacy client bootstrapping
policies to remain in effect, no action is necessary.
There are several advantages to the Lync Server 2013 approach of using in-band provisioning, instead of
Group Policy, when configuring clients. The following table compares the two types of client
configurations.
Administrators can handle all client Administrators must often work with other
configuration tasks in a single location, by departments in the organization. For
using a single user interface. example, administrators manage Active
Directory Domain Services (AD DS) or
messaging to configure clients.
Settings can be configured at the global Settings can only be configured at the
level, that is, domain or organizational unit. global and user levels.
Settings can also be configured at the site
or tag level.
In-band provisioning settings that are Group Policy settings that are distributed
server-based provide a consistent end-user by using Active Directory require that users
experience for people who are not joined be connected to the corporate domain by
to the corporate domain, or for people using a computer.
who join by using devices or remote
clients.
Settings take effect at the Lync sign-in. Users must log off from the Windows
operating system and then log back on for
settings to take effect.
You should aim to move all clients to Lync Server 2013 client software as part of your migration plan. This
will give users a better experience and will allow them to use the full Lync Server 2013 feature set, which is
not available when using legacy client software.
To design your Group Policies and in-band provisioning settings, you should:
• Evaluate current Group Policy settings for Lync 2010 or Office Communicator 2007 R2 configuration.
• You should also evaluate organizational requirements with the project stakeholders before deciding
on the client configuration for your Lync Server 2013 deployment. Even though you may be
migrating from an earlier version of Office Communications Server, organizational requirements
might have evolved or changed since that version’s configuration was designed and implemented.
Question: Why are some Group Policy settings still required for Lync Server 2013 clients
when you can use in-band provisioning?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-33
When you design policies for phone devices, you should consider the following:
• The usage profile of the phone devices for which you are designing the policies.
• The physical locations where the devices will be located.
You will normally deploy user policies for common area phones, because you do not want a general site
or even global policy applied to these devices. Common area phones require special considerations,
because these may be placed in locations where non-organizational staff can access them. For example,
you may have a common area phone placed in a lobby or reception area, and such a phone would
normally be locked down through policies, so that a person using the phone in the lobby would not be
able to access conferences by using this device.
The Device Update Service is a web service that runs on all front-end servers, and is used to provide
firmware or software updates to Lync 2013 Phone Edition devices.
When deployed in a front-end pool, the service configuration is shared between the servers in the pool,
but not between pools, or between Standard Edition servers.
In versions earlier to Office Communications Server 2007, it was a challenging task to install and configure
the Device Update Service. However, in Office Communications Server 2007 R2, the Device Update Service
became an integral part of the server infrastructure, and this is carried forward with Lync Server 2010 and
2013.
When designing your Lync Server 2013 infrastructure, you need decide about how to use the Device
Update service in your environment. For this, you need to consider the following:
• The makes and models of devices that you will be deploying. Because you must download updates for
each specific Lync 2013 Phone Edition device manually to your Device Update Service, you may want
MCT USE ONLY. STUDENT USE PROHIBITED
12-34 Planning a Migration to Lync Server 2013
to limit the amount of different devices that you deploy on each front-end pool or Standard Edition
server.
• The devices of each type that should be deployed as test devices. You should designate at least one test
device for each type of device that you deploy in your environment. This test device will enable you
to try new firmware releases before applying them to the rest of the devices in your environment.
• Supporting devices located outside your corporate network. If you are supporting devices outside your
network, you need to ensure that devices can connect to the Device Update Service from outside
your corporate network.
Considering these, you should be able to design and implement a successful Device Update Service in
your Lync Server 2013 environment.
Question: If you have several front-end server pools or Standard Edition servers, can you
manage the Device Update Service on a global level?
• Remote control—Of clients by IT administrators who install the software for the user.
• The Lync 2013 client will not uninstall any existing Office Communicator 2007 R2/Lync 2010 client as
part of its installation routine.
For remote clients, new remote access solutions such as Microsoft Unified Access Gateway (UAG)
DirectAccess may be used to enable you to distribute Lync 2013 clients to remote, domain-joined clients
in the same manner as with your in-house clients.
When you start migrating users to Lync Server 2013, you may need to ensure that the migrated users
have access to Lync 2013 Web App, or Lync 2013 Attendee to attend meetings hosted on Lync Server
2013.
Question: Are you required to deploy Lync Server 2013 client software by using software
distribution solutions such as System Center Configuration Manager?
Live Meeting
In Lync Server 2010, a service existed called the
Lync Web Conferencing Compatibility Service,
which was essentially the Live Meeting MCU from
OCS 2007 R2. It would service any Legacy on-
premise Live Meetings that were created in the
OCS/OCS 2007 R2 environments. However, Lync
Server 2013 does not contain this service. As such,
Legacy Live Meetings (that start with meet://) will
no longer work.
• Be aware that using the Lync 2013 client with earlier versions of Office Communications Server is
unsupported.
• Ensure that users can participate in meetings hosted on Lync Server 2013.
• Make Lync 2013 Web App available to non-Windows clients.
• Do not remove Live Meeting clients as part of your Lync client rollout.
• If possible, move users who organize and participate in conferences with each other.
• Perform pilot migration of users, clients, and devices to Lync Server 2013.
• Use pilot migrations as trial runs to adjust and prepare for full-scale migrations.
• Ensure consistent security update levels for clients and devices across your deployment.
• Use client version policies to block unwanted client versions in your environment before, during, and
after migration.
Question: Why should you avoid removing the Live Meeting client by default when rolling
out the Lync Server 2013 client software?
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-37
2. List the phases of migration from Lync Server 2010 to Lync Server 2013.
Task 1: List the phases of migration from Office Communications Server 2007 R2 to
Lync Server 2013.
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
MCT USE ONLY. STUDENT USE PROHIBITED
12-38 Planning a Migration to Lync Server 2013
Phase 7
Phase 8
Phase 9
Phase 10
Task 2: List the phases of migration from Lync Server 2010 to Lync Server 2013.
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
Phase 6
Phase 7
Phase 8
MCT USE ONLY. STUDENT USE PROHIBITED
Core Solutions of Microsoft® Lync® Server 2013 12-39
When migrating from Office Communications Server 2007 R2 to Lync Server 2013, any time you
add or remove servers in the Office Communications Server 2007 R2 environment, you must start
Topology Builder and run the Merge Office Communications Server 2007 R2 topology data into
the Central Management Store. Then, publish the topology to update Lync Server 2013 about the
changes.
Microsoft Lync Server 2013 Control Panel and the Move-CsLegacyUser cmdlet require that user
names are properly formed and do not have leading or trailing spaces. You cannot move a user
account by using Lync Server 2013 Control Panel or the Move-CsLegacyUser cmdlet if the user
account contains leading or trailing spaces. Ensure that your user accounts meet this
requirement.
Locating users on Lync Server 2013 does not require that you deploy upgraded clients at the
same time. New functionality will be available to users only when they have upgraded to the new
client software. If migrating from Lync Server 2010 to Lync Server 2013, you can deploy Lync
2013 clients first, before deploying Lync Server 2013 pools because Lync 2013 clients work
against Lync Server 2010, provided the appropriate Lync Server 2010 cumulative updates have
been deployed.
Review Question(s)
Question: Which Event Source and ID can you filter on, when verifying user replication
during migration?
Question: When you configure and enable front-end pool pairing for disaster recovery, what
additional Lync service is installed?
Question: When migrating users of Lync Server 2013 to Microsoft Exchange 2013, you can
use both Exchange storage and Lync Server storage on an interim basis, while you complete
the migration. When is permanent use of both Exchange and Lync Server storage enabled for
Lync Server 2013?
Question: In Lync Server 2013, after a migration from Communications Server 2007 R2, what
actions can you perform with Live Meeting conferences?
Question: What is the first step in preparing for any migration after the planning phase is
complete?
Answer:
They should first complete the migration to Lync Server 2010 as a tri-existence scenario is not supported.
Contoso migrated from Office Communications Server 2007 to Office Communications Server 2007 R2,
but never migrated the Office Communications Server Global Settings from the Systems container to the
Configuration container in Active Directory Domain Services. Can they migrate to Lync Server 2013?
Answer:
Yes. However, they may have to run some cmdlets from the Lync Server Management Shell during the
Active Directory Preparation because they assume that the global settings are stored in the Configuration
container.
MCT USE ONLY. STUDENT USE PROHIBITED
12-40 Planning a Migration to Lync Server 2013
Course Evaluation
Your evaluation of this course will help Microsoft understand the quality of your learning experience.
Please work with your training provider to access the course evaluation form.
Microsoft will keep your answers to this survey private and confidential and will use your responses to
improve your future learning experience. Your open and honest feedback is valuable and appreciated.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-1
To begin this lab, you must start and connect to the appropriate virtual machines by using the
following steps in this specific order:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-02, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-02, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-02, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-02, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-02, is not running:
a. First ensure that 20336B-LON-SQL1-02 has booted completely before starting this virtual
machine.
8. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-02, is not running:
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-02, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-02, is not running:
a. First ensure that 20336B-RED-SQL1-02 has booted completely before starting this virtual
machine.
12. On Host2, when 20336B-RED-CL1-02 has booted up completely, close the Virtual Machine
Connection window.
13. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
14. In the Remote Desktop Connection window, click Options.
15. Click the Local Resources tab, and then, under Remote audio, click Settings.
16. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
17. Under Remote audio recording, click Record from this computer, and then click OK.
22. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Connect.
23. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK, click Yes.
24. On Host1, when 20336B-LON-CL1-02 has booted up completely, close the Virtual Machine
Connection window.
25. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
26. In the Remote Desktop Connection window, click Options.
27. Click the Local Resources tab, and then, under Remote audio, click Settings.
28. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
29. Under Remote audio recording, click Record from this computer, and then click OK.
33. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box (if it appears), and then click Connect.
34. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
3. If not, right-click the service, and then click Start.
Important Note All connections to LON-CL1-02 and RED-CL1-02, and will require using a Remote
Desktop Connection with remote audio playback and remote audio recording enabled, unless
otherwise specifically stated.
Install Software:
2. On the Microsoft Lync Server 2013 pop-up answer yes to the question if to install the Microsoft Visual
C++ runtime.
3. On the Installation Location page, leave the default location, and then click Install.
4. On the End User License Agreement page, select the I accept the terms in the license agreement
check box, and then click OK.
Note: Wait as the wizard runs the commands to prepare the schema.
Note: Wait as the wizard runs the commands to prepare the forest.
13. On the Prepare Active Directory for Lync Server page, next to Step 5: Prepare Current Domain, click
Run.
Note: Wait as the wizard runs the commands to prepare the domain.
15. When the Task Status shows as Completed, click Finish.
2. In the Active Directory Users and Computers administrative snap-in, in the navigation pane, expand
ADatum.com, and then click the Users container.
3. In the Results pane, right-click the CSAdministrator group, and then click Properties.
4. On the CSAdministrator Properties page, click the Members tab, and then click Add.
5. On the Select Users, Contacts, Computers, Service Accounts, or Groups page, in the Enter the object
names to select box, type Administrator, and then click OK.
6. On the CSAdministrator Properties page, click OK.
7. Close the Active Directory Users and Computers Microsoft Management Console (MMC).
3. Right-click the LyncShare folder, and then select Share with, specific People…
4. Ensure that Administrator is listed as read/write and Administrators group is listed as Owner.
5. Click Share, and then click Done.
Results: After completing this exercise, you should have prepared Active Directory for an installation of
Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-5
4. On the Topology Builder page, click New Topology, and then click OK.
5. In the Save New Topology As window, navigate to the desktop and save the topology as Lab2.tbxml.
6. On the Define the primary domain page, in the Primary SIP Domain box, type ADatum.com, and then
click Next twice.
7. On the Define the first site page, in the Name box, type London (Site 0), and then click Next.
8. On the Specify site details page, in the City box, type London.
9. In the Country/Region Code box, type +44, and then click Next.
10. On the New topology was successfully defined page, verify that Open the New Front End Wizard
when this wizard closes is selected, and then click Finish.
11. On the Define New Front End Pool wizard, on the Define the New Front End pool page, click Next.
12. On the Define the Front End pool FQDN page, in the Pool FQDN box, type lon-pool.ADatum.com.
Verify that Enterprise Edition Front End Pool is selected, and then click Next.
13. On the Define the computers in this Pool page, in the Computer FQDN box, type lon-
fe01.adatum.com, click Add, and then click Next.
14. On the Select Features page, select the Conferencing(includes audio, video and application sharing),
Dial in (PSTN) conferencing, Enterprise Voice and Call Admission Control check boxes, and then click
Next.
15. On the Select collocated server roles page, select the Collocate Mediation Server check box, and then
click Next.
16. On the Associate server roles with this Front End pool page, clear all check boxes, and then click
Next.
17. On the Define the SQL store page, click New, and then, in the SQL Server FQDN box, type Lon-
SQL01.ADatum.com.
20. On the Define the file store page, click Define a new file store, and then, in the File Server FQDN
box, type Lon-SQL01.adatum.com.
21. In the File Share box, type LyncShare, and then click Next.
22. On the Specify the Web Services URL page, select the Override Internal Web Services Pool FQDN
checkbox. Then, in the box, type lon-poolweb-int.adatum.com, in the External Base URL, update the
URL to lon-poolweb-ext.adatum.com, and then click Next.
23. On the Select an Office Web Apps Server page, clear the Associate pool with an Office Web Apps
Server check box, and then click Finish.
24. In the Topology Builder right-click Lync Server, and then select New Central Site.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-6 Core Solutions of Microsoft® Lync® Server 2013
25. On the Define new central site page, in the Name box, type Redmond (Site 1), and then click
Next.
26. On the Specify site details page, in the City box, type Redmond.
27. In the Country/Region Code box, type +1, and then click Next.
28. On the Central site was successfully defined page, verify that Open the New Front End Wizard when
this wizard closes is selected, and then click Finish.
29. On the Define New Front End Pool wizard, on the Define the New Front End pool page, click Next.
30. On the Define the Front End pool FQDN page, in the Pool FQDN box, type red-pool.ADatum.com.
Verify that Enterprise Edition Front End Pool is selected, and then click Next.
31. On the Define the computers in this Pool page, in the Computer FQDN box, type red-
fe01.adatum.com, click Add, and then click Next.
32. On the Select Features page, select the Conferencing(includes audio, video and application sharing),
Dial in (PSTN) conferencing, Enterprise Voice and Call Admission Control check boxes, and then click
Next.
33. On the Select collocated server roles page, select the Collocate Mediation Server check box, and then
click Next.
34. On the Associate server roles with this Front End pool page, clear all check boxes, and then click
Next.
35. On the Define the SQL store page, click New , and then, in the SQL Server FQDN box, type Red-
SQL01.ADatum.com
37. Clear the this SQL instance is in mirroring relation check box, click OK, and then click next.
38. On the Define the file store page, click Define a new file store, and then, in the File Server FQDN
box, type Red-SQL01.adatum.com.
39. In the File Share box, type LyncShare, and then click Next.
40. On the Specify the Web Services URL page, select Override Internal Web Services Pool FQDN
checkbox. Then, in the box, type red-poolweb-int.adatum.com, in the External Base URL, update the
URL to red-poolweb-ext.adatum.com, and then click Next.
41. On the Select an Office Web Apps Server, clear the Associate pool with an Office Web Apps Server
check box, and then click Finish.
2. On the Edit Properties page, under Simple URLs, in the Administrative access URL box, type
https://lyncadmin.adatum.com.
3. In the Central Management Server Section, use the drop-down menu to select the lon-
pool.adatum.com London (Site 0) as the front-end server on which to install central management
server, and then click OK.
Results: After completing this exercise, you should have created and edited a publishable topology.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-7
2. On the Publish topology page, review the actions that will be performed, and then click Next.
3. On the Select Central Management Server, verify that the lon-pool.adatum.com London (Site 0) is
selected, and then click Next.
4. On the Create databases page, verify that both the lon-sql01.adatum.com and the red-
sql01.adatum.com are selected, and then click Next.
5. On the Publishing wizard complete page, verify that all steps show as Success. If any step finishes
with completed with warnings, review these warnings to verify that they are not serious. SQL Server
might generate an error about Setting SQL Server Show Advanced Options to 1.
6. Under Next steps, click the link to open the to-do list.
7. Review the NextSteps.txt file that opens and the instructions to run local setup on each server in the
list, and then close Notepad.
Results: After completing this exercise, you should have a published topology.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-8 Core Solutions of Microsoft® Lync® Server 2013
2. In DNS Manager, expand LON-DC1, expand Forward Lookup Zones, and then click ADatum.com.
3. Right-click ADatum.com, and then click New Host (A or AAAA).
5. In the IP Address box, type 172.16.0.31, and then click Add Host.
6. At the DNS prompt, click OK.
8. In the IP Address box, type 172.16.0.31, and then click Add Host.
9. At the DNS prompt, click OK.
10. In the New Host window, in the Name box, type lon-poolweb-int.
11. In the IP Address box, type 172.16.0.31, and then click Add Host.
12. At the DNS prompt, click OK.
13. In the New Host window, in the Name box, type lyncadmin.
14. In the IP Address box, type 172.16.0.31, and then click Add Host.
15. At the DNS prompt, click OK.
16. In the New Host window, in the Name box, type lyncdiscoverinternal.
17. In the IP Address box, type 172.16.0.31, and then click Add Host.
18. At the DNS prompt, click OK.
19. In the New Host window, in the Name box, type meet.
20. In the IP Address box, type 172.16.0.31, and then click Add Host.
22. In the New Host window, in the Name box, type red-pool.
23. In the IP Address box, type 172.16.1.31, and then click Add Host.
24. At the DNS prompt, click OK.
25. In the New Host window, in the Name box, type red-poolweb-int.
26. In the IP Address box, type 172.16.1.31, and then click Add Host.
27. At the DNS prompt, click OK, and then click Done.
29. In the Select a resource record type window, click Service Location (SRV), and then click Create
Record.
34. In the Host offering this service text box, type lon-pool.ADatum.com, and then click OK.
35. In Select a resource record type window, click Service Location (SRV), and then click Create Record.
38. Leave the Priority entry at the default. Enter 10 for Weight.
40. In the Host offering this service text box, type red-pool.ADatum.com, and then click OK.
2. On the Lync Server 2013 - Deployment Wizard page, click Install or Update Lync Server System.
3. On the Lync Server 2013 - Deployment Wizard page, next to Step 1: Install Local Configuration Store,
click Run.
4. On the Configure Local Replica of Central Management Store page, verify that Retrieve directly from
the Central Management Store is selected, and then click Next. This step will take about 10 minutes
to execute.
5. On the Executing Commands page, when the Task Status shows Completed, click Finish.
3. On the Executing Commands page, when the Task status shows Completed, click Finish.
2. In the Certificate Wizard window, select the Default Certificate, and then click Request.
6. On the Certification Authority Account page, leave the box clear, and then click Next.
7. On the Specify Alternate Certificate Template page, leave the box clear, and then click Next.
8. On the Name and Security Settings page, in the Friendly Name box, type LON-FE01 Lync Server
Certificate, and then click Next.
11. On the Geographical Information page, in the Country/Region drop-down list, click United Kingdom.
14. On the Subject Name/Subject Alternate Names page, review the Subject Name and Subject
Alternative Names automatically populated, and then click Next.
15. On the SIP Domain setting on Subject Alternate Names page, select the ADatum.com check box, and
then click Next.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-11
16. On the Configure Additional Subject Alternate Names page, leave the fields blank, and then click
Next.
19. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
22. On the Executing Commands page, when the Task Status shows Completed, click Finish.
23. On the Certificate Wizard, click the down arrow next to Default Certificate to expand the Certificate
Type.
24. Verify that Server Default, Web Services Internal, and Web Services External all show as Assigned.
25. In the Certificate Wizard window, select the OAuthTokenIssuer, and then click Request.
26. On the Certificate Request page, click Next.
27. On the Delayed or Immediate Requests page, verify that Send the request immediately to an online
certification authority is selected, and then click Next.
28. On the Choose a Certification Authority (CA) page, verify that LON-DC1.adatum.com\adatum-lon-
dc1-ca is listed, and then click Next.
29. On the Certification Authority Account page, leave the box clear, and then click Next.
30. On the Specify Alternate Certificate Template page, leave the box clear, and then click Next.
31. On the Name and Security Settings page, in the Friendly Name box, type Adatum OAUTH Certificate,
and then click Next.
32. On the Organization Information page, in the Organization box, type A Datum.
33. In the Organizational Unit box, type IT, and then click Next.
34. On the Geographical Information page, in the Country/Region drop-down list, click United Kingdom.
35. In the State/Province box, type England.
36. In the City/Locality box, type London, and then click Next.
37. On the Subject Name/Subject Alternative Names page, review the Subject Name that is
automatically populated, and then click Next.
38. On the Configure Additional Subject Alternate Names page, leave the fields blank, and then click
Next.
40. On the Executing Commands page, when the Task Status shows Completed, click Next.
41. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
45. On the Certificate Wizard, click the down arrow next to OAuthTokenIssuer to expand the Certificate
Type.
3. On the Installation Location page, leave the default location, and then click Install.
4. On the End User License Agreement page, select the I accept the terms in the license agreement
check box, and then click OK.
5. On the Lync Server 2013 - Deployment Wizard page, click Install or Update Lync Server System.
6. On the Lync Server 2013 - Deployment Wizard page, next to Step 1: Install Local Configuration
Store, click Run.
7. On the Configure Local Replica of Central Management Store page, verify that Retrieve directly
from the Central Management Store is selected, and then click Next.
8. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
3. On the Executing Commands page, when the Task status shows as Completed, click Finish.
2. In the Certificate Wizard window, select the Default Certificate, and then click Request.
3. On the Certificate Request page, click Next.
4. On the Delayed or Immediate Requests page, verify that Send the request immediately to an
online certification authority is selected, and then click Next.
6. On the Certification Authority Account page, leave the box clear, and then click Next.
7. On the Specify Alternate Certificate Template page, leave the box clear, and then click Next.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-13
8. On the Name and Security Settings page, in the Friendly Name box, type RED-FE01 Lync Server
Certificate, and then click Next.
11. On the Geographical Information page, in the Country/Region drop-down list, click United States.
14. On the Subject Name/Subject Alternative Names page, review the Subject Name and Subject
Alternative Names automatically populated, and then click Next.
15. On the SIP Domain setting on Subject Alternate Names (SANs) page, select the ADatum.com check
box, and then click Next.
16. On the Configure Additional Subject Alternative Names page, leave the fields blank, and then click
Next.
17. On the Certificate Request Summary page, click Next.
18. On the Executing Commands page, when the Task Status shows as Completed, click Next.
19. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
23. On the Certificate Wizard, click the down arrow next to Default Certificate to expand the Certificate
Type.
24. Verify that Server Default, Web Services Internal, and Web Services External all show as Assigned.
3. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
4. On the Lync Server 2013 – Deployment Wizard page, click Exit.
Results: After completing this exercise, you should have a configured Lync Server 2013 deployment.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-14 Core Solutions of Microsoft® Lync® Server 2013
2. When prompted for logon credentials, use adatum\administrator, with the password, Pa$$w0rd
3. On the Exchange admin center webpage, select Unified Messaging.
4. On the Unified Messaging webpage, click the + sign to create a New UM Dial Plan.
5. Under name, enter ADatum london, under extension length, enter 3, under Dial Plan Type, select SIP
URI, under VOIP Security Mode, select Secured, leave the Audio Language on English (United
States), change Country/Region Code to 4, and then click Save.
6. On the Unified Messaging webpage, click the + sign to create a New UM Dial Plan.
7. Under name, enter ADatum Redmond, under extension length, enter 3, under Dial Plan Type, select
SIP URI, under VOIP Security Mode, select Secured, leave the Audio Language on English (United
States), change Country/Region Code to 1, and then click save.
8. On LON-EX01, click start, and then click Exchange Management Shell
9. To associate the dial plans to the Exchange UM Server, type the following cmdlet, and then press
Enter.
10. Type the following cmdlet, and then press Enter, to enable the service with TLS and TCP in the
Exchange Management Shell.
11. Type the following cmdlet in Exchange Management Shell, then press enter, and when prompted,
type Y, and then press Enter, to enable the certificate for usage with Exchange UM.
12. Type the following command in Exchange Management Shell, and then press Enter, to restart the
Exchange UM server.
restart-service msexchangeUM
13. Type the following cmdlet in Exchange Management Shell to enable the UM Call Router Service for
TLS.
14. Type the following cmdlet in Exchange Management Shell, then press enter, and when prompted,
type Y, and then press Enter, to assign the Certificate to the UM Call Router Functionality.
15. Type the following cmdlet in Exchange Management Shell, and then press Enter, to assign the UM
Call Router to the dial plans.
16. Type the following cmdlet in the Exchange Management Shell, and then press Enter, to restart the
Exchange UM Call Routing Service.
restart-service msexchangeumcr
17. In Exchange Management Shell, type cd $exscripts, press Enter, then type .\ExchUCUtil.ps1, and
then press Enter.
18. After running the script, again type .\ExchUCUtil.ps1 in Exchange Management Shell, and then press
Enter. Verify that the script ends with the red-pool and the lon-pool being associated with an
UMIPGateway and two DialPlans each.
2. In OCSUMUtil, click the load data button and verify that both ADatum London and ADatum
Redmond are listed.
Task 3: Enable users for Lync Enterprise Voice and Exchange UM.
1. On Lon-FE01, click start, and then click Lync Server Control Panel.
2. Select https://lon-poolweb-int.adatum.com/Cscp and log on as adatum\administrator, with password,
Pa$$w0rd.
3. Select users on the left menu, and then click enable users.
4. Click the add button in the new Lync Server user panel, then click add filter.
5. In the first dropdown box, select Department. In the second dropdown box, select equal to. In the
textbox, type Sales, and then press Find.
6. Click on the first user, and use control-A to select all of the users from the search results. Click OK.
7. On the assign users to a pool drop-down box, select lon-pool.adatum.com, change the telephony
drop-down box to Enterprise Voice, and then click Enable in the upper-left corner.
8. After all users have been enabled, return to the Microsoft Lync Server 2013 Control Panel. Double-
click Aaren Ekelund.
9. Navigate to the Line URI and enter tel:+44555555111;ext=1111, and then click commit.
10. On Lon-FE01, click start and click Internet Explorer (if Windows Internet Explorer 10 message
appears, click Ask me later), and navigate to https://lon-ex01.adatum.com/ecp/. Log on as
adatum\administrator, with password, Pa$$w0rd.
11. Navigate to the recipients page on the left and click the looking glass to search for sales.
12. Select the mailbox of aaren ekelund and then click the pen symbol. In the pop-up window, select
mailbox features and scroll down until you see “Phone and Voice Features”. Unified Messaging will
appear as disabled. Click enable.
13. In the new pop-up window, click browse, select the ADatum London Default Policy, click OK, and
then click next. As an extension number, type 111. Do not change any other options and click Finish.
In the still open user edit dialog box, click Save.
MCT USE ONLY. STUDENT USE PROHIBITED
L2-16 Core Solutions of Microsoft® Lync® Server 2013
MCT USE ONLY. STUDENT USE PROHIBITED
L3-1
To begin this lab, you must start and connect to the appropriate virtual machines by using the
following steps:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
a. Right-click 20336B-LON-CL1-03, and then click Start.
b. Right-click 20336B-LON-CL1-03, and then click Connect.
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
MCT USE ONLY. STUDENT USE PROHIBITED
L3-2 Core Solutions of Microsoft® Lync® Server 2013
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
b. Right-click 20336B-RED-FE1-03, and then click Start.
13. On Host2, when 20336B-RED-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
14. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
15. In the Remote Desktop Connection window, click Options.
16. Click the Local Resources tab, and then, under Remote audio, click Settings.
17. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
18. Under Remote audio recording, click Record from this computer, and then click OK.
21. In the User name box, type Adatum\Alex, and then click Connect.
23. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
24. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
25. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
26. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
27. In the Remote Desktop Connection window, click Options.
MCT USE ONLY. STUDENT USE PROHIBITED
L3-3
28. Click the Local Resources tab, and then, under Remote audio, click Settings.
29. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
30. Under Remote audio recording, click Record from this computer, and then click OK.
33. In the User name box, type Adatum\Adam, and then click Connect.
35. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
36. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
Important Note Verify that all services set to Automatic have started on all virtual machines. Most
notably, check the Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do
so, complete the following steps:
37. On each virtual machine, open Server Manager, click Tools, and then click Services.
38. In the Services console, verify that all services set to Automatic start have started.
39. If not, right-click the service, and then click Start.
Important Note All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote
Desktop Connection with remote audio playback and remote audio recording enabled, unless
otherwise specifically instructed.
Results: After completing this exercise, all virtual machines should start properly.
MCT USE ONLY. STUDENT USE PROHIBITED
L3-4 Core Solutions of Microsoft® Lync® Server 2013
2. In the Lync Server Management Shell, type the following command, and then press Enter.
$rootDN = ([adsi]"").distinguishedName
3. In the Lync Server Management Shell, type the following command, and then press Enter.
$sipDomain = “adatum.com”
4. In the Lync Server Management Shell, type the following command, and then press Enter.
$csPool = 'lon-pool.adatum.com'
5. In the Lync Server Management Shell, type the following command, and then press Enter.
6. In the Lync Server Management Shell, type the following command, and then press Enter.
$users = $group.member
7. In the Lync Server Management Shell, type the following command, and then press Enter.
Note You may have to use a trial and error method to determine where spaces might be needed, or
not needed, in the preceding commands.
Note The $sipDomain, $csPool, $group, and $users are all variables in the commands.
5. Notice the list of enabled users now includes users who are members of the Managers group in
Active Directory.
MCT USE ONLY. STUDENT USE PROHIBITED
L3-5
Results: After completing this exercise, you should have provisioned users based on an Active Directory
attribute, in this case, group membership, by using the Lync Server Management Shell.
MCT USE ONLY. STUDENT USE PROHIBITED
L3-6 Core Solutions of Microsoft® Lync® Server 2013
2. In Internet Explorer, in the address box, type https://lyncadmin.adatum.com, and then press Enter.
3. At the connection prompt, sign in as Adatum\Adam, with the password, Pa$$w0rd.
4. Confirm that access is denied. You should see an …Access is denied… message.
2. In the Active Directory Users and Computers administrative snap-in, in the navigation pane, expand
Adatum.com, and then click the Users container.
3. In the Results pane, right-click the CSAdministrator group, and then click Properties.
4. On the CSAdministrator Properties page, click the Members tab, and then click Add.
5. On the Select Users, Contacts, Computers, Service Accounts, or Groups page, in the Enter the object
names to select box, type Adam, and then click OK.
6. Return to the CSAdministrator Properties page. On this page, click OK.
5. At the Windows Security prompt, in the User name box, type Joe, in the Password box, type
Pa$$w0rd, and then click OK.
6. Navigate around and notice what is and what is not available to the CSHelpDesk members as
compared to the CSAdministrator group.
Important After this lab, we recommend that you take a snapshot of all running virtual machines
before starting the next lab. To do so, in Hyper-V Manager, select all running virtual machines, right-
click, and then click Snapshot.
Results: After completing this exercise, you should be able to use RBAC and know how basic Active
Directory group membership modifies rights within Lync Server 2013.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-1
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
a. Right-click 20336B-LON-SQL2-03, and then click Start.
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
a. Right-click 20336B-LON-CL1-03, and then click Start.
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
MCT USE ONLY. STUDENT USE PROHIBITED
L4-2 Core Solutions of Microsoft® Lync® Server 2013
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
12. On Host2, when 20336B-RED-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
13. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
16. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
17. Under Remote audio recording, click Record from this computer, and then click OK.
18. Click the General tab.
19. Under Logon settings, in the Computer box, type red-cl1.Adatum.com.
20. In the User name box, type Adatum\Alex, and then click Connect.
23. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
24. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
25. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
28. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
29. Under Remote audio recording, click Record from this computer, and then click OK.
30. Click the General tab.
31. Under Logon settings, in the Computer box, type lon-cl1.Adatum.com.
32. In the User name box, type Adatum\Adam, and then click Connect.
33. On the Remote Desktop Connection page, click Connect.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-3
34. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
35. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Important: All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Results: After completing this exercise, you will have started all the virtual machines to complete the
remaining exercises.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-4 Core Solutions of Microsoft® Lync® Server 2013
2. In the Lync Server Management Shell, type the following command, and then press Enter.
3. In the Lync Server Management Shell, type the following command, and then press Enter.
4. In the Lync Server Management Shell, type the following command, and then press Enter.
5. In the Lync Server Management Shell, type the following command, and then press Enter.
6. In the Lync Server Management Shell, type the following command, and then press Enter.
7. In the Lync Server Management Shell, type the following command, and then press Enter.
Get-CsClientPolicy
8. In the Lync Server Management Shell, type the following command, and then press Enter.
4. Double-click Alex Darrow and verify that his Client Policy is set as Marketing. Also verify that the
Telephony Mode is set to Enterprise Voice, click Cancel. If not, select Enterprise Voice from the
drop-down, click Commit.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-5
5. Repeat step 4 for Adam Barr and notice that his Client Policy should show as Automatic because if
no policy is set explicitly for him, he will get the Site policy.
6. In the Lync Server Management Shell, type the following command, and then press Enter.
Get-CsClientPolicy
7. On 20336B-LON-FE1-03, review the output showing the Client policies and settings. Notice the
IMWarning for the Site:Redmond (Site 1) Client policy and for Global.
11. At the low right corner, right click Lync, then click Exit. Click start, and then type lync. Click Lync
2013
12. Notice that there is an option for Alex to appear offline, but not for Adam.
13. Start an IM session from Adam to Alex, and notice that the IM Warning appears only for Alex. Next
close the IM window in LON-CL1.
14. Start an IM session from Alex to Adam, and notice the IM Warning appears only for Adam.
Results: After completing this exercise, you should be able to describe how to create client policies in
Lync 2013, how to apply them, and then see the effects of the client policies.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-6 Core Solutions of Microsoft® Lync® Server 2013
2. In the Lync Server Management Shell, type the following command, and then press Enter.
3. In the Lync Server Management Shell, type the following command, and then press Enter.
4. In the Lync Server Management Shell, type the following command, and then press Enter.
5. In the Lync Server Management Shell, type the following command, and then press Enter.
6. In the Lync Server Management Shell, type the following command, and then press Enter.
4. View the created Device Configuration policies, and then compare the new site policy to the global
policy.
5. In the Lync Server Management Shell, type the following command, and then press Enter.
Get-CsCommonAreaPhone | FL
6. Notice the new Lobby Phone in Redmond and its configured settings.
Results: After completing this exercise, you should have created device policies and edited the global
policies by using a PowerShell script. This script should also configure a new common area phone.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-7
3. On the Specify file path page, click Browse, navigate to C:\, and then click Next.
8. Notice the newest files that need to be approved. If they do not appear, click Refresh.
3. In the Select a Site window, click Redmond (Site 1), and then click OK.
4. On the New Test Device-Redmond page, in the Device name box, type Test Aries.
5. Under Identifier type, click Serial number.
6. In the Unique identifier box, type 1111111111 (this is a ten-digit number), and then click Commit.
3. On the Device Update tab, click the Edit drop-down menu, and then click Select All.
4. On the Device Update tab, click the Action drop-down menu, and then click Approve.
Results: After completing this exercise, you should have installed a new device update file, uploaded it
into Lync Server, tested it on a specific device, and then approved it for all devices.
MCT USE ONLY. STUDENT USE PROHIBITED
L4-8 Core Solutions of Microsoft® Lync® Server 2013
Get-Csmobilitypolicy | FL
Results: After completing this exercise, you should have created a mobile device policy.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-1
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
a. Right-click 20336B-LON-SQL2-03, and then click Start.
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
a. Right-click 20336B-LON-CL1-03, and then click Start.
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-2 Core Solutions of Microsoft® Lync® Server 2013
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-WAC01-03, is not running:
13. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
14. On Host2, when 20336B-RED-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
15. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
17. Click the Local Resources tab, and then, under Remote audio, click Settings.
18. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
19. Under Remote audio recording, click Record from this computer, and then click OK.
20. Click the General tab.
22. In the User name box, type Adatum\Alex, and then click Connect.
25. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
26. On Host1, when 20336B-LON-CL1-03 has booted up completely, close both Virtual Machine
Connection windows.
27. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-3
29. Click the Local Resources tab, and then, under Remote audio, click Settings.
30. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
31. Under Remote audio recording, click Record from this computer, and then click OK.
34. In the User name box, type Adatum\Adam, and then click Connect.
36. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
37. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Important: All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
2. In the Topology Builder dialog box, select Download Topology from existing deployment, and then
click OK.
3. In the Save Topology As dialog box, type a name for your topology document (for example,
PreWebAppsServerTopology) in the File name box, and then click Save. This topology can later be
retrieved and republished if you encounter problems with your new topology.
4. In Topology Builder, expand Lync Server, expand the London site, expand Lync Server 2013, expand
Enterprise Edition Front End pools, right-click the lon-pool.adatum.com, and then click Edit
Properties.
5. In the Edit Properties dialog box, on the General tab, find the heading Associate pool with an
Office Web Apps Server, select the check box on the left, and then click New.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-4 Core Solutions of Microsoft® Lync® Server 2013
6. In the Define New Office Web Apps Server dialog box, type the fully qualified domain name
(FQDN) of your Office Web Apps server computer in the Office Web Apps Server FQDN box as lon-
wac01.adatum.com. When you do this, your Office Web Apps server discovery URL should
automatically be entered into the Office Web Apps Server discovery URL box as https:// lon-
wac01.adatum.com/hosting/discovery/.
7. In the Define New Office Web Apps Server dialog box, click OK, and then, in the Edit Properties
dialog box, click OK. The Office Web Apps discovery URL will then be listed as one of the pool's
associations.
8. In Topology Builder, expand Lync Server, expand the Redmond site, expand Lync Server 2013, expand
Enterprise Edition Front End pools, right-click the red-pool.adatum.com, and then click Edit
Properties.
9. In the Edit Properties dialog box, on the General tab, find the heading Associate pool with an
Office Web Apps Server and check it. Then, from the drop-down menu, select lon-
wac01.adatum.com, and then click OK.
10. You have successfully associated the LON-WAC01 Office Web Apps server to the London and
Redmond pools. You can now publish the topology.
2. On the Publish the topology page, review the actions that should be completed, and then click
Next.
3. On the Publishing wizard complete page, verify that all steps show as Success.
4. Click Finish to close the Publish Topology window.
2. In the Certificates Management Console, expand Certificates (Local Computer), and then click
Personal.
3. Right-click Personal, click All Tasks, click Advanced Operations, and then click Create Custom
Request.
4. In the Certificate Enrollment Wizard, on the Before You Begin page, click Next.
5. On the Select Certificate Enrollment Policy page, click Active Directory Enrollment Policy, and then
click Next.
6. On the Custom Request page, in the Template drop-down list, select Web Server, and then click
Next.
7. On the Certificate Information page, in the window next to Details, click the down chevron, and
then click Properties.
8. On the Certificate Properties page, on the Subject tab, under Subject name, in the Type drop-
down list, select Common name.
10. Under Alternative name in the Type drop-down list, select DNS.
11. In the Value box, type lon-wac01.adatum.com, and then click Add.
12. Click the General tab, and then, in the Friendly name box, type Office Web Apps Certificate.
Note This exact name is important because you will need to refer to this certificate by using its
Friendly Name in a command line, later.
13. Click the Private Key tab, and then click the down chevron next to Key Options to expand the
options.
14. Select the Make private key exportable check box, and then click OK.
15. Return to the Certificate Information page, and then click Next.
16. On the Certificate Enrollment page, in the File Name box, type C:\WACCert.req, and then click Finish.
5. Close Notepad.
6. Start Microsoft Internet Explorer.
7. In the Address bar, type http://lon-dc1/certsrv, and then press Enter. If Windows Internet Explorer
10 popped up, click Ask me later.
10. On the Advanced Certificate Request page, click Submit a certificate request by using a base-64-
encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7
file.
11. On the Submit a Certificate Request or Renewal Request page, right-click in the Saved Request
window, and then click Paste.
12. In the Certificate Template drop-down list, select Web Server, and then click Submit.
Note: If it fails please restart the Active Directory Certificate Services on LON-DC1, and then go to
LON-WAC01 to confirm that all services set to Automatic start have started, then to try again.
14. In the File Download window, click Save, and then select Save as.
15. On the Save As page, in the File name box, type C:\WACCert.cer, and then click Save.
3. On the File to Import page, in the File name box, type C:\WACCert.cer, and then click Next.
4. On the Certificate Store page, leave the default settings, and then click Next.
6. At the Certificate Import Wizard prompt, click OK, and then close the Certificates MMC without
saving changes.
2. In the Microsoft Office Web Apps Server 2013 Wizard, select the I accept the terms of this
agreement check box, and then click Continue.
3. On the Choose a file location page, leave the default settings, and then click Install Now.
Import-Module OfficeWebApps
This will load the Office Web Apps Windows PowerShell module.
Note If the preceding command fails to run, LON-WAC01 may need to be restarted, following the
installations that took place in the previous task.
Note The Certificate parameter must match the Friendly Name you entered when you created the
certificate request.
2. In Event Viewer, expand Applications and Services Logs, and then click Lync Server.
3. In the Lync Server event logs, find the newest event with the ID of 41032 with the source of LS Data
MCU, and view its properties.
2. In the Select URL dialog box, click https://lon-poolweb-int.adatum.com/cscp, and then click OK.
a. In the Windows security box, type Administrator, with the password, Pa$$w0rd.
4. On the Dial Plan tab, click the New button, and choose Site dial plan from the drop-down list.
5. In the Select a Site dialog box, click London (Site 0), and then click OK.
7. In the Dial In Conferencing Region box, enter UK Region, and then click OK.
8. On the Dial Plan tab, click the New button, and choose Site dial plan from the drop-down list.
9. In the Select a Site dialog box, click Redmond (Site 1), and then click OK.
12. On the Dial Plan tab, double-click the Global dial plan.
13. On the Edit Dial Plan - Global page, in the Dial-in conferencing region box, type US Region, and then
click OK.
14. Click the Commit menu, and then click Commit all.
15. On the Uncommitted Voice Configuration Settings page, click OK.
16. At the Microsoft Lync Server 2013 Control Panel prompt, click Close.
3. On the New Dial-in Access Number page, in the Display number box, type +1 (425) 555-2345.
4. In the Display name box, type US Dial-in Conferencing Number.
5. In the Line URI box, type tel:+14255552345.
6. In the SIP URI box, type sip:USCAA, and then, in the drop-down list, click adatum.com.
10. In the Select Regions window, click US Region, and then click OK.
11. On the New Dial-in Access Number page, click Commit.
2. On the New Dial-in Access Number page, in the Display number box, type +44-20-5555-4567.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-8 Core Solutions of Microsoft® Lync® Server 2013
5. In the SIP URI box, type sip:UKCAA, and then, in the drop-down list, click adatum.com.
9. In the Select Regions window, click UK Region, and then click OK.
$cred = Get-Credential
3. In the Windows PowerShell Credential Request window, in the User name box, type
Adam@adatum.com.
4. In the Password box, type Pa$$w0rd, and then click OK.
5. In Lync Server Management Shell, type the following command, and then press Enter.
6. In Lync Server Management Shell, type the following command, and then press Enter.
Results: After completing this exercise, you should have configured dial-in conferencing, first by
configuring Regions for the dial plans, and then configuring US and UK dial-in access numbers. Then, you
used the Lync Server 2013 Management Shell to test the conferencing numbers.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-9
2. Double-click Global.
3. On the Edit Conferencing Policy - Global page, in the Maximum meeting size box, type 10.
3. On the New Conferencing Policy – London page, in the Maximum meeting size box, type 100.
8. On the Conferencing Policy tab, click New, and then click Site policy.
9. In the Select a Site window, click Redmond, and then click OK.
10. On the New Conferencing Policy - Redmond page, in the Maximum meeting size box, type 100.
12. Verify that the Enable PSTN dial-in conferencing check box is selected
2. On the New Conferencing Policy page, in the Name box, type Unrestricted Conferencing Policy.
3. In the Description box, type Adatum Unrestricted Conferencing Policy.
5. Select the Allow federated and anonymous participants to record check box.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-10 Core Solutions of Microsoft® Lync® Server 2013
7. Select the Allow federated and anonymous participants to take control check box.
8. Select the Enable peer-to-peer recording check box, and then click Commit.
2. In the User Search bar, type Adam Barr, and then click Find.
5. In the Line URI field, enter the following: tel:+442055551001;ext=1001, and then click Commit.
6. Repeat steps 2-4 for Alex Darrow to enable the user for Enterprise Voice, if not already enabled.
7. In the Line URI field, enter the following: tel:+14255552001;ext=2001, and then click Commit.
Results: After completing this exercise, you should have edited the global conferencing policy, created
two site policies and one unrestricted user policy.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-11
2. Sign in to Lync 2013 on LON-CL1 as Adam, and then open Microsoft Outlook.
Note: You will be prompted to create an Outlook profile here. Click Next three times and then click
finish to create the Outlook profile. Do the same after the next step as well.
3. Sign in to Lync 2013 on RED-CL1 as Alex, and then open Microsoft Outlook.
4. On LON-CL1, in Lync 2013, click the Phone tab, and then click PIN.
5. On the Dial-in Conferencing Settings and PIN Management page, click Sign In.
6. In the Dial-in Conferencing Settings and PIN Management page, click Sign In again, and then
enter Adam’s credentials.
Note If you are not prompted for credentials or get an error, go back to the Dial-in Conferencing
Settings and PIN Management page, click Sign in with a different account, and then enter Adam’s
credentials.
7. On the Set Your PIN page, in the New PIN and Confirm PIN boxes, type 13579, and then click OK.
8. On the Dial-in Conferencing Settings and PIN Management page, under Assigned Conference
Information, make a note of Adam’s assigned Conference ID and Meeting URL.
9. Notice the features of Dial-in Conferencing, such as DTMF controls, entrance and exit
announcements, and the option for different languages.
10. On both clients, call the US dial-in access number (+14255552345). The Conference Auto Attendant
will prompt you to enter a conference ID. Enter Adam’s Conference ID to start an specific dial-in
conference. Repeat these steps for the London dial-in access number (+442055554567).
Note Enter the + sign when you dial. If you cannot hear audio from the virtual machines, you can still
enter the conference ID by using the keypad or the dialpad in Lync.
4. In the meeting invite, notice the meeting join information provided and other information, such as
Conference ID.
6. If you get a Join Meeting Audio prompt, select Use Lync (full audio and video experience), select
the Don’t show this again check box, and then click OK.
a. Application Sharing
i. On LON-CL1, in the conference window, click the Share tab, and then select Program.
ii. In the Present Programs window, click Inbox – Adam@Adatum.com– Microsoft Outlook,
and then click Present.
iii. At the Lync prompt, select the Do not show again check box, and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-12 Core Solutions of Microsoft® Lync® Server 2013
i. On the sharing toolbar, click Give Control, and then click Give Control Automatically.
c. Desktop sharing
i. On LON-CL1, in the conference window, click the Share tab, and then click Desktop.
i. On the sharing toolbar, click Give Control, and then click Give Control Automatically.
e. Data collaboration
i. On LON-CL1, in the conference window, click the Share tab, and then select PowerPoint
Presentation.
ii. In the Share PowerPoint window, navigate to C:\Program Files (x86)\Microsoft
Office\Templates\1033, click Training.pptx, and then click Open.
f. Annotations
i. On LON-CL1 and RED-CL1, in the conference window, use the toolbar at the right of the
stage to edit the PowerPoint slides.
g. Whiteboards
i. On LON-CL1, in the conference window, click the Share tab, and then click Whiteboard.
ii. On LON-CL1 and RED-CL1, notice that you can write on the whiteboard.
iii. On LON-CL1, click Stop Presenting.
h. Polls
i. On LON-CL1, in the conference window, click the Share tab, and then click Poll.
ii. In the Create a Poll window, type a Poll name and Question, type in some Choices, and
then click Create.
i. Recording
i. On LON-CL1, in the conference window, click the … ellipsis at the lower-right, and then click
Start Recording.
ii. On RED-CL1, notice that the Recording has started prompt appears. Start a conversation and
send some IM messages.
iv. In the Stop Recording window, notice the default settings, and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-13
v. When you see the Your Lync Recording is available prompt on the system tray, click the
prompt to open the Microsoft Lync Recording Manager.
vi. In the Microsoft Lync Recording Manager window, click the recording, and then click Play.
vii. If you get any messages about Media Player’s first run, click the defaults.
viii. Notice that the meeting recording is played, close the window, and then close the Microsoft
Lync Recording Manager.
8. On RED-CL1, in Alex’s Outlook Calendar, click the New Lync Meeting button.
9. Invite Adam to the meeting, and click Send to send the email invite.
10. On LON-CL1 have Adam join the meeting, and on RED-CL1, have Alex join the meeting.
11. If you get a Meeting Audio prompt, select Use Lync (integrated audio and video), select the Don’t
show this again check box, and then click OK.
12. Notice that Redmond site’s conferencing policy is being applied and view the features that are
available.
3. In the Assign Policies window, in the Conferencing policy drop-down list, click Unrestricted
Conferencing Policy, and then click OK.
4. Close Lync 2013 and Microsoft Outlook on LON-CL1, and then sign back in as Adam. Then, open
Outlook2013.
5. Close Lync 2013 and Outlook 2013 on RED-CL1, and then sign back in as Alex. Then, open
Outlook2013.
6. On LON-CL1, in Adam’s Outlook Calendar, click the New Lync Meeting button.
7. Invite Alex to the meeting, and click Send to send the email invite.
8. On LON-CL1 have Adam join the meeting, and on RED-CL1, have Alex join the meeting.
9. Notice that the unrestricted user conferencing policy is being applied and all the features are
available:
Results: After completing this exercise, you should have tested and verified the dial-in conferencing
access numbers you earlier configured. You also tested and verified the application of conferencing
policies, and reviewed the features of Lync Server 2013 conferencing.
MCT USE ONLY. STUDENT USE PROHIBITED
L5-14 Core Solutions of Microsoft® Lync® Server 2013
MCT USE ONLY. STUDENT USE PROHIBITED
L6-1
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
a. Right-click 20336B-LON-SQL1-03, and then click Start.
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
b. Right-click 20336B-RED-FE1-03, and then click Start.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, click Start, click Administrative Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Important All connections to LON-CL1 will require using a Remote Desktop Connection with remote
audio playback and remote audio recording enabled, unless otherwise specifically instructed.
2. On LON-FE01, press the Windows key, type Lync, and then click Lync Server Management Shell.
3. In the Lync Server Management Shell, type the following command, and then press Enter.
Note: You may only need to type the “Get…” line of this command.
Get-CsManagementStoreReplicationStatus
UpToDate : True
MCT USE ONLY. STUDENT USE PROHIBITED
L6-3
ReplicaFqdn : lon-fe01.adatum.com
LastStatusReport : 12/5/2012 8:26:47 AM
LastUpdateCreation : 12/5/2012 8:24:57 AM
ProductVersion : 5.0.8308.0
UpToDate : True
ReplicaFqdn : red-fe01.adatum.com
LastStatusReport : 12/5/2012 8:26:47 AM
LastUpdateCreation : 12/5/2012 8:24:57 AM
ProductVersion : 5.0.8308.0
2. On the Welcome to Topology Builder page, select Download Topology from existing deployment,
and then click OK.
3. In the Save Topology As window, navigate to the desktop and save the topology as Lab6.tbxml.
4. In the Topology Builder, expand Lync Server, expand London, expand Lync Server 2013, and then
click Edge Pools.
7. On the Define the Edge pool FQDN page, in the Pool FQDN box, type lon-edge01.adatum.com.
10. On the Select IP options page, select the Enable IPv4 on internal interface and Enable IPv4 on external
interface check boxes, and then click Next.
11. On the External FQDNs page, in the Access Edge Service box, type sip.adatum.com, and leave the
port as 443.
12. In the Web Conferencing box, type webconf.adatum.com, and leave the port as 443.
13. In the A/V Edge Service box, type av.adatum.com, leave the port as 443, and then click Next.
14. On the Define the internal IP address page, in the Internal IP address box, type 172.16.0.40, and then
click Next.
15. On the Define the external IP address page, in the Access Edge Service box, type 131.107.155.3.
17. In the A/V Edge service box, type 131.107.155.5, and then click Next.
18. On the Define the next hop page, in the Next hop pool drop-down list, click lon-pool.adatum.com
London (Site 0), and then click Next.
19. On the Associate Front End pools page, select the lon-pool.adatum.com and red-pool.adatum.com
check boxes, and then click Finish.
20. In Topology Builder, right-click London (Site 0), and then click Edit Properties.
21. Under Site federation route assignment, click Enable SIP federation.
22. In the drop-down list, click lon-edge01.adatum.com London (Site 0) Edge.
23. Under Site federation route assignment, click Enable XMPP federation
24. In the drop-down list, click lon-edge01.adatum.com London (Site 0) Edge, and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L6-4 Core Solutions of Microsoft® Lync® Server 2013
25. In Topology Builder, right-click Lync Server, and then click Publish Topology.
27. On the Publishing wizard complete page, verify that all steps show as Success, and then click
Finish.
2. In the Lync Server Management Shell, type the following command, and then press Enter.
5. Copy \\lon-fe01\c$\Config.zip to C:\LabFiles. Note You may need to create a folder named, LabFiles
on the drive C.
Results: After completing this exercise, you should have defined a new Edge Pool, defined internal and
external FQDNs and IP addresses, and then published the topology. You should have also exported the
configuration for Edge Server role deployment.
MCT USE ONLY. STUDENT USE PROHIBITED
L6-5
4. On the Properties for LON-EDGE01 page, next to External, click the IPv4 address assigned by DHCP,
IPv6 enabled link.
5. In the Network Connections window, right-click External, and then click Properties.
6. In the External Properties dialog box, scroll down and click Internet Protocol Version 4
(TCP/IPv4), and then click the Properties button.
7. In the on Internet Protocol Version 4 (TCP/IPv4) properties dialog box, click the Use the following IP
address button. Enter 131.107.155.3 for the IP address, and 255.255.0.0 for the Subnet mask.
9. In the Advanced TCP/IP Settings dialog box, under IP address, click the Add button.
10. Enter 131.107.155.4 for the IP address and 255.255.0.0 for the Subnet mask, and then click Add.
11. In the Advanced TCP/IP Settings dialog box, under IP address, click the Add button.
12. Enter 131.107.155.5 for the IP address and 255.255.0.0 for the Subnet mask, and then click Add.
13. In the Advanced TCP/IP Settings dialog box, click OK.
14. In the Internet Protocol Version 4 (TCP/IPv4) properties dialog box, click OK.
18. In the System Properties dialog box, on the Computer Name tab, click the Change button.
19. In the Computer Name/Domain Changes dialog box, click the More…. button.
20. In the Primary DNS Suffix of this computer box, type adatum.com, and then click OK.
25. After the server restarts, log on to LON-EDGE01 as Administrator, with the password, Pa$$w0rd.
2. Ensure that the topology configuration file you created by using Topology Builder is available on the
Edge Server.
5. Click Yes to install the Visual C++ 2012 x64 Minimum Runtime. Wait a few moments for setup to
start.
6. On the Installation Location page, leave the default location, and then click Install.
7. On the License Agreement page, select the I accept the terms in the license agreement check box,
and then click OK.
8. On the Lync Server 2013 - Deployment Wizard page, click Install or Update Lync Server System.
9. On the Lync Server 2013 - Deployment Wizard page, next to Step 1: Install Local Configuration Store,
click Run.
10. On the Configure Local Replica of Central Management Store page, verify that Import from a file is
selected, and then click Browse.
11. Navigate to C:\LabFiles, select Config.zip, click Open, and then click Next.
12. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
13. On the Lync Server 2013 - Deployment Wizard page, next to Step 2: Setup or Remove Lync Server
Components, click Run.
Note Ensure that LON-EDGE01 has the CA Certificate Chain from the internal Adatum Certificate
Authority LON-DC1. This step was completed as part of the classroom setup.
1. On LON-EDGE01, on the Lync Server 2013 - Deployment Wizard page, next to Step 3: Request, Install
or Assign Certificates, click Run.
2. In the Certificate Wizard window, verify that Edge Internal is selected, and then click Request.
5. On the Choose a Certification Authority (CA) page, in the Specify another certification authority box,
type LON-DC1.adatum.com\adatum-lon-dc1-ca, and then click Next.
6. On the Certification Authority Account page, clear the Specify alternate credentials for the
certification authority check box, and then click Next.
7. On the Specify Alternate Certificate Template page, leave the check box clear, and then click Next.
8. On the Name and Security Settings page, in the Friendly Name box, type LON-EDGE01 Internal
Cert, verify that the Bit Length is 2048, and then click Next.
9. On the Organization Information page, in the Organization box, type ADATUM Corporation.
10. In the Organizational Unit box, type IT, and then click Next.
11. On the Geographical Information page, in the Country/Region drop-down list, click United Kingdom.
MCT USE ONLY. STUDENT USE PROHIBITED
L6-7
13. In the City/Locality box, type London, and then click Next.
14. On the Subject Name/Subject Alternate Names page, review the Subject Name that is
automatically populated, and then click Next.
15. On the Configure Additional Subject Alternate Names page, leave the fields blank, and then click
Next.
18. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
23. Return to the Certificate Wizard, and then, under Certificate, click External Edge certificate (public
internet), and then click Request.
24. On the Certificate Request page, click Next.
25. On the Delayed or Immediate Requests page, verify that Send the request immediately to an online
certification authority is selected, and then click Next.
26. On the Choose a Certification Authority (CA) page, verify that LON-DC1.adatum.com\adatum-lon-
dc1-ca is listed, and then click Next.
27. On the Certification Authority Account page, clear the Specify alternate credentials for the
certification authority check box, and then click Next.
28. On the Specify Alternate Certificate Template page, leave the check box clear, and then click Next.
29. On the Name and Security Settings page, in the Friendly Name box, type LON-EDGE01 External
Cert, verify that the Bit Length is 2048, and then click Next.
30. On the Organization Information page, in the Organization box, type Adatum Corporation.
31. In the Organizational Unit box, type IT, and then click Next.
32. On the Geographical Information page, in the Country/Region drop-down list, click United Kingdom.
34. In the City/Locality box, type London, and then click Next.
35. On the Subject Name/Subject Alternate Names page, review the Subject Name and Subject
Alternate Names automatically populated, and then click Next.
36. On the SIP Domain setting on Subject Alternate Names (SANs) page, select the Adatum.com check
box, and then click Next.
37. On the Configure Additional Subject Alternate Names page, leave the fields blank, and then click
Next.
39. On the Executing Commands page, when the Task Status shows as Completed, click Next.
MCT USE ONLY. STUDENT USE PROHIBITED
L6-8 Core Solutions of Microsoft® Lync® Server 2013
40. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
44. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
45. Return to the Certificate Wizard, click the down arrow next to External Edge certificate (public
Internet), verify that Sip Access Edge external, Web Conferencing Edge external, and A/V Edge
external show a Status of Assigned, and then click Close.
2. On the Start Services page, click Next. Wait a few minutes for the services to start.
3. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
4. In the Lync Server Control Panel, in the navigation pane, click Federation and External User Access.
5. On the External Access Policy, double-click Global.
6. On the Edit External Access Policy - Global page, select the Enable communications with federated
users, Enable communications with remote users, and Enable communications with public users check
boxes, and then click Commit.
8. Double-click Global.
9. On the Edit Access Edge Configuration page, select the Enable federation and public IM connectivity,
Enable partner domain discovery, Enable remote user access, and Enable anonymous user access to
conferences check boxes, and then click Commit.
MCT USE ONLY. STUDENT USE PROHIBITED
L6-9
2. Install the telnet client by using the following command, and then press Enter.
Add-WindowsFeature telnet-client
3. On the Start menu of the LON-FE1, in the Search box, type cmd and then press Enter. The
Command Prompt window appears.
4. At the command prompt, type telnet lon-edge01.adatum.com 5061, and then press Enter.
5. Close the Command Prompt window.
6. On the Start menu of the LON-FE1, in the Search box, type cmd, and then press Enter. The
Command Prompt window appears.
7. At the command prompt, type telnet lon-edge01.adatum.com 8057, and then press Enter.
9. On the Start menu of the LON-FE1, in the Search box, type cmd, and then press Enter. The
Command Prompt window appears.
10. At the command prompt, type telnet lon-edge01.adatum.com 5062, and then press Enter. Close
the Command Prompt window.
11. On the Start menu of the LON-FE1, in the Search box, type cmd, and then press Enter. The
Command Prompt window appears.
12. At the command prompt, type telnet lon-edge01.adatum.com 443, and then press Enter.
14. On the Start menu of the LON-FE1, in the Search box, type cmd, and then press Enter. The
Command Prompt window appears.
15. At the command prompt, type telnet lon-edge01.adatum.com 4443, and then press Enter.
Note Verify that all telnet sessions are connected successfully without errors. The telnet session may
display some symbols if successful.
To begin this lab, you must connect to the appropriate virtual machines by performing the following
steps:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
a. Right-click 20336B-LON-CL1-03, and then click Start.
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
MCT USE ONLY. STUDENT USE PROHIBITED
L7-2 Core Solutions of Microsoft® Lync® Server 2013
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-CHAT1-03, is not running:
14. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
16. Click the Local Resources tab, and then, under Remote audio, click Settings.
17. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
18. Under Remote audio recording, click Record from this computer, and then click OK.
19. Click the General tab.
21. In the User name box, type Adatum\Alex, and then click Connect.
22. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Connect.
23. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
24. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
25. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
26. In the Remote Desktop Connection window, click Options.
27. Click the Local Resources tab, and then, under Remote audio, click Settings.
28. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
29. Under Remote audio recording, click Record from this computer, and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L7-3
32. In the User name box, type Adatum\Adam, and then click Connect.
33. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Connect.
34. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Verify that all services set to Automatic have started on the appropriate virtual machines. Most
notably, check the Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do
so, complete the following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Important Note All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote
Desktop Connection with remote audio playback and remote audio recording enabled, unless
otherwise specifically instructed.
3. On the Welcome to Topology Builder page, click Download Topology from existing deployment,
and then click OK.
4. In the Save Topology As window, navigate to the desktop and save the topology as Lab7.tbxml.
5. Expand Lync Server, expand London (Site 0), expand Lync Server 2013, right-click persistent Chat
Pools, and then click New persistent Chat Pool.
6. In pool FQDN, type Lon-CHAT01.adatum.com, select the Single Computer Pool radio button, and
then click Next.
7. In the Display Name of the Persistent Chat Pool text box, type ADatum Persistent Chat Pool. Select
the Enable Compliance check box, and then click Next.
8. In the Define the SQL Server Store window, on the drop-down menu, select lon-
sql01.adatum.com\LYNC. Leave the Enable SQL Server Store Mirroring box unchecked, and then
click Next.
9. In the Define the Compliance SQL Server Store window, on the drop-down menu, select lon-
sql01.adatum.com\LYNC. Leave the Enable SQL Server Store Mirroring box unchecked, and then
click Next.
10. In the Define the file store window, in the drop-down box, select the lon-
sql02.adatum.com\lyncshare check box, and then click Next.
11. On the select the next hop server, in the drop-down box, select the lon-pool.adatum.com London
(Site 0) as the next hop pool, and then click Finish
12. Review the settings for Persistent Chat, right-click Lync Server 2013 in the Topology select Publish.
13. On the Publish the topology page, review the actions that will be performed, and then click Next.
14. On the Create databases page, verify that the lon-sql01.adatum.com\LYNC is selected, and then
click Next.
MCT USE ONLY. STUDENT USE PROHIBITED
L7-4 Core Solutions of Microsoft® Lync® Server 2013
15. On the Publishing wizard complete page, verify that all steps show as Success. If any step finishes
with completed with warnings, review these warnings to verify that they are not serious. SQL Server
might throw an error about Setting SQL Server Show Advanced Options to 1.
16. Under Next steps, click the link to open the to-do list.
17. Review the NextSteps.txt file that opens and the instructions to run local setup on each server in the
list, and then close Notepad.
Results: After completing this exercise, you should have published the persistent Chat pool to the
topology.
MCT USE ONLY. STUDENT USE PROHIBITED
L7-5
9. On the Microsoft Lync Server 2013 pop-up, answer yes to the question about installing the Microsoft
Visual C++ runtime.
10. On the Lync Server 2013 page, let stand the default location, and then click Install.
11. On the End User License Agreement page, select the I accept the terms in the license agreement
check box, and then click OK.
12. On the Lync Server 2013 - Deployment Wizard page, click Install or Update Lync Server System.
13. On the Lync Server 2013 - Deployment Wizard page, next to Step 1: Install Local Configuration Store,
click Run.
14. On the Configure Local Replica of Central Management Store page, verify that Retrieve directly from
the Central Management Store is selected, and then click Next.
15. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
3. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
4. On the Delayed or Immediate Requests page, verify that Send the request immediately to an online
certification authority is selected, and then click Next.
8. On the Name and Security Settings page, in the Friendly Name box, type LON-CHAT01 Lync Server
Certificate, and then click Next.
11. On the Geographical Information page, in the Country/Region drop-down list, click United
Kingdom.
14. On the Subject Name/Subject Alternate Names page, review the Subject Name and Subject
Alternate Names that are automatically populated, and then click Next.
15. On the Configure Additional Subject Alternate Names page, leave the fields blank, and then click
Next.
16. On the Certificate Request Summary page, click Next.
17. On the Executing Commands page, when the Task Status shows as Completed, click Next.
Note: If it fails please restart the Active Directory Certificate Services on LON-DC1, and then go to
LON-CHAT1 to confirm that all services set to Automatic start have started, then to try again.
18. On the Online Certificate Request Status page, verify that the Assign this certificate to Lync Server
certificate usages check box is selected, and then click Finish.
19. On the Certificate Assignment page, click Next.
22. On the Certificate Wizard, click the down arrow next to Default Certificate to expand the Certificate
Type.
23. Verify that Server Default shows as Assigned.
3. On the Executing Commands page, when the Task Status shows as Completed, click Finish.
4. On the Lync Server 2013 – Deployment Wizard page, next to Service Status (Optional), click Run.
5. In the Services console, scroll down to the Lync Server Persistent Chat service, and verify that the
Status is Running. Close the Services console.
4. On the Security tab, click Local intranet, and then click Sites.
5. In the Local intranet window, clear the Automatically detect intranet network check box, and then
click Advanced.
6. In the next Local intranet window, in the Add this website to the zone box, type *.adatum.com,
click Add, and then click Close.
8. In Internet Explorer, in the Address box, type https://lyncadmin.adatum.com, and then press Enter.
12. On the Select from Active Directory® page, in the Search bar, type Allie Bellew, and then click Find.
13. Select Allie Bellew, and then click OK.
14. On the New Lync Server User page, in the Assign users to a pool drop-down menu, click lon-
pool.adatum.com.
15. Under Generate users’ SIP URI, leave the default selection of Use user’s email address.
3. Select the persistent chat on the left, click New in the Category tab, then click
persistentChatServer:lon-chat01.adatum.com, and then click OK.
4. In the New Category window, in the Name box, type Sales persistent Chat Room, in the
Description, type Chat Room for Sales Users, and then select the Enable File Upload check box.
5. In the membership section, underneath Allowed members, click Add, in the Select Allowed
Members box, type “sales” in the search bar. Click Find.
6. In the results section, select the Sales Organizational Unit, and then click OK
7. Underneath the Creators section, click Add, and in the Select Creators box, type Aaren Ekelund in
the search bar. Click Find.
8. In the results section, select Aaren Ekelund, and then click OK
10. Click the Persistent Chat Policy Tab, select the Global policy, click Edit, and then click Show details.
MCT USE ONLY. STUDENT USE PROHIBITED
L7-8 Core Solutions of Microsoft® Lync® Server 2013
11. In the Edit Persistent Chat Policy – Global window, check the Enable Persistent Chat button, and then
click Commit.
Task 3: Create the Persistent Chat room for the Sales employees.
1. Log on to LON-CL1 as adatum\aaren. with the password, Pa$$w0rd.
2. On the LON-CL1, click Desktop, on the First things first page, click Ask me later, click Accept. The
Aaren Ekelund User should now have a Chat Room symbol. Click this symbol and observe the Ego
Feed. Click the plus symbol, and then select Create a Chat Room.
Note If you a warning message, “chat services may not be available…”, appears, then wait about five
minutes, and then you will be able to proceed.
3. In the webpage, log on as Aaren, with the user name, adatum\aaren, and the password, Pa$$w0rd.
5. In the Room Name textbook, type Sales War Room, and press the validation button on the right to
validate. In the Description textbook, type this is the war room for the sales team of Adatum.
Leave the privacy option radio button as closed. Verify that Aaren Ekelund is listed in the Managers
section.
6. In the Members section, try to add both “Allie Bellew” and “Dan Park” by typing ;Allie Bellew;Dan
Park, in the Members box. Click the verification icon on the right to verify their names.
7. Observe how Allie Bellew is an invalid member, because she is not part of the sales OU. Remove Allie
Bellew and click Create. Close the Explorer window.
8. In the Lync client, click the chat room icon, then click the MEMBER OF tab, and then double-click
Sales Room to open the Sales Room chat room.
9. Type something and press enter, and then log off from the client.
10. Log on to LON-CL1 as adatum\allie, with the password, Pa$$w0rd.
11. On the LON-CL1, click Desktop, on the First things first page, click Ask me later, click Accept. if
necessary, click start, type Lync, and then click Lync 2013. Wait until sign in successful, Click the chat
room symbol and observe the Ego Feed. Click the MEMBER OF tab and observe that there is no
room listed.
14. On LON-CL1, click Desktop, on the First things first page, click Ask me later, click Accept. If
necessary, click start, type Lync, and then click Lync 2013. Wait until sign in successfully, click the
chat room symbol and observe the Ego Feed. Click the MEMBER OF tab and observe that Sales
Room is listed.
15. Double-click the Sales Room and observe that the text you typed as Aaren is visible.
Note: After this lab, we recommend that you take a snapshot of all running virtual
machines before starting the next lab. To do so, in Hyper-V Manager, highlight all running virtual
machines, right-click and then click Snapshot.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-1
To begin this lab, you must connect to the appropriate virtual machines by using the following steps:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
b. Right-click 20336B-LON-ROUT1-03, and then click Connect.
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-2 Core Solutions of Microsoft® Lync® Server 2013
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-WAC01-03, is not running:
13. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
14. On Host2, when 20336B-RED-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
15. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
17. Click the Local Resources tab, and then, under Remote audio, click Settings.
18. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
19. Under Remote audio recording, click Record from this computer, and then click OK.
20. Click the General tab.
22. In the User name box, type Adatum\Alex, and then click Connect.
25. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
26. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
27. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-3
29. Click the Local Resources tab, and then, under Remote audio, click Settings.
30. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
31. Under Remote audio recording, click Record from this computer, and then click OK.
34. In the User name box, type Adatum\Adam, and then click Connect.
36. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
37. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Verify that all services set to Automatic have started on the appropriate virtual machines. Most
notably, check the Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do
so, complete the following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Important: All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
Task 3: Configure Lync Server 2013 to be a partner application for Exchange Server
2013.
1. On LON-EX01, click Start, and then click Exchange Management Shell.
2. Locate the value of IsExcludedFromProvisioning for the Mailbox Database by running the following
command and the pressing Enter.
3. If the value is True, update the Mailbox Database so it is enabled for Provisioning. Without this step,
the partner application creation will fail, because there are no valid Mailbox Databases to use for
provisioning. Type the following command, and then press Enter.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-4 Core Solutions of Microsoft® Lync® Server 2013
4. Navigate to the Scripts folder by typing the following command, and then press Enter.
5. At the [PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts> prompt, type the following, and
then press Enter.
Note If you receive the error, “Load balancing failed to find a valid mailbox database”, perform step 3
of this task.
6. Stop and restart Internet Information Services (IIS) by typing the following command, and then press
Enter.
iisreset
7. Leave the Exchange Management Shell open for the next task.
Task 4: Configure Exchange Server 2013 to be a partner application for Lync Server
2013.
1. On LON-EX01, locate the value for the AutodiscoverServiceInternalURI by typing the following
command in Exchange Management Shell, and then pressing Enter.
2. Record the value from the last script in the box below (so you can recall it later).
https://
3. On LON-FE01, click Start, and then click Lync Server Management Shell.
4. Configure Lync by using the Autodiscover information by typing the following command, and then
pressing Enter.
5. Create a new partner application for Exchange by typing the following command in Lync Server
Management Shell, and then pressing Enter.
6. Test the connectivity between Lync and Exchange by typing the following command, and then
pressing Enter.
You should receive the result, Test Passed. If not, contact your instructor.
Task 5: Configure Lync Server 2013 to use Exchange Server 2013 for archiving.
1. On LON-FE01, click Start, and then click Lync Management Shell.
2. Enable Exchange Archiving globally by typing the following command and press enter.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-5
5. In the Windows Security dialog box, type Administrator for the user name, with the password,
Pa$$w0rd, and then click OK.
6. Click Monitoring and Archiving, and then click the Archiving Policy tab.
7. Click the New button, and select User Policy from the drop-down box.
8. In the Name box, enter LondonArchivingPolicy. Select the Archive internal communications and
Archive external communications check boxes, and then click Commit.
9. Click Users. In the search box, type Adam, and then click Find.
10. Double-click the Adam Barr user. Scroll down to the Archiving Policy, click the drop-down arrow,
select LondonArchivingPolicy, and then click Commit.
11. In Lync Management Shell, enable Exchange Archiving for all users on the London Pool by typing the
following command and press enter.
12. Show the list of users that have been enabled for Exchange Archiving by typing the following
command in Lync Management Shell and press enter:
2. Expand adatum.com, and then click the Microsoft Exchange Security Groups Organizational Unit.
3. Double-click the Discovery Management group. On the Members tab, click Add.
4. In the Select Users, Contacts, Computers, Services Accounts, or Groups dialog box type
Administrator, and then click Check Names. Click OK. Click OK to close the Discovery Management
Properties dialog box.
7. On the Exchange Admin Center page, type Adatum\Administrator for the user name, with the
password, Pa$$w0rd, and then click Sign In.
10. In the Name and Description window, type LyncItems for the name, and then click Next.
11. Under Mailboxes, click the Search all mailboxes button, and then click Next.
12. Under Search query, click the Filter based on criteria button. At the lowermost part, click the select
message types… button.
13. In the message types to search window, click the select the messages types to search button, and
select the Lync items check box, and then click OK.
18. Click LyncItems. On the toolbar above, click search, and then select preview search results from the
drop-down box.
Note: A new window opens. Notice the results of the archived message content.
Results: After completing this exercise, you should have configured archiving settings, including polices,
configurations and Exchange integration for Adatum. You should also have generated some IM and web
conferencing traffic to be archived. Finally, you will have viewed the archived data by using Exchange
Control Panel.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-7
Exercise 2: Configuring the Monitoring Server Role and the Lync Server
Monitoring Reports
Task 1: Define Monitoring in Topology Builder.
1. On LON-FE01, click Start, and then click Lync Server Topology Builder. Alternatively, use the
shortcut on the taskbar).
2. On the Topology Builder page, verify that Download Topology from existing deployment is
selected, and then click OK.
3. On the Save Topology as page, browse to C:\LabFiles, in the File Name box, type
AdatumTopologyMon, and then click Save.
4. In the Topology Builder, expand Lync Server, expand London (Site 0), expand Lync Server 2013, and
then expand Enterprise Edition Front End pools.
5. Right-click lon-pool.adatum.com, and then click Edit Properties.
6. Under Associations, select the Monitoring (CDR and QoE Metrics) check box.
4. On the Publishing wizard complete page, verify that all steps show as Success.
Note You may see a Completed with warnings status for Creating Databases on lon-
sql01.adatum.com\LYNC. This is safe to ignore.
5. On the Publishing wizard complete page, click the “Click here to open the to-do list” hyperlink. A
new file will open in Notepad. Read the steps listed. Close Notepad.
9. Start the stopped Lync services by typing the following command and press Enter.
Start-CsWindowsService
3. On the Specify Monitoring Database page, verify that lon-sql01.adatum.com\LYNC is listed for
both the Monitoring Database and the SQL Server Reporting Services (SRSS) instance, and then click
Next.
4. On the specify credentials page, in the User name box, type Adatum\Administrator, in the
Password box, type Pa$$w0rd, and then click Next.
Note The account specified here will be granted read access to the reporting databases. This is the
account used when accessing reports. For lab purposes, we will use the Administrator account. The
user deploying Monitoring Reports must be a System Administrator (SA) on SQL.
5. On the Specify Read-Only Group page, type Adatum\LyncMonReportReaders, and then click Next.
Note This group was created during the classroom setup, and the Administrator account was made a
member of this group.
6. On the Executing Commands page, the last line should be Monitoring Reports have been successfully
deployed. Click Finish.
Results: After completing this exercise, you should have defined Monitoring in the Topology, and
successfully published the changes. Then, you should have deployed the Lync Server Monitoring Reports.
MCT USE ONLY. STUDENT USE PROHIBITED
L8-9
5. Leave the call up for about two minutes, then hang up.
Task 2: Connect to Lync Server Monitoring Reports and review the Dashboard.
1. Log on to LON-CL1 and RED-CL1 as Adatum\Administrator.
2. On LON-CL1 and RED-CL1, open Internet Explorer from the taskbar.
4. In the Windows Security dialog box, in the User Name box, type Administrator, in the Password
box, type Pa$$w0rd for the password, and then click OK.
5. On the Home screen, under Top Actions, expand View Monitoring reports, and then click lon-
sql02.adatum.com. Wait for Internet Explorer to open the Monitoring Server Reports page.
6. On the Monitoring Reports page, in the upper-right corner, click Dashboard.
3. On the Monitoring Server Reports page, view each report listed under Call Diagnostic Reports
(Per User) and review the collected data.
4. On the Monitoring Server Reports page, review each report listed under Call Diagnostic Reports
and review the collected data.
5. On the Monitoring Server Reports page, view each report listed under Media Quality Diagnostic
Reports and review the collected data.
6. In one of the reports, at the uppermost part of the page, click the Save button, and choose Excel
from the drop-down list.
Results: After completing this exercise, you should have reviewed the collected CDR and QoE data
displayed on the Dashboard. You should have also reviewed several reports from each of the four
categories of reports, including manipulating the data displayed and understanding how to export the
reports to different formats.
MCT USE ONLY. STUDENT USE PROHIBITED
L9-1
To begin this lab, you must connect to the appropriate virtual machines by using the following steps:
1. On the host computer, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not started:
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not started:
a. Right-click 20336B-LON-ROUT1-03, and then click Start.
b. Right-click 20336B-LON-ROUT1-03, and then click Connect.
5. In the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not started:
6. In the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not started:
a. Right-click 20336B-LON-SQL2-03, and then click Start.
7. In the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not started:
a. Right-click 20336B-LON-FE1-03, and then click Start.
b. Right-click 20336B-LON-FE1-03, and then click Connect.
8. In the Virtual Machines list, if the virtual machine, 20336B-LON-EDGE1-03, is not started:
a. Right-click 20336B-LON-EDGE1-03, and then click Start.
b. Right-click 20336B-LON-EDGE1-03, and then click Connect.
9. In the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not started:
a. Right-click 20336B-LON-EX1-03, and then click Start.
11. When 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine Connection window.
MCT USE ONLY. STUDENT USE PROHIBITED
L9-3
12. On the host, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
15. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
16. Under Remote audio recording, click Record from this computer, and then click OK.
17. Click the General tab.
19. In the User name box, type Adatum\Adam, and then click Connect.
20. On the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Connect.
21. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
22. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
23. In the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not started:
a. Right-click 20336B-RED-SQL1-03, and then click Start.
24. In the Virtual Machines list, if the virtual machine, 20336B-RED-FE1-03, is not started:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
27. On the host, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
29. Click the Local Resources tab, and then, under Remote audio, click Settings.
30. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
31. Under Remote audio recording, click Record from this computer, and then click OK.
32. Click the General tab.
34. In the User name box, type Adatum\Alex, and then click Connect.
35. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Connect.
MCT USE ONLY. STUDENT USE PROHIBITED
L9-4 Core Solutions of Microsoft® Lync® Server 2013
36. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
37. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, click Start, click Administrative Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
Important All connections to LON-CL1 and RED-CL1 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
2. On the Welcome to Topology Builder page, select Download Topology from existing deployment,
and then click OK.
3. In the Save Topology As window, navigate to the desktop and save the topology as Lab9.tbxml.
4. In the Topology Builder, right-click Lync Server, and then click Edit Properties.
You will see the option of adding another SIP Domain, editing the simple URLs and be able to view which
front-end pool is the Central Management Server.
6. Expand Lync Server\London (Site 0)\Lync Server 2013\Enterprise Edition Front End pools.
8. Note that on the Edit Properties page, you can configure the following:
a. General Properties
b. Resiliency–Associated backup pools. Failover and Failback settings.
10. Click File, and then click Exit to close the Lync Server Topology Builder.
Note In a typical situation where you would like to see changes applied, you would have to publish
the topology. For the purpose of this lab, we are exploring the Lync Server Topology Builder, and will
not be publishing the changes.
1. On LON-FE01, press the Windows key, type Lync, and then click Lync Server Control Panel.
2. In the Select URL dialog box, click https://lon-poolweb-int.adatum.com/cscp, and then click OK. In
the Windows security box, type Administrator, with the password, Pa$$w0rd
3. Notice all the tabs on the left. Click between them and become familiar with what each tab contains.
5. In the Status tab, note that you are able to view the services and replications status of all the servers
in the Lync 2013 topology.
6. Double-click lon-fe01.adatum.com to view details about the status of that particular server.
7. On the Computer Details page for lon-fe01.adatum.com, click Get service status to view which
services are started or stopped. From the Action button, you can start or stop a service as required.
8. Also notice that the database mirroring status can be seen on this page if you have database
mirroring configured for this server.
9. On the left, click the Conferencing tab to create a new Conferencing Policy that will limit video
usage in a conference and apply it to a user.
10. On the Conferencing Policy tab, click New, and then click User Policy.
11. Name the policy, Limited User Video. Under Organizer Policy, in the Audio/Video: setting, click
Enable IP audio in the drop-down box.
14. Highlight Adam Barr, click Action, and then click Assign Policies.
15. Under Conferencing policy, from the drop-down list click Limited User Video.
16. You can view the policy by clicking View or just click OK to apply.
17. Close the Lync Server Control Panel, in pop-up, click Yes.
Task 4: Use Lync Server Management Shell to get user data and replication status.
By now, you should be familiar with Lync Server Management Tool through experience in previous
labs.
1. On LON-FE01, press the Windows key, type Lync, and then click Lync Server Management Shell.
2. Most of the tasks have been done by using the Lync Server Control Panel. These tasks can also be
done through the Lync Server Management Shell.
Tip: If you are not familiar with Windows PowerShell and the Lync Server Management Shell
commands, you can use some facilities to help you. After you have started typing the start of a
command, you can press the Tab key, which will scroll through the available cmdlets for that specific
MCT USE ONLY. STUDENT USE PROHIBITED
L9-6 Core Solutions of Microsoft® Lync® Server 2013
action. When in doubt, you can use the Get-Help <cmdlet name> -Full, for example, Get-Help
New-CsConferencingPolicy –Full.
3. You will use the Lync Server Management Shell to get the replication status and service status of lon-
fe01.adatum.com.
4. To check the replication status of the Central Management Store (CMS), in the Lync Server
Management Shell window, type the following command and press enter.
Get-CSManagementStoreReplicationStatus | FT
5. To only highlight the servers where the CMS is out of sync, type the following command and press
enter.
You should note if any of the servers experience any CMS replication issues.
6. Next we will check to see if all of the Lync services are running. Type the following command and
press enter:
Note that the Limited User Video Conferencing Policy has been assigned to Adam.
9. Close the Lync Server Management Shell.
Note: There are many tasks that can be completed by using the Lync Server Management Shell,
especially when you want to automate bulk tasks.
Task 5: Use Network Monitor to view Real Time Protocol (RTP) traffic.
1. Log on to LON-FE01. Navigate to D:\ and install the following as Administrator:
a. Install Network Monitor 3.4 by double-clicking NM34_x64.exe.
b. Install NetworkMonitor_Parsers_03_04_2978_x64.msi.
i. In the previous versions of Microsoft Network Monitor dialog box, select Yes, and then click
Next.
c. Install NetworkMonitor-LyncParsers-x64.msi.
2. Open the Microsoft Network Monitor shortcut that you created during the installation.
a. If a Microsoft Update Opt-In dialog box appears, clear the Periodically check for updates when…
check box, and then click No.
3. In the Select network section, select the network that has an IPv4 Address of 172.16.0.31 (The name of
the interface will vary depending on your local setup).
4. Click the Parser Profiles drop-down at the upper-right. Select NetworkMonitor Parsers for Lync,
and then select Lync.
7. With the Lync Parsers loaded, you will see a lot of Lync-based traffic when you click My Traffic.
8. In the Display Filter window, type RTP, and then click Apply.
a. On LON-CL1, signed in as Adatum\Adam, Microsoft Lync 2013 should be open already. If not,
open Microsoft Lync 2013.
b. On RED-CL1, signed in as Adatum\Alex, Microsoft Lync 2013 should be open already. If not,
open Microsoft Lync 2013:
c. Start a conference with Alex Darrow as Adam Barr:
i. On LON-CL1, in the Microsoft Lync window, click the drop-down arrow next to the gear icon,
and then click Meet Now.
ii. If a Join Meeting Audio dialog box appears, select Use Lync, and select Don’t show this
again, and then click OK.
iii. In the new conversation window, click the People icon, and then click the Invite More
People button.
iv. In the Invite by Name or Phone Number dialog box, type Alex. Select the Alex Darrow
checkbox, and then click OK.
Note: If Alex is already in Adam’s contact list, you will not need to search for him. You can simply click
Alex Darrow if he is already listed
d. On RED-CL1, Alex must click the Adam Barr Conference Call notification that comes up on his
screen. If a Join Meeting Audio dialog box appears, select the Use Lync and the Don’t show this
again check boxes, and then click OK.
b. If you click the first packet, view the Frame Details pane.
c. Expand the RTP field.
Results: At the end of this exercise, you will see how Microsoft Network Monitor with Lync Parsers can be
a useful tool for troubleshooting. However, you will need to practice this regularly to gain more familiarity
with this tool.
MCT USE ONLY. STUDENT USE PROHIBITED
L9-8 Core Solutions of Microsoft® Lync® Server 2013
Get-CSClsConfiguration
4. Next, check and configure a provider. The provider defines the components of a Lync Server 2013
that will be traced, the type of messages (for example, fatal, error, or warning) to collect, and the flags
(for example, TF_Connection or TF_Diag). To retrieve provider information about a scenario, type the
following command (note the providers “built into the Always on Scenario”).
5. Start a logging scenario with the Centralized Logging Service by typing the following command and
press enter.
Note: The AlwaysOn scenario has no default duration. This scenario will run until you explicitly stop it with
the Stop-CsClsLogging cmdlet. For details, see Stop-CsClsLogging. For all other scenarios, the default
duration is four hours. Press Enter to run the command.
Note: It may take some time (30 to 60 seconds) for the command to run and to receive the status from
the computers in your deployment.
Important: You can have a total of two scenarios running on any given computer at any time. If the
command is global in scope, all of the computers in your deployment will run the scenario or scenarios.
To start a third scenario, you must stop logging on the computer, pool, site, or global scope that you want
to run the new scenario on. If you have started a global scope, you can stop logging for one or both of
the scenarios on one or more computers and pools. For more information about managing which
scenarios are running, see “Using Stop for the Centralized Logging Service” and “Stop-CsClsLogging.”
6. Start a second logging scenario (AudioVideoConferencingIssue) with the Centralized Logging Service
by typing the following command and press enter.
1. On LON-CL1 as adatum\adam, Microsoft Lync 2013 should be open already. If not, open Microsoft
Lync 2013.
2. On RED-CL1 as adatum\alex, Microsoft Lync 2013 should be open already. If not, open Microsoft
Lync 2013.
a. On LON-CL1, in the Microsoft Lync window, click the drop-down arrow next to the gear icon, and
then click Meet Now.
b. If a Join Meeting Audio dialog box appears, select the Use Lync and don’t show this again
check boxes, and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L9-9
c. In the new conversation window, click the People icon, and then click the Invite More People
button.
d. In the Invite by Name or Phone Number dialog box, type Alex, and then press Enter. Select Alex
Darrow, and then click OK.
Note: If Alex is already in Adam’s contact list, you will not need to search for him. You can simply
click Alex Darrow if he is already listed
4. On RED-CL1, Alex must click the Adam Barr Conference Call notification that comes up on his
screen. If a Join Meeting Audio dialog box appears, select the Use Lync and don’t show this again
check boxes, and then click OK. After generating audio traffic and sharing content, you may end the
conference.
Sync-CsClsLogging
3. Execute a search against the currently running logging scenario and output the results to a file by
executing the following command, and press enter.
4. Stop the AudioVideoConferencingIssue logging scenario by entering the following command and
press Enter.
Task 4: Use Snooper from the Lync Debugging Tools to view the logfile output.
You can view the logs generated from the Search-CsClsLogging cmdlet with the Snooper utility,
which is found in the Lync Debugging Tools.
1. If Lync Debug Tools has not already been installed, on LON-FE01, open File Explorer and navigate
to D:\ and install LyncDebugTools.msi. Accept the Licensing Agreement, and all of the defaults.
Click Install.
2. In File Explorer, navigate to C:\Program Files\Microsoft Lync Server 2013\Debugging Tools\ and
double-click Snooper.
3. In Snooper, click on the File menu, and click Open File.
To begin this lab, you must connect to the appropriate virtual machines by using the following steps:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
8. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-FE1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-WAC01-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
15. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
16. In the Remote Desktop Connection window, click Options.
17. Click the Local Resources tab, and then, under Remote audio, click Settings.
18. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
19. Under Remote audio recording, click Record from this computer, and then click OK.
24. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
25. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
26. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
27. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
28. In the Remote Desktop Connection window, click Options.
MCT USE ONLY. STUDENT USE PROHIBITED
L10-3
29. Click the Local Resources tab, and then, under Remote audio, click Settings.
30. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
31. Under Remote audio recording, click Record from this computer, and then click OK.
34. In the User name box, type Adatum\Adam, and then click Connect.
36. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
37. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
3. If not, right-click the service, and then click Start.
Important: All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
Task 2: Create and assign permissions for the SQL mirroring file share.
1. On LON-DC1, open File Explorer by clicking the folder icon on the taskbar.
2. Under Computer, right-click Local Disk (C:), and then click New > Folder.
3. Rename the newly created folder as SQLMirrorShare.
4. Right-click the newly created folder, SQLMirrorShare, and then select Properties.
5. Click the Sharing tab, and then click the Advanced Sharing button.
6. Select the “Share this folder” check box.
8. In the Permissions for SQLMirrorShare dialog box, click the Everyone group, and then click the
Remove button.
9. Click the Add button. Click the Object Types button. In the Object Types dialog box, select the
Service Accounts check box. Leave the other check boxes as they are, and then click OK.
10. In the Enter the object names to select text box, type Administrators;SQLSvc, and then click
Check Names. Ensure that both entries are underlined, and then click OK.
Note: The SQL Services were configured to run under the Adatum\SQLSvc$ account as part
of the classroom setup. These steps ensure that the service has appropriate permissions to the
backup location used for the mirroring configuration.
11. In the Permissions for SQLMirrorShare dialog box, click the Administrators group, and then select
the Full Control check box in the Allow column.
MCT USE ONLY. STUDENT USE PROHIBITED
L10-4 Core Solutions of Microsoft® Lync® Server 2013
12. In the Permissions for SQLMirrorShare dialog box, click the SQLSvc user account, and then select
the Full Control check box in the Allow column.
13. Click Ok to return to the Advanced Sharing Dialog box. Click OK, and then click Close.
2. On the Topology Builder page, verify that Download Topology from existing deployment is
selected, and then click OK.
3. On the Save Topology as page, browse to C:\LabFiles, in the File Name box, type
AdatumTopologyWithHA, and then click Save.
4. In the Topology Builder, expand Lync Server, expand London (Site 0), expand Lync Server 2013, and
then expand Enterprise Edition Front End pools.
6. On the Edit Properties page, under Associations, select the Enable SQL store mirroring check box,
and then click New.
7. In the Define New SQL Server Store window, in the SQL Server FQDN box, type lon-
sql02.adatum.com
8. Select Named Instance, and then, in the box, type LYNC.
Note: The Instance name must be capitalized. Leave the Edit Properties page open.
9. Take note of the default mirror port number given, and then click OK.
10. In the Edit Properties dialog box, under Associations, select the Use SQL Server mirroring witness to
enable automatic failover check box, and then click New.
11. In the Define New SQL Server Store window, in the SQL Server FQDN box, type lon-
dc1.adatum.com
12. Select Named Instance, and then, in the box, type LYNC.
Note: The Instance name must be capitalized. Leave the Edit Properties page open.
13. Take note of the default witness port number given, and then click OK.
3. In the Edit Properties window, in the Mirror port number box, type 5022, and then click OK. (Hint:
step 9 of the previous task)
2. On the Publish the topology page, review the actions that should be completed, and then click
Next.
3. On the Create mirror databases page, verify that the lon-sql02.adatum.com check box is selected.
4. Click lon-sql02.adatum.com, and then click Settings.
5. In the Mirror Database Settings window, in the Path to file share box, type \\lon-
dc1.adatum.com\SQLMirrorShare, and then click OK.
6. Return to the Create mirror databases page, and then click Next.
Wait as the topology is published. This will take about 3-4 minutes.
7. On the Publishing wizard complete page, verify that all steps show as Success.
8. On the Publishing wizard complete page, click Finish.
3. In Object Explorer, click the plus sign (+) to expand the Databases folder.
4. Notice that the databases listed show as (Principal, Synchronized).
8. On LON-SQL02, click Start, and then click SQL Management Studio (or use the shortcut on the
taskbar).
9. In the Connect to Server dialog box, under Server name, enter LON-SQL02\LYNC, and then click
Connect.
10. In Object Explorer, click the plus sign (+) to expand the Databases folder.
11. Notice that the databases listed show as (Mirror, Synchronized / Restoring).
Results: After completing this exercise, you should have used Topology Builder to establish database
mirroring between two defined SQL instances, and verified the configuration by using the SQL
Management Studio tool.
MCT USE ONLY. STUDENT USE PROHIBITED
L10-6 Core Solutions of Microsoft® Lync® Server 2013
2. Sign in as Adam@adatum.com.
2. Sign in as Alex@adatum.com.
3. On LON-CL1, in the Lync client, right-click the Alex Darrow contact, and then click Call > Lync Call.
2. Observe the output, noting the values for StateOnPrimary and StateOnMirror
For example, for the rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : Principal
StateOnMirror : Mirror
MirroringStatusOnPrimary : synchronized
MirroringStatusOnMirror : synchronized
3. Fail over the databases to the mirrored instance. On LON-FE01, open Lync Management Shell, type
the following command, and then press Enter.
4. At the Confirm – Are you sure you want to perform this action prompt, type A, and then press Enter.
5. On LON-FE01, open Lync Management Shell, type the following command, and then press Enter.
6. Observe the output, noting the values for StateOnPrimary and StateOnMirror
For example, for the rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : Mirror
StateOnMirror : Principal
MirroringStatusOnPrimary : synchronized
MirroringStatusOnMirror : synchronized
MCT USE ONLY. STUDENT USE PROHIBITED
L10-7
1. On LON-CL1, in the main Lync client, select the Presence drop-down under Adam Barr’s name (which
currently reads “Available”) and then select Reset Status.
Notice the Presence status changes to “In a Call”.
2. Observe the output, noting the values for StateOnPrimary and StateOnMirror
For example, for the rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : Mirror
StateOnMirror : Principal
MirroringStatusOnPrimary : synchronized
MirroringStatusOnMirror : synchronized
3. Fail the database instances back to the original primary SQL instance. On LON-FE01, open Lync
Management Shell, type the following command, and then press Enter.
4. At the Confirm – Are you sure you want to perform this action prompt, type A, and then press Enter.
5. Observe the output, looking for Success in the FailoverResult column.
6. On LON-FE01, in Lync Server Management Shell, type the following command, and then press Enter.
7. Observe the output, noting the values for StateOnPrimary and StateOnMirror
For example, for the rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : Principal
StateOnMirror : Mirror
MirroringStatusOnPrimary : synchronized
MirroringStatusOnMirror : synchronized
8. Leave Lync Management Shell open for the next exercise.
Results: After completing this exercise, you should have used the Lync Server 2013 Management Shell to
perform manual failover of the databases from the primary SQL instance to the mirror SQL instance, and
back.
MCT USE ONLY. STUDENT USE PROHIBITED
L10-8 Core Solutions of Microsoft® Lync® Server 2013
2. Sign in as Adam@adatum.com.
3. On LON-CL1, in the Lync client, right-click the Alex Darrow contact, and then click Call > Lync Call.
2. In the Services window, right-click the SQL Server (LYNC) service, and then click Stop.
2. Observe the output, noting the values for StateOnPrimary and StateOnMirror For example, for the
rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : StatusUnavailable
StateOnMirror : Principal
MirroringStatusOnPrimary :
MirroringStatusOnMirror : disconnected
2. Observe the output, noting the values for StateOnPrimary and StateOnMirror For example, for the
rtcab database, the output should appear as follows:
DatabaseName : rtcab
StateOnPrimary : Mirror
StateOnMirror : Principal
MirroringStatusOnPrimary : synchronized
MCT USE ONLY. STUDENT USE PROHIBITED
L10-9
MirroringStatusOnMirror : synchronized
3. If desired, you can move the instances back to the primary SQL instance at this time, by using the
following command in Lync Management Shell, and then pressing Enter.
4. At the Confirm – Are you sure you want to perform this action prompt, type A, and then press
Enter.
Results: After completing this exercise, you should have observed the automatic failover process between
mirrored databases in Lync Server 2013, by using the Lync Management Shell to verify.
MCT USE ONLY. STUDENT USE PROHIBITED
L10-10 Core Solutions of Microsoft® Lync® Server 2013
MCT USE ONLY. STUDENT USE PROHIBITED
L11-1
To begin this lab, you must connect to the appropriate virtual machines by using the following steps:
1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.
2. In the Virtual Machines list, if the virtual machine, 20336B-LON-DC1-03, is not running:
3. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.
4. In the Virtual Machines list, if the virtual machine, 20336B-LON-ROUT1-03, is not running:
c. In the Virtual Machine Connection window, wait until the virtual machine has booted up
completely before continuing.
5. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL1-03, is not running:
6. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-SQL2-03, is not running:
7. On Host1, in the Virtual Machines list, if the virtual machine, 20336B-LON-CL1-03, is not running:
a. First ensure that 20336B-LON-SQL1-03 has booted completely before starting this virtual
machine.
9. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-SQL1-03, is not running:
10. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-EX1-03, is not running:
11. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-RED-CL1-03, is not running:
12. On Host2, in the Virtual Machines list, if the virtual machine, 20336B-LON-WAC01-03, is not running:
a. First ensure that 20336B-RED-SQL1-03 has booted completely before starting this virtual
machine.
15. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
16. In the Remote Desktop Connection window, click Options.
17. Click the Local Resources tab, and then, under Remote audio, click Settings.
18. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
19. Under Remote audio recording, click Record from this computer, and then click OK.
24. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
25. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.
26. On Host1, when 20336B-LON-CL1-03 has booted up completely, close the Virtual Machine
Connection window.
27. On Host1, click Start, click All Programs, click Accessories, and then click Remote Desktop
Connection.
28. In the Remote Desktop Connection window, click Options.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-3
29. Click the Local Resources tab, and then, under Remote audio, click Settings.
30. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.
31. Under Remote audio recording, click Record from this computer, and then click OK.
34. In the User name box, type Adatum\Adam, and then click Connect.
36. In the Remote Desktop Connection window, select the Don’t ask me again for connections to this
computer check box, and then click Yes.
37. In the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK
Verify that all services set to Automatic have started on all virtual machines. Most notably, check the
Microsoft Exchange, Lync Server 2013, and Microsoft SQL Server® services. To do so, complete the
following steps:
1. On each virtual machine, open Server Manager, click Tools, and then click Services.
2. In the Services console, verify that all services set to Automatic start have started.
3. If not, right-click the service, and then click Start.
Important: All connections to LON-CL1-03 and RED-CL1-03 will require using a Remote Desktop
Connection with remote audio playback and remote audio recording enabled, unless otherwise
specifically instructed.
Note: If this task was already completed in Lab 8, you will receive a message stating, “The object
RTCUniversalServerAdmins is already in the list and cannot be added a second time.” Click OK to dismiss
this.
2. On the Topology Builder page, verify that Download Topology from existing deployment is selected,
and then click OK.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-4 Core Solutions of Microsoft® Lync® Server 2013
3. On the Save Topology as page, browse to C:\LabFiles, in the File Name box, type
AdatumTopologyWithDR, and then click Save.
4. In the Topology Builder, expand Lync Server, expand London (Site 0), expand Lync Server 2013, and
then expand Enterprise Edition Front End pools.
5. Right-click lon-pool.adatum.com, and then click Edit Properties.
6. Click Resiliency.
7. Select the Associated backup pool check box. In the drop-down box, select red-pool.adatum.com.
8. Select the Automatic failover and failback for voice check box. Leave the default values for Voice
failure detection interval and Voice failback interval, and then click OK.
9. In Topology Builder, expand Redmond (Site 1), expand Lync Server 2013, and then expand Enterprise
Edition Front End pools.
10. Click red-pool.adatum.com. In the right pane, under Resiliency, notice that the associated backup
pool is automatically set as lon-pool.adatum.com. This is because pool pairing follows a 1:1
relationship.
2. On the Publish the topology page, review the actions that should be completed, and then click
Next.
3. On the Create databases page, ensure that the red-sql01.adatum.com\Lync check box is selected,
and then click Next. Wait as the topology is published.
4. On the Publishing wizard complete page, verify that all steps show as Success.
5. On the Publishing wizard complete page, click the Click here to open to-do list hyperlink. A new
file will open in Notepad. Observe the steps listed. (These steps will be performed in the upcoming
tasks of this exercise). Close Notepad.
3. On the Lync Server 2013 page, next to Step 2: Setup or Remove Lync Server Components, click Run.
4. On the Set Up Lync Server Components page, click Next. This will take a few minutes.
5. On the Executing Commands page, when the Task Status shows Completed, click Finish.
6. On RED-FE01, click Start, and then click Lync Server Management Shell.
7. Type the following command, and then press Enter.
8. At the command prompt, type the following command, and then press Enter.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-5
.\Bootstrapper.exe
2. In the Services list, scroll down to Lync Server Backup Service. Notice that the service is not running.
Right-click Lync Server Backup Service, and then click Start.
3. On RED-FE01, click Start, click Administrative Tools, and then double-click Services.
4. In the Services list, scroll down to Lync Server Backup Service. Notice that the service is not running.
Right-click Lync Server Backup Service, and then click Start.
5. Repeat step 4 for the Lync Server File Transfer Agent and Lync Server Master Replicator Agent
services.
Note: Another way to perform the tasks in steps 3-5 on RED-FE01 is to open Lync
Management Shell, type the following command, and then press Enter.
Start-CsWindowsService
3. At the Are you sure you want to continue prompt, press Enter.
4. To verify the state, type the following command, and then press Enter.
8. At the Are you sure you want to continue prompt, press Enter.
9. To verify the state, type the following command, and then press Enter.
Results: After completing this exercise, you should have used Topology Builder to configure pool pairing
between two existing pools.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-6 Core Solutions of Microsoft® Lync® Server 2013
2. Sign in as Adam@adatum.com.
Note: This task may not be necessary because Adam Barr may already be signed in.
2. Sign in as Alex@adatum.com.
Note: This task may not be necessary because Alex Darrow may already be signed in.
Task 3: Start a Lync Online Meeting on LON-CL1 and join the meeting from RED-CL1.
1. On LON-CL1, in the Lync 2013 main window, click the down-arrow next to the gear icon, and then
click Meet Now.
2. In the Join Meeting Audio dialog box, ensure the Use Lync option button is selected, and then click
OK.
3. In the conversation window, point to the People icon, and then click Invite More People.
4. Click Alex Darrow, and then click OK.
5. On RED-CL1, you will see a toast for the conference call invitation appear. Click the toast to accept
the invitation and join the meeting.
2. In the Services window, right-click the Lync Server Front-End service, and then click Stop.
3. On RED-CL1, after about five minutes, notice that Alex’s client has signed back in, but is in resiliency
mode (Limited Functionality). Also notice that functionality is now restored in the online meeting.
2. At the Are you sure you want to perform this action prompt, press Enter.
2. Notice that the Lync Online Meeting is still in progress, with all functionality available.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-7
2. In the Services window, right-click the Lync Server Front-End service, and then click Start.
3. Wait for the service to start successfully. This will take a few minutes.
2. At the Are you sure you want to perform this action prompt, press Enter.
Notice that the Lync Online Meeting is still in progress, with all functionality available.
Results: After completing this exercise, you will have observed client behavior during a pool failure. You
will have also used Lync Management Shell to invoke failover to the backup pool, to restore services for
the users on the failed pool.
MCT USE ONLY. STUDENT USE PROHIBITED
L11-8 Core Solutions of Microsoft® Lync® Server 2013
MCT USE ONLY. STUDENT USE PROHIBITED
L12-1
• Employees of Adatum Corporation use Lync 2013 for IM, phone, and meeting capabilities at the top
level, along with the contact list.
• Adatum Corporation employees must assign their contacts various levels of access, depending on
their relationship with them, such as Family or Workgroup.
• Adatum Corporation can use the enhanced Presence and privacy relationships to show Presence for
individuals.
• Adatum Corporation needs external user access because most of the communication involves people
outside the firewall.
• Adatum Corporation wants to integrate Office 2013 applications and Windows 7.
Phase 3. In this phase, you need to deploy Lync Server 2013 pilot pool. To do this, you need to deploy
a new Lync Server 2013 pilot pool and then verify the coexistence of the pilot pool with the legacy
pool. Some important tasks are:
Phase 5. In this phase, you configure the pilot pool. To do this, you need to:
1. Connect the pilot pool to legacy Edge Servers.
Phase 6. In this phase, you move users to the pilot pool. You can move a single user or groups of
users to the new Lync Server 2013 deployment by using either Lync Server Control Panel or Lync
Server Management Shell. To do this, you need to:
Phase 7. In this phase, you need to add Lync Server 2013 Edge Server to the pilot pool. The sub-
phases are as follows:
Phase 9. In this phase, you need to complete the post-migration tasks. Some of the important tasks
include:
12. Verify that all Exchange UM contact objects are removed from the legacy pool.
Phase 10. In this phase, you need to decommission the legacy site. To do this, you need to:
1. Remove server and server roles from the Office Communications Server environment.
Task 2: List the phases of migration from Lync Server 2010 to Lync Server 2013.
Phase 1. In this phase, you need to plan the migration from Lync Server 2010 to Lync Server 2013.
You can either plan for a single site migration or a multi-site migration.
Phase 2. In this phase, you need to prepare for migration. To do this, you need to:
Phase 3. In this phase, you need to deploy the Lync Server 2013 pilot pool. To do this, you need to
deploy a new Lync Server 2013 pilot pool, and then verify the coexistence of the pilot pool with the
legacy pool. Some important steps are:
Phase 4. In this phase, you move users to the pilot pool. You can move a single user or groups of
users to the new Lync Server 2013 deployment by using either Lync Server Control Panel or Lync
Server Management Shell. To do this, you need to:
Phase 5. In this phase, you need to add Lync Server 2013 Edge Server to the pilot pool. The tasks for
this phase are as follows:
1. Deploy pilot Edge Servers.
Phase 8. In this phase, you need to decommission the legacy site. To do so, perform the following
important steps:
2. Move the Lync Server 2010 Configuration Management Server to Lync Server 2013.
3. Remove the Archiving server association.
5. Remove the Enterprise Edition front-end server or Standard Edition front-end server.