Lab 01 - Deploying Microsoft Lync Server 2010

Microsoft® Lync™ Server 2010 Ignite In-a-Box

Lab 1: Deploying Microsoft Lync Server 2010

DISCLAIMER

© 2010 Microsoft Corporation. All rights reserved.

Microsoft®, Active Directory®, Hyper-V™, Internet Explorer®, Lync™, PowerShell®, Silverlight®,

SQL Server®, Visual C++®, Windows®, and Windows Server® are either registered trademarks

or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their

respective owners.

THE CONTENTS OF THIS PACKAGE ARE FOR INFORMATIONAL AND TRAINING PURPOSES ONLY AND ARE

PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT

LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND

NON-INFRINGEMENT.

No part of the text or software included in this training package may be reproduced or

transmitted in any form or by any means, electronic or mechanical, including photocopying,

recording, or any information storage and retrieval system, without permission from

Microsoft®. Because Microsoft must respond to changing market conditions, it should not be

interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the

accuracy of any information presented after the date of publication. The names of actual

companies and products mentioned herein may be the trademarks of their respective owners.

To obtain authorization for uses other than those specified above, please visit the Microsoft

Copyright Permissions Web page at http://www.microsoft.com/about/legal/permissions

This content is proprietary and confidential, and is intended only for users described in the

content provided in this document. This content and information is provided to you under a

Non-Disclosure Agreement and cannot be distributed. Copying, disclosing all or any portion of

the content and/or information included in this document is strictly prohibited.

http://www.microsoft.com/about/legal/permissions

Table of Contents Lab: Deploying Microsoft Lync Server 2010 ................................................................................................... 1

Exercise 1: Preparing Active Directory Domain Services and Installing the Lync Server 2010

Topology Builder ......................................................................................................................................... 6

Exercise 2: Starting the Topology Builder and Defining a Enterprise Edition Front End Pool. .......... 9

Exercise 3: Preparing the Environment for Lync Server 2010 and then Publishing the Topology. .... 13

Exercise 4: Deploying Lync Server 2010 ................................................................................................... 16

Exercise 5: Validating the Deployment Using the Lync Server 2010 Control Panel ............................ 19

Exercise 6 (Optional): Exploring the Topology Builder to Define a Standard Edition Front End

Topology ..................................................................................................................................................... 21


1 ©2010 Microsoft – Confidential

Lab: Deploying Microsoft Lync Server 2010

During this lab, you will use the DC01, SQL01, and LS-FE, virtual machines (VMs) to gain

hands-on experience with deploying a Microsoft® Lync™ Server 2010 topology using the new

Lync Server 2010 Topology Builder and deployment process.

Estimated time to complete this lab: 90 minutes

Before You Begin This lab does not depend on the completion of any previous labs. Log on to the Microsoft

Hyper-V™ virtual machines either by using the CTRL+ALT+END key combination or by

clicking the CTRL+ALT+DELETE button on the toolbar.

What You Will Learn After completing the exercises, you will be able to:

Prepare Microsoft Active Directory® Domain Services (AD DS) for

Lync Server 2010.

Install and start the Lync Server 2010 Topology Builder.

Define an Enterprise Edition Front End topology.

Define an Archiving and a Monitoring server.

Publish a Lync Server 2010 topology.

Deploy Lync Server 2010.

Define a Standard Edition Front End topology.

Define an Edge pool.

Scenario

Contoso Ltd. has decided to deploy Microsoft Lync Server 2010 and you want to use the new

Lync Server 2010 Topology Builder tool to define and publish the architecture. You will

explore the Lync Server 2010 Topology Builder and gain familiarity with defining Enterprise

Edition Front End and other server roles. The final exercise is optional and goes over

defining a Standard Edition Front End topology.

There is a pre-staged version of the topology that you may publish later in this lab, if you

choose to. You will only deploy one server role in this lab, the Front End server on LS-FE.

The process for deploying other server roles is the same, except that not all roles require the

same certificates.


©2010 Microsoft – Confidential 2

Exercise 0: Preparing the Lab Environment In this exercise, you will prepare the lab environment by connecting to the necessary VMs

using the Microsoft Windows Server® 2008 Release 2 (R2) Hyper-V Manager.

Virtual Machines

The entire Microsoft Lync Server 2010 Ignite In-a-Box course uses the following VMs:

Virtual Machines

LS-FELS 2010

Front End10.0.0.30

SQL01SQL Server 2008

10.0.0.20

LS-ARC-MONMonitoring &

Archiving10.0.0.40

R2-FEOCS 2007 R2

Front End10.0.0.50

CLIENT01Internal Client

10.0.0.90

LS-SBSBranch Office

20.0.0.253

CLIENT02Branch Client

20.0.0.95

RAS01RRAS Server

10.0.0.8920.0.0.89

DC01DC, CA, DNS

Exchange 2010 SP110.0.0.10

CLIENT03Internal Client

10.0.0.95

Snapshots

The set of virtual machines has two snapshots that correspond with different labs. The two

snapshots are INSTALL LAB START and CORE LAB START.

INSTALL LAB START is required for beginning Lab 1. Only the DC01, SQL01 and

LS-FE VMs have this snapshot.

CORE LAB START is required for starting Lab 2 and is the main snapshot to be

used for the rest of the labs. Labs 2 through 10 all build off of each other and

require the previous labs being complete.

Lab Preparation

In this section, you will verify that the correct virtual machines are started and that the

INSTALL LAB START snapshot has been applied to all of the needed virtual machines on



both hosts. You will then connect to the virtual machines and verify that all of the services

have started.

This lab uses the following VMs with the INSTALL LAB START snapshot applied.

Lab 1 Virtual Machines

LS-FELS 2010

Front End10.0.0.30

SQL01SQL Server 2008

10.0.0.20

DC01DC, CA, DNS

Exchange 201010.0.0.10

On Host1:

DC01 – Domain Controller, Domain Name System (DNS), certificate authority

(CA), Microsoft Exchange 2010 SP1, with 4096 megabytes (MB) of memory

On Host2:

SQL01 – Lync Server 2010 Back End with Microsoft SQL Server™ 2008 SP1 with

2048 MB of memory

LS-FE – Lync Server 2010 Front End with 4096 MB of memory

Tasks

1. Verify DC01 and then connect and check services.

a. On Host1, verify that the computer date and time are correct.

b. Click Start and then click Hyper-V Manager.

c. In Hyper-V Manager, under Virtual Machines, click DC01.

d. Under Snapshots, right-click the INSTALL LAB START snapshot and

then click Apply.

e. At the Apply Snapshot prompt, click Apply.

f. Under Virtual Machines, right-click DC01 and then click Start.

g. Right-click DC01 again and then click Connect.

Wait for this VM to fully start up before continuing.

h. Verify that the virtual machine has automatically logged in as

Contoso\Administrator.



i. Click Start, click Administrative Tools, and then click Services.

j. In Services, verify that all services listed with a Startup Type of

Automatic or Automatic (Delayed Start) are started. Most

importantly, check the Exchange Services.

Note:

There may be a Windows Licensing Monitoring Service that shows as Automatic but is not started. This service can be ignored on all of the virtual machines.

If any of these services are not started, right-click each service and then

click Start.

k. When done, close the Services console.

2. Apply the INSTALL LAB START snapshot to SQL01 and then connect and

check services.

a. On Host2, verify that the computer time and date are correct.

b. In Hyper-V Manager, under Virtual Machines, click SQL01.

c. Under Snapshots, right-click the INSTALL LAB START snapshot and

then click Apply.

d. At the Apply Snapshot prompt, click Apply.

e. Under Virtual Machines, right-click SQL01 and then click Start.

f. Right-click SQL01 again and then click Connect.

g. Verify that the virtual machine has automatically logged in as


h. Click Start, click Administrative Tools, and then click Services.

i. In Services, verify that all services listed with a Startup Type of

Automatic or Automatic (Delayed Start) are started. Most

importantly, check the SQL Server services.


click Start.

j. When done, close the Services console.

3. Apply the INSTALL LAB START snapshot to LS-FE and then connect and

check services.

a. On Host2, in Hyper-V Manager, under Virtual Machines, click LS-FE.



b. Under Snapshots, right-click the INSTALL LAB START snapshot and

then click Apply.

c. At the Apply Snapshot prompt, click Apply.

d. Under Virtual Machines, right-click LS-FE and then click Start.

e. Right-click LS-FE again and then click Connect.

f. Verify that the virtual machine has automatically logged in as


g. Click Start, click Administrative Tools, and then click Services.

h. In Services, verify that all services listed with a Startup Type of

Automatic or Automatic (Delayed Start) are started.


click Start.

i. When done, close the Services console.



Exercise 1: Preparing Active Directory Domain Services and

Installing the Lync Server 2010 Topology Builder

In this exercise, you will prepare Active Directory Domain Services for Lync Server 2010 and then install the Lync Server 2010 Topology Builder. A number of prerequisites have been pre-staged for you in the interest of saving time. The following prerequisites have already been installed:

Microsoft Internet Information Services (IIS) 7.0 Rewrite package

SQL Server 2008 Native Client

SQL Server 2005 Backwards Compatibility tool

Microsoft Visual C++® 2008 Redistributable Package

Microsoft Silverlight®

Microsoft .NET Framework 3.5 with SP1

Microsoft Windows PowerShell® 2.0

The following features have also been preinstalled:

Message Queuing

IIS 7.0 was installed with the following command:

ServerManagerCmd.exe -Install Web-Server Web-Http-Redirect Web-

Scripting-Tools Web-Windows-Auth Web-Asp-Net Web-Log-Libraries

Web-Http-Tracing Web-Basic-Auth

AD DS Tools

Desktop Experience (needed for Lync Server 2010 on Windows Server 2008 R2)

The SQL Server Express local database has also been pre-staged on LS-FE.



Tip:

The command that installed the local CMS database on LS-FE is:

SQLEXPR_x64.exe /Q /HIDECONSOLE /ACTION=Install

/FEATURES=SQLEngine,Tools /INSTANCENAME=RTC /TCPENABLED=1

/SQLSVCACCOUNT="NT AUTHORITY\NetworkService"

/SQLSYSADMINACCOUNTS="Builtin\Administrators"

/BROWSERSVCSTARTUPTYPE="Automatic" /AGTSVCACCOUNT="NT

AUTHORITY\NetworkService" /SQLSVCSTARTUPTYPE=Automatic

This can be done on any server that is going to have a Lync Server 2010 role

installed on it, in order to speed up setup. This command has already been run; do

not run it again.

Tasks

1. Prepare the AD DS schema.

This step extends the Active Directory Domain Services schema by adding new

classes and attributes that are used by Lync Server 2010. This would need to be

run once for each forest in your deployment.

a. On LS-FE, click Start > All Programs > Accessories > Windows

Explorer.

b. In Microsoft Windows Explorer, navigate to

C:\LabFiles\LS2010\Setup\AMD64 and double-click Setup.exe.

There will be a brief delay while setup starts.

c. On the Microsoft Lync Server 2010 (RC) page, leave the default values for

the Installation Location, and then click Install.

d. On the License Agreement page, select I accept the terms in the

license agreement and then click OK.

Wait while setup starts.

e. On the Microsoft Lync Server 2010 (RC) Deployment Wizard page, click

Prepare Active Directory.

f. On the Prepare Active Directory for Lync Server page, next to Step 1:

Prepare Schema, click Run.

g. On the Prepare Schema page, click Next.

Wait as the wizard executes the commands to prepare the schema.

h. When the Task Status shows as Completed, click Finish.

2. Prepare the AD DS forest.



This step creates global settings and universal groups that are used by

Lync Server 2010. This would need to be run once for each forest in your

deployment.

a. On LS-FE, on the Prepare Active Directory for Lync Server page, near

Step 3: Prepare Current Forest, click Run.

b. On the Prepare Forest page, click Next.

c. On the Universal Group Location page, verify that Local Domain is

selected and then click Next.

Wait as the wizard executes the commands to prepare the forest.

d. When the Task Status shows as Completed, click Finish.

3. Prepare the AD DS domain.

This step adds permissions on objects to be used by members of universal

groups and would need to be run once per user domain or server domain.

a. On LS-FE, on the Prepare Active Directory for Lync Server page, next to

Step 5: Prepare Current Domain, click Run.

b. On the Prepare Domain page, click Next.

Wait as the wizard executes the commands to prepare the domain.

c. When the Task Status shows as Completed, click Finish.

d. On the Prepare Active Directory for Lync Server page, click Back.

4. Install the Topology Builder.

a. On LS-FE, in the Lync Server 2010 (RC) Deployment Wizard, click

Install Topology Builder.

Wait for the tool to be installed. This will only take a few seconds and

there will be no prompts.

b. Click Exit to close the Lync Server 2010 (RC) Deployment Wizard.

c. Close Windows Explorer.



Exercise 2: Starting the Topology Builder and Defining a

Enterprise Edition Front End Pool.

In this exercise, you will start the Lync Server 2010 Topology Builder and then create a site.

Topology Builder is a wizard-driven user interface that you use to create your initial

Lync Server 2010 topology, and to make changes to that topology later. With Topology

Builder, your topology is validated before you commit it or begin installing Lync Server 2010

on any servers. The setup process itself on each server is greatly simplified.

You will use the Lync Server 2010 Topology Builder to define an Enterprise Edition Front

End Pool Topology. You will use the Define New Front End Pool wizard.

Tip:

If you want to run through defining a Standard Edition topology, the last exercise in this lab is an optional one that covers Standard Editions.

Tasks

1. Start the Topology Builder.

You will now start the Topology Builder tool and define the default Session

Initiation Protocol (SIP) domain. Your deployment must include at least one

central site and can include zero to many branch sites. A site represents a

geographical location of your network and is a set of computers well connected

by a high-speed, low-latency network, such as a single local area network (LAN)

or two networks connected by a high-speed fiber optic network. Note that

Lync Server 2010 sites are a separate concept from Active Directory sites and

Microsoft Exchange sites.

a. On LS-FE, click Start > All Programs > Microsoft Lync Server 2010

(RC) > Lync Server Topology Builder.

b. In the Topology Builder wizard, on the Welcome to Topology Builder

page, select New Topology and then click OK.

c. On the Save New Topology As window, navigate to the desktop and save

the topology as ContosoTopology.tbxml.

d. On the Create New Topology wizard, on the Define the primary domain

page, in the Primary SIP domain field, type Contoso.com and then

click Next.

e. On the Specify additional supported domains page, leave the fields blank

and then click Next.



f. On the Define the first site page, in the Name field, type Redmond, in

the Description field, type US Main Office and then click Next.

g. On the Specify site details page, in the City field, type Redmond

h. In the State/Province field, type Washington

i. In the Country/Region Code field, type 1 and then click Next.

j. 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.

2. Define the Enterprise Edition Front End Pool using the Topology Builder.

You will now use the Define New Front End Pool wizard to add various

components and save the Topology.

a. On LS-FE, in the Define New Front End Pool wizard, on the Define the

New Front End pool page, notice the information the wizard asks you to

collect, and then click Next.

b. On the Define the Front End pool FQDN page, in the Pool FQDN field,

type lspool01.contoso.com. Verify that Enterprise Edition Front End

Pool is selected and then click Next.

c. On the Define the computers in this Pool page, in the Computer FQDN

field, type LS-FE.contoso.com click Add, and then click Next.

d. On the Select Features page, select the Conferencing, which includes

audio, video and application sharing, Dial-in (PSTN) Conferencing,

Enterprise Voice, and Call Admission Control check boxes, and then

click Next.

e. On the Select collocated server roles page, select the Collocate A/V

Conferencing service and Collocate Mediation Server checkboxes


f. On the Associate server roles with this Front End pool page, select only

the Enable archiving and Enable monitoring check boxes and then

click Next.

g. On the Define the SQL store page, select Define a new SQL store and

then in the SQL Server FQDN field, type sql01.contoso.com

h. Select Named Instance, in the Named Instance field, type LS2010 and

then click Next.

Note: The instance name must be uppercase.



i. On the Define the file share page, select Define a new file share, and

then in the File Server FQDN field, type sql01.contoso.com

j. In the File Share field, type FileShare and then click Next.

k. On the Specify the Web Services URL page, verify that the Override

internal Web Service pool FQDN check box is clear.

l. In the External Base URL field, type webext.contoso.com and then

click Next.

m. On the Specify PSTN gateways page, click New.

n. On the Define New IP/PSTN Gateway page, in the Gateway FQDN or IP

Address field, type 10.1.10.10

o. In the Listening port for IP/PSTN gateway field, type 5060

p. Under Sip Transport Protocol, select TCP and then click OK.

q. Back on the Specify PSTN gateways page, click Next.

r. On the Select an Archiving Server page, click New.

s. On the Define New Archiving Server wizard, on the Define the fully

qualified domain name page, in the FQDN field, type LS-ARC-

MON.contoso.com and then click Next.

t. On the Define the SQL store page, verify that Use a previously defined

SQL store is selected, in the drop-down list select

sql01.contoso.com\LS2010 and then click Next.

u. On the Define the file store page, verify that Use a previously defined

file share is selected, in the drop-down list select

\\sql01.contoso.com\FileShare and then click Finish.

v. Back on the Select an Archiving Server page, click Next.

w. On the Select a Monitoring Server page, click New.

x. On the Define New Monitoring Server wizard, on the Define the fully

qualified domain name page, in the FQDN field, type LS-ARC-

MON.contoso.com and then click Next.

y. On the Define the SQL store page, verify that Use a previously defined

SQL store is selected, in the drop-down list select

sql01.contoso.com\LS2010 and then click Finish.

z. Back on the Select a Monitoring Server page, click Finish.

3. Configure the Administrative URL and the Central Management Server.



Lync Server 2010 requires you to set up a simple Uniform Resource Locators

(URL) for the administrative website.

a. On LS-FE, in the Topology Builder, in the Navigation pane, right-click

Lync Server 2010 (RC) and then click Edit Properties.

b. On the Edit Properties page, under Simple URLs, in the

Administrative access URL field, type https://admin.contoso.com

c. Under Central Management Server, in the Front End server to

install Central Management Server drop-down list, select

lspool01.contoso.com Redmond and then click OK.

Leave the Topology Builder running.



Exercise 3: Preparing the Environment for Lync Server 2010

and then Publishing the Topology.

In this exercise, you will prepare the topology for Lync Server 2010 by adding the

Administrator to the CSAdministrator group and then creating the necessary Domain

Name System (DNS) records.

You will also publish the topology, which includes installing the databases, setting the

configuration store location, and then publishing and enabling the Lync Server 2010

topology.

Note:

There is a fully configured topology Extensible Markup Language (XML) file located in C:\LabFiles named ContosoTopology.tbxml. If you did not create an Topology XML file in the earlier exercise, you can use this file to publish in this exercise.

Tasks

1. Add the Administrator to the CSAdministrator group.

The user that will configure and install Lync Server 2010 must be a member of the

CSAdministrator group. You will add the Administrator account to this group.

a. On DC01, click Start > Administrative Tools > Active Directory Users

and Computers.

b. In the Active Directory Users and Computers administrative snap-in, in

the navigation pane, expand Contoso.com and then click the Users

container.

c. In the Results pane, right-click the CSAdministrator group and then

click Properties.

d. On the CSAdministrator Properties page, click the Members tab and

then click Add.

e. On the Select Users, Contacts, Computers, Service Accounts, or Groups

page, in the Enter the object names to select window, type

Administrator and then click OK.

f. Back on the CSAdministrator Properties page, click OK, and then close

Active Directory Users and Computers.

2. Create a DNS record for the different components.



You will now create the necessary DNS records, which will include the pool

name and the simple URLs. Normally, you would also need a Service Location

(SRV) record, but since you already have

Office Communications Server 2007 R2, it already exists.

a. On DC01, click Start > Administrative Tools > DNS.

b. In the DNS Manager, expand DC01, expand Forward Lookup Zones,

and then click Contoso.com.

c. Right-click Contoso.com and then click New Host (A or AAAA).

d. In the New Host window, in the Name field, type lspool01

e. In the IP Address field, type 10.0.0.30 and then click Add Host.

f. At the DNS prompt, click OK.

g. In the New Host window, in the Name field, type dialin

h. In the IP Address field, type 10.0.0.30 and then click Add Host.

i. At the DNS prompt, click OK.

j. In the New Host window, in the Name field, type meet

k. In the IP Address field, type 10.0.0.30 and then click Add Host.

l. At the DNS prompt, click OK.

m. In the New Host window, in the Name field, type admin

n. In the IP Address field, type 10.0.0.30 and then click Add Host.

o. At the DNS prompt, click OK and then click Done.

p. Close DNS Manager.

3. Publish the topology.

Each time that you use Topology Builder to build your topology, you must publish

the topology to a database in the Central Management Store (CMS) so the data can

be used for deployment of Lync Server 2010 servers. You will see the list of things

that will be performed when running this for the first time.

a. On LS-FE, switch to the Topology Builder.

b. Right-click Lync Server 2010 (RC) and then click Publish Topology.

It will take a moment for the Publish Topology wizard to appear.

c. On the Publish the topology page, review the actions that will be performed


d. On the Create databases page, verify that sql01.contoso.com is selected and

then click Next.



e. On the Select Central Management Server page, verify that the front end pool

drop-down displays lspool01.contoso.com Redmond and then click Next.

Wait as the topology is published. This will take about two minutes.

f. On the Publishing wizard complete page, verify that all steps show as

Success.

g. Under Next steps click the link to open the to-do list.

h. Review the NextSteps.txt file that opens and the instructions to run local

setup on each server in the list and then close Notepad.

i. Back on the Publishing wizard complete page, click Finish.

j. Close the Lync Server 2010 Topology Builder.



Exercise 4: Deploying Lync Server 2010

In this exercise, you will deploy Lync Server 2010. You will use the Deployment Wizard

to walk through the steps, which include installing the Local Configuration Store,

setting up the Lync Server 2010 components, requesting and assigning the necessary

certificates, and then starting the services. Finally, you will initialize the

Lync Server 2010 administrator roles.

Tasks

1. Start the Lync Server 2010 Deployment Wizard and install the Local

Configuration Store.

The procedure for installing server roles is the same for all roles. In this task, you

will see the first step, which will install the Local Configuration Store from the

CMS.

a. On LS-FE, click Start and then click Windows Explorer.

b. Navigate to C:\LabFiles\LS2010\Setup\amd64 and then double-click

Setup.exe.

Wait a few moments for setup to start.

c. On the Lync Server 2010 (RC) Deployment Wizard page, click Install or

Update Lync Server System.

d. On the Lync Server 2010 page, next to Step 1: Install Local

Configuration Store, click Run.

e. On the Local Server Configuration page, verify that Retrieve directly

from the Central Management Store is selected and then click Next.

This step would usually take several minutes, but in this environment will

only take about two minutes as the local store has been pre-staged in

order to save time.

f. On the Executing Commands page, when the Task Status shows as

Completed, click Finish.

2. Set up Lync Server 2010 components.

The second step will install the server components for the roles to be installed.

a. On the Lync Server 2010 page, next to Step 2: Setup or Remove Lync

Server Components, click Run.

b. On the Setup Lync Server components page, click Next.

This will take about 5-7 minutes.



c. On the Executing Commands page, when the Task Status shows as


3. Request and assign a certificate.

You will now request the certificate for the Default usage.

a. On the Lync Server 2010 page, next to Step 3: Request, Install or Assign

Certificates, click Run.

b. In the Certificate Wizard window, click Request.

c. On the Certificate Request page, click Next.

d. On the Delayed or Immediate Requests page, verify that Send the

request immediately to an online certificate authority is selected


e. On the Choose a Certificate Authority (CA) page, verify that

DC01.contoso.com\ContosoCA is listed and then click Next.

f. On the Certificate Authority Account page, leave the box clear and then

click Next.

g. On the Specify Alternate Certificate Template page, leave the box clear


h. On the Name and Security Settings page, in the Friendly Name field,

type Default Cert and click Next.

i. On the Organization Information page, in the Organization field, type

Contoso

j. In the Organizational Unit field, type IT and then click Next.

k. On the Geographical Information page, in the Country/Region drop-

down list, select United States.

l. In the State/Province field, type Washington

m. In the City/Locality field, type Redmond and then click Next.

n. On the Subject Name/Subject Alternate Names page, review the Subject

Name and Subject Alternate Names automatically populated and then

click Next.

o. On the SIP Domain setting on Subject Alternate Names (SANs) page,

select the Contoso.com check box and then click Next.

p. On the Configure Additional Subject Alternate Names page, leave the

fields blank and then click Next.

q. On the Certificate Request Summary page, click Next.



r. On the Executing Commands page, when the Task Status shows as

Completed, click Next.

s. 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.

t. On the Certificate Assignment page, click Next.

u. On the Certificate Assignment Summary page, click Next.

v. On the Executing Commands page, when the Task Status shows as


w. Back on the Certificate Wizard, click the down arrow next to Default

Certificate to expand the Certificate Type.

x. Verify that Server Default, Web Services Internal, and Web Services

External are selected and then click Close.

4. Start the services.

Now that installation is complete, you will start the services.

a. On the Lync Server 2010 page, next to Step 4: Start Services, click Run.

b. On the Start Services page, click Next.

Wait a few minutes for the services to start.

c. On the Executing Commands page, when the Task Status shows as


d. Next to Service Status (Optional), click Run.

e. In the Services console that opens, verify that all of the Lync Server 2010

services have started and then close the Services console.

f. Close the Lync Server 2010 (RC) Deployment Wizard and then close

Windows Explorer.



Exercise 5: Validating the Deployment Using the

Lync Server 2010 Control Panel

During this exercise, you will validate your deployment by using the Lync Server 2010

Control Panel and view some of the features and information displayed in the Topology

Viewer.

Tasks

1. Start and log in to the Lync Server 2010 Control Panel.

The Web-based Lync Server 2010 Control Panel replaces the Microsoft

Management Console (MMC) interface from previous versions for graphical user

interface (GUI)–based management of Lync Server 2010.

a. On LS-FE, click Start > All Programs > Microsoft Lync Server 2010

(RC) > Lync Server Control Panel.

b. At the Connecting to lspool01.contoso.com prompt, in the User

name field, type Contoso\Administrator

c. In the Password field, type Password1 and then click OK.

2. Explore the Microsoft Lync Server 2010 Control Panel Topology Viewer.

You can use the Topology section of the Lync Server 2010 Control Panel to see a

list of computers and services. You can also view the details and the status of

each computer and service. You can sort the list by computer, pool, or site.

a. On LS-FE, in the Lync Server 2010 Control Panel, in the navigation pane,

click Topology.

b. In the results pane, notice the four entries listed under Computer.

c. Click 10.1.10.10 and then click Properties.

d. On the View Computer Detail page, under Service, notice in the details

that this computer is listed as the PstnGateway.

You defined this earlier in the lab, when you created the topology using

the Lync Server 2010 Topology Builder.

e. Click Close to return to the Topology Viewer main page.

f. Under Computers, double-click sql01.contoso.com.

g. On the View Computer Detail page, under Service, notice the six Stores

listed:

ApplicationDatabase

ArchivingDatabase



CentralManagementDatabase

FileStore

MonitoringDatabase

UserDatabase

h. Click FileStore and then click Properties.

i. On the View Service Detail - FileStore page, notice Dependent services

and then click Close twice.

j. Under Computers, click LS-FE.contoso.com and then click

Properties.

k. On the View Computer Detail – LS-FE.contoso.com page, notice the

various services listed. You are able to stop and start these services from

here by using the Action menu.

l. Click ConferencingServer and then click Properties.

m. On the View Service Detail – ConferencingServer page, view the

information provided, such as the various ports and Dependent Services,

and then click Close twice.

n. Back on the Topology Viewer page, click the Server Application tab at

the top of the page.

o. On the Server Application page, notice the various applications and then

click ClientVersionFilter.

p. Click Action and notice that you can Enable or Disable the application

or Select or Deselect the application as Critical.

q. Click the Simple URL tab, and notice the URLs we saw and configured

in the Topology builder.

r. Close the Lync Server 2010 Control Panel and any other open windows.



Exercise 6 (Optional): Exploring the Topology Builder to

Define a Standard Edition Front End Topology

In this exercise, you will run through the steps to define a Standard Edition Pool using the

Lync Server 2010 Topology Builder. This includes a brief look at configuring External Access

with an Edge server. You will not save your settings when finished. This is an optional

exercise and is used to show the process for defining a Standard Edition Front End Pool

topology.

Tasks

1. Define a Standard Edition Front End topology.

In this procedure, you will briefly review the steps for defining a Standard

Edition topology, but you will not save the settings.

a. On LS-FE, open the Lync Server Topology Builder.

b. On the Topology Builder page, verify that Download Topology from

existing deployment is selected and then click OK.

c. In the Save New Topology As window, save the file as

TestSETopology.tbxml and save it on the desktop.

d. In the Topology Builder navigation pane, expand the Redmond Site,

right-click Standard Edition Front End Servers, and then click New

Front End Pool.

e. On the Define the New Front End pool page, click Next.

f. On the Define the Front End pool FQDN page, in the FQDN field, type

SE-Test.Contoso.com

This must be the FQDN of the Standard Edition server you would

deploy.

g. Verify that Standard Edition Server is selected and then click Next.

h. On the Select Features page, select the Conferencing, which includes

audio, video and application sharing, Dial-in (PSTN) Conferencing

and Enterprise Voice check boxes, and then click Next.

i. On the Select collocated server roles page, notice that Collocate A/V

Conferencing service is selected and grayed out.

j. Verify that the Collocate Mediation Server check box is selected and

then click Next.

k. On the Associate server roles with this Front End pool page, clear all of

the check boxes and then click Next.



l. On the Define the SQL store page, notice that it is grayed out, and then

click Next.

m. On the Define the file share page, leave the defaults and then click Next.

n. On the Specify the Web Services URL page, verify that the Override

internal Web Service pool FQDN check box is not selected.

o. In the External Base URL field, type SE-Test-Ext.contoso.com and

then click Next.

p. On the Specify PSTN gateways page, click Finish.

2. Define an Edge pool.

a. On LS-FE, in the Topology Builder, expand Standard Edition Front

End Servers, right-click SE-Test.contoso.com, and then click Edit

Properties.

b. On the Edit Properties page, under Associations, select the Associate

Edge pool check box and then click New.

c. On the Define the New Edge Pool page, click Next.

d. On the Define the Edge pool FQDN page, in the Pool FQDN field, type

ls-edge.contoso.com

e. Select Single computer pool, and then click Next.

f. On the Select features page, read the list of features, select only Enable

federation (port 5061) and then click Next.

g. On the External FQDNs page, in the SIP Access field, type

sip.contoso.com and leave the port as 443.

h. In the Web Conferencing field, type webconf.contoso.com and leave

the port as 443.

i. In the Audio/Video field, type av.contoso.com and leave the port as

443, and then click Next.

j. On the Define the internal IP address page, in the Internal IP address

field, type 10.0.0.99 and then click Next.

k. On the Define the external IP address page, in the SIP Access field, type

172.16.0.101

l. In the Web Conferencing field, type 172.16.0.102

m. In the Audio/Video field, type 172.16.0.103 and then click Next.

n. On the Define the next hop page, verify that SE-Test.contoso.com

Redmond is selected in the drop-down list and then click Finish.



o. On the Edit Properties page, click OK.

p. Close the Topology Builder.

3. Shut down all running VMs.

You will no longer need the current state of these VMs. You will apply a

snapshot to these VMs with more roles deployed for the remaining labs.

Documents

Lab 01 - Deploying Microsoft Lync Server 2010