10533ad-enu-labmanual

7/27/2019 10533AD-ENU-LabManual

1/364

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

10533A

Lab Instructions and Lab Answer Key:Deploying, Configuring, and AdministeringMicrosoft Lync Server 2010


2/364

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

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people,

places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain

name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright

laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be

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

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

Corporation.

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

matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this

document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

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

representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the

products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of

Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of

Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any

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

any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply

endorsement of Microsoft of the site or the products contained therein.

2011 Microsoft Corporation. All rights reserved.

Microsoft, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/orother countries.

All other trademarks are property of their respective owners.

Product Number: 10533A

Part Number : X17-52341

Released: 5/2011


3/364

Lab Instructions: Deploying Microsoft Lync Server 2010 1

Module 2

Lab Instructions: Deploying Microsoft Lync Server 2010

Contents:Exercise 1: Preparing for Lync Server 2010 4

Exercise 2: Configuring a Lync Server 2010 Topology 5

Exercise 3: Publishing the Topology 7

Exercise 4: Configuring Domain Name Server (DNS) 8

Exercise 5: Deploying the Front End Server Role 9


4/364

2 Lab Instructions: Deploying Microsoft Lync Server 2010

Lab: Preparing the Environment and Deploying a LyncServer 2010 Pool

Lab Scenario

You are the Network Administrator for Fabrikam, Inc., and have been tasked with deploying

Lync Server 2010. You will prepare your Active Directory for Lync Server 2010, configure a topology by

using the Topology Builder, publish it, and then deploy one Enterprise Edition Front End server.

Start the virtual machinesFor Labs 2, 3 and 4, each student should have their own set of virtual machines and will perform all of the

steps by themselves. The set of virtual machines include:

10533A-MIA-DC1.1 10533A-MIA-SQL1.1 10533A-MIA-LS1.1 10533A-MIA-CL1.1Use the Hyper-V Manager to start and connect to the MIA-DC1 virtual machine and wait for it to

completely startup. . Start and connect to the rest of the virtual machines (10533A-MIA-SQL1.1,

10533A-MIA-LS1.1, and 10533A-MIA-Cl1.1) before beginning labs. The virtual machines are configured

to automatically log on as Fabrikam\Administrator with the password, Pa$$w0rd, except for the followingvirtual machine:

MIA-CL1 as Fabrikam\Andreas, with the password, Pa$$w0rdTo 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, right-click 10533A-MIA-DC1.1 and click Start.


5/364


3. Right-click 10533A-MIA-DC1.1 and click Connect.4. In the Virtual Machine Connection window, wait until the virtual machine has booted up completely

before continuing.

5. In the Virtual Machines list, right-click 10533A-MIA-SQL1.1 and click Start.6. Right-click 10533A-MIA-SQL1.1 and click Connect.7. In the Virtual Machines list, right-click 10533A-MIA-LS1.1 and click Start.8. Right-click 10533A-MIA-LS1.1 and click Connect.9. In the Virtual Machines list, right-click 10533A-MIA-CL1.1 and click Start.10. Right-click 10533A-MIA-CL1.1 and click Connect.11. When 10533A-MIA-CL1.1 has booted up completely, close the Virtual Machine Connection window.12. On the host, click Start, click All Programs, click Accessories, and then click Remote Desktop

Connection.

13. In the Remote Desktop Connection window, click Options.14.

Click the Local Resources tab, and then under Remoteaudio, click Settings.

15. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.16. Under Remote audiorecording, click Record from thiscomputer, and then click OK.17. Click the General tab.18. Under Logon settings, in the Computer box, type mia-cl1.fabrikam.com.19. In the User name box, type Fabrikam\Andreas, and then click Connect.20. On the Remote Desktop Connection window, select the Dont ask me again for connections to this

computer check box, and then click Connect.

21. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.22. On the Remote Desktop Connection window, select the Dont ask me again for connections to thiscomputer 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 2010, 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.3. If not, right-click the service and click Start.Important: All connections to MIA-CL1 will require using a Remote Desktop Connection with remote

audio playback and remote audio recording enabled, unless otherwise specifically instructed.

Note: If the virtual machines are reporting that they need to be activated, run slmgr.vbs rearm from acommand prompt and then reboot the server.


6/364


Exercise 1: Preparing for Lync Server 2010

Scenario

In the first exercise, you will prepare Active Directory for Lync Server 2010 and add the Administrator in

the CSAdministrator group.

The main tasks for this exercise are as follows:

1. Prepare Active Directory for Lync Server 2010.2. Add an administrator to the CSAdministrator group.

Task 1: Prepare Active Directory for Lync Server 2010.1. On MIA-LS1, launch the Lync Server 2010 Deployment Wizard.2. Using the Lync Server 2010 Deployment wizard, perform the steps to Prepare Active Directory.3. Close the Deployment Wizard.

Task 2: Add an administrator to the CSAdministrator Group.1. On MIA-DC1, launch Active Directory Users and Computers.2. Add Fabrikam\Administrator to the CSAdministrator group.3. Log off of MIA-LS1 and then log back on as Fabrikam\Administrator with the password of

Pa$$w0rd

Results: After this exercise, you should have prepared Active Directory for an installation ofLync Server 2010.


7/364


8/364


Wizard step Entry

File Share: Type fileshare

Specify the Web Services Leave default

Task 2: Configure the Administrative Access URL.1. On MIA-LS1, in the Topology Builder, configure the Administrative Access URL to be

https://admin.fabrikam.com.

Results: After this exercise, you should have created and edited a publishable topology.


9/364


Exercise 3: Publishing the Topology

Scenario

In this exercise, you will publish the topology and understand the changes made during this process, such

as creating the CMS database, setting the configuration store location, and creating the necessary

databases.The main task for this exercise is to publish your topology.

Task 1: Publish the topology.1. On MIA-LS1, use the Topology Builder to publish the topology.2. Verify that MIA-SQL1.Fabrikam.com is selected to create the databases.3. Select Pool.fabrikam.com for the Central Management Service.4. Verify that the topology publishes successfully.5. Read the to-do list.'

Results: After this exercise, you should have published the topology.


10/364


Exercise 4: Configuring Domain Name Server (DNS)

Scenario

In this exercise, you will use the DNS MMC to create appropriate A and SRV records on MIA-DC1 that

are required for automatic client logon.

The main task for this exercise is to create the necessary DNS records for Lync Server 2010.

Task 1: Create the necessary DNS records for Lync Server 2010.1. On MIA-DC1, open DNS Manager.2. In the Fabrikam.com Forward Lookup zone, create the following DNS records:

'A' Pool 10.0.10.12 'A' Dialin 10.0.10.12 'A' Meet 10.0.10.12 'A' Admin 10.0.10.12 'SRV' _sip._tls.fabrikam.com 5061 pool.fabrikam.com 'SRV' _sipinternaltls._tcp.fabrikam.com 5061 pool.fabrikam.com


11/364


Exercise 5: Deploying the Front End Server Role

Scenario

In this exercise, you will walk through the four steps in the deployment wizard to complete the setup of a

Lync Server 2010 Front End server. You will install a Local Configuration Store, set up components, request

and configure certificates, and then start the Lync Services.The main tasks for this exercise are as follows:

1. Install the Local Configuration Store.2. Set up components.3. Request and assign certificates.4. Start Lync Server Services.

Task 1: Install the Local Configuration Store.1. On MIA-LS1, using the Lync Server 2010 Deployment Wizard, perform the steps to install or update

Lync Server System and install the Local Configuration Store.

2. Verify that the Local Configuration Store will retrieve directly from the CMS. Task 2: Set up components.

1. On MIA-LS1, using the Lync Server 2010 Deployment Wizard, perform the steps to set up or removeLync Server components.

Task 3: Request and assign certificates.1. On MIA-LS1, using the Lync Server 2010 Deployment Wizard, perform the steps to request, install, or

assign certificates.

Use the following information to request and assign the necessary certificates.

Wizard step Entry

Certification Authority MIA-DC1.Fabrikam.com\FabrikamCA

Name and Security Friendly Name: Type MIA-LS1 Lync Server Certificate

Bit Length: Select 2048

Organization Information Organization: Type Fabrikam Corporation

Organizational Unit: Type IT

Geographical Information Country/Region: Select United States

State/Province: Type Florida

City/Locality: Type Miami

SIP Domain setting on SubjectAlternate Name (SANs)

Select Fabrikam.com

Certificate Wizard Expand the Certificate Type:

Server Default Web Services Internal Web Services ExternalVerify all show as Assigned.


12/364


Task 4: Start Lync Server Services.1. On MIA-LS1, using the Lync Server 2010 Deployment Wizard, perform the steps to start the

Lync Server 2010 services.

Results: After this exercise, you should have a configured Lync Server 2010 deployment.


13/364

Lab Instructions: Configuring Users and Rights in Microsoft Lync Server 2010 1

Module 3

Lab Instructions: Configuring Users and Rights in MicrosoftLync Server 2010

Contents:Exercise 1: Using the Lync Server Control Panel 4

Exercise 2: Using the Lync Server Management Shell 6

Exercise 3: Configuring Role-Based Access Control 7


14/364

2 Lab Instructions: Configuring Users and Rights in Microsoft Lync Server 2010

Lab: Configuring Users and Rights in Lync Server 2010

Lab Scenario

You have successfully deployed Lync Server 2010 at Fabrikam, Inc.You will now provision users and

delegate administrative rights.

Start the virtual machinesThis lab requires the virtual machines from the previous lab and depends on Lab 2 being completed.The

virtual machines are configured to automatically logon as Fabrikam\Administrator with the password,Pa$$w0rd, except for the following virtual machine:

MIA-CL1 as Fabrikam\Andreas, with the password, Pa$$w0rdTo 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 10533A-MIA-DC1.1 is not started:

a. Right-click 10533A-MIA-DC1.1 and click Start.b. Right-click 10533A-MIA-DC1.1 and click Connect.

3. In the Virtual Machine Connection window, wait until the virtual machine has booted up completelybefore continuing.

4. In the Virtual Machines list,if the virtual machine 10533A-MIA-SQL1.1 is not started:a. Right-click 10533A-MIA-SQL1.1 and click Start.b. Right-click 10533A-MIA-SQL1.1 and click Connect.

5. In the Virtual Machines list, if the virtual machine 10533A-MIA-LS1.1 is not started:a. Right-click 10533A-MIA-LS1.1 and click Start.


15/364


b. Right-click 10533A-MIA-LS1.1 and click Connect.6. In the Virtual Machines list, if the virtual machine 10533A-MIA-CL1.1 is not started:

a. Right-click 10533A-MIA-CL1.1 and click Start.b. Right-click 10533A-MIA-CL1.1and click Connect.

7. When 10533A-MIA-CL1.1 has booted up completely, close the Virtual Machine Connection window.8. On the host, click Start, click All Programs, click Accessories, and then click Remote Desktop

Connection.

9. In the Remote Desktop Connection window, click Options.10. Click the Local Resources tab, and then under Remoteaudio, click Settings.11. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.12. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.13. Click the General tab.14. Under Logon settings, in the Computerbox, type mia-cl1.fabrikam.com.15. In the User namebox, type Fabrikam\Andreas, and then click Connect.16. On the Remote Desktop Connection window,select the Dont ask me again for connections to this


17. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.18. On the Remote Desktop Connection window, select the Dont 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 theMicrosoft Exchange, Lync Server 2010, and Microsoft SQL Server services. To do so, complete thefollowing steps:

1. On each virtual machine, click Start, click Administrative Tools, and then click Services.2. In the Services console, verify that all services that are set to Automatic start have started.3. If not, right-click the service and click Start.

Important: All connections to MIA-CL1 will require using a Remote Desktop Connection with remote

audio playback and remote audio recording enabled, unless otherwise specifically instructed.


16/364


Exercise 1: Using the Lync Server Control Panel

Scenario

In this exercise, you will use the Lync Server Control Panel to provision and administer users for

Lync Server 2010.

The main tasks for this exercise areas follows:1. Enable users.2. Validate the configuration.

IMPORTANT: On all virtual machines, verify that all of the services set to start automatically havestarted. Most notably, check the Exchange, SQL Server, and Lync Server 2010 services. To do so, clickStart, click Administrative Tools and then click Services. In the Services console, verify all services thatare set to Automatic start have started. If not, right-click the service and click Start.

Task 1: Enable users.1. On MIA-LS1, launch Internet Explorer.

a. To enable auto logon, add *.fabrikam.com to Local Intranet Sites inMicrosoft Internet Explorer Security.

2. On MIA-LS1, start the Lync Server Control Panel by running https://admin.fabrikam.comor opening iton the Start menu.

3. Enable the following users: Andreas Herbinger Anna Lidman Conor Cunningham EbruErsan Patricia Doyle Paul West

4. Use the following settings: Pool: Pool.fabrikam.com Use the format: [email protected] Telephony: PC-to-PC only Remaining settings: 'Default'

Task 2: Validate the configuration.1. On MIA-LS1, use the Lync Server Management Shell to update the Address book and the User

Database.

2. On the host, import the Fabrikam CA certificate as a Trusted Root Certification Authority from \\MIA-DC1\Certenroll.

3. Install Lync 2010 from \\MIA-LS1.Fabrikam.com\C$\LabFiles\4. Validate the ability to logon to Lync Server 2010 and have conversations.


17/364


a. On the host, sign in to Lync as Conor. [email protected], Pa$$w0rd

b. On MIA-CL1 sign in as Andreas by using a Remote Desktop Connection with remote audioplayback and remote audio recording enabled.

[email protected], Pa$$w0rdc. Launch Lync 2010.d. Add each other as contacts and have an instant messaging (IM) conversation between Andreas

and Conor.

NOTE: You may have to wait a moment for Address book synchronization or enter the full SIP URI,such as [email protected].

e. Add Marcel as a contact for Andreas and Conor.Results:After completing this exercise, you should have enabled existing Active Directory users byusing the Lync Server Control Panel. Then, you should have installed Lync Server 2010 on the host

and verified Lync Server 2010 connectivity and functionality.


18/364


Exercise 2: Using the Lync Server Management Shell

Scenario

In this exercise, you will use the Lync Server Management Shell to provision users for Lync Server 2010

based on their Active Directory group membership.

The main tasks for this exercise are as follows:1. Validate group membership.2. Enable users for Lync Server 2010.3. Validate the configuration.

Task 1: Validate group membership.1. On MIA-DC1, launch Active Directory Users and Computers.2. Browse to the Executives OU.3. Review the Executives group membership.

Task 2: Enable users for Lync Server 2010.1. On MIA-LS1, use the Lync Server Management Shell to enable all users in the Executives OU for LyncServer and assign them to the pool.fabrikam.com pool.

Task 3: Validate the configuration.1. Validate the ability to logon to Lync 2010.

a. On MIA-CL1, sign in as Marcelby using a Remote Desktop Connection as described at thebeginning of this lab.

Fabrikam\marcel, Pa$$w0rdb. Launch Lync 2010 and notice that Marcel can log on.c.

Have a conversation with Conor.

Results: After 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.


19/364


Exercise 3: Configuring Role-Based Access Control

Scenario

In this exercise, you will grant administrative rights to users and verify that those rights have been applied

in accordance with RBAC.

The main tasks for this exercise are as follows:1. Validate user rights.2. Grant rights to specific users.3. Validate that RBAC has been applied.

Task 1: Validate user rights.1. On MIA-CL1, start Internet Explorer.2. Navigate to https://admin.fabrikam.com3. Log on as Andreas.

Fabrikam\Andreas, Pa$$w0rd4. Validate that access is denied.

Task 2: Grant rights to specific users.1. On MIA-DC1, add Andreas to the CSAdministratorgroup.2. On MIA-DC1, add Conor Cunningham to the CSHelpDeskgroup.

Task 3: Validate that RBAC has been applied.1. Validate that access now is granted and that the user has the assigned rights in the

Lync Server Control Panel.

2. On MIA-CL1, start Internet Explorer.3. Navigate to https://admin.fabrikam.com4. Log on as Andreas.


20/364


21/364

Lab Instructions: Client and Device Deployment and Management 1

Module 4

Lab Instructions: Client and Device Deployment andManagement

Contents:Exercise 1: Creating and Assigning Client Policies 4

Exercise 2: Creating and Assigning Device Policies 6

Exercise 3: Configuring a Device Update 8


22/364

2 Lab Instructions: Client and Device Deployment and Management

Lab: Client and Device Management

`

Scenario

With users configured for Lync Server 2010, you have been tasked with deploying devices and clients. The

management and security team in Fabrikam Inc. have developed client and device requirements that

match company policies.

You will create and assign client and device policies at the global, site, and user levels by using the

available Lync Server 2010 tools to enforce the defined company policies with granular control.

Start the virtual machinesThis lab requires the virtual machines running from the previous lab and depends on the completion of

Labs2 and 3.The virtual machines are configured to automatically logon as Fabrikam\Administrator with

the password, Pa$$w0rd, except for the following virtual machine:

MIA-CL1 as Fabrikam\Andreas, with the password, Pa$$w0rd

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 10533A-MIA-DC1.1 is not started:

a. Right-click 10533A-MIA-DC1.1 and click Start.b. Right-click 10533A-MIA-DC1.1 and click Connect.

3. In the Virtual Machine Connection window, wait until the virtual machine has booted up completelybefore continuing.

4. In the Virtual Machines list,if the virtual machine 10533A-MIA-SQL1.1 is not started:a. Right-click 10533A-MIA-SQL1.1 and click Start.


23/364


b. Right-click 10533A-MIA-SQL1.1 and click Connect.5. In the Virtual Machines list, if the virtual machine 10533A-MIA-LS1.1 is not started:

a. Right-click 10533A-MIA-LS1.1 and click Start.b. Right-click 10533A-MIA-LS1.1 and click Connect.

6. In the Virtual Machines list, if the virtual machine 10533A-MIA-CL1.1 is not started:a. Right-click 10533A-MIA-CL1.1 and click Start.b. Right-click 10533A-MIA-CL1.1 and click Connect.

7. When 10533A-MIA-CL1.1 has booted up completely, close the Virtual Machine Connection window.8. On the host, click Start, click All Programs, click Accessories, and then click Remote Desktop

Connection.

9. In the Remote Desktop Connection window, click Options.10. Click the Local Resources tab, and then under Remoteaudio, click Settings.11. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.12. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.13. Click the General tab.14. Under Logon settings, in the Computerbox, type mia-cl1.fabrikam.com.15. In the User namebox, type Fabrikam\Andreas, and then click Connect.16. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


17. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.18. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


Verify that all services set to Automatic have started on all virtual machines. Most notably, check theMicrosoft Exchange, Lync Server 2010, and Microsoft SQL Server services. To do so, complete thefollowing 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.3. If not, right-click the service and click Start.Important: All connections to MIA-CL1 will require using a Remote Desktop Connection with remoteaudio playback and remote audio recording enabled, unless otherwise specifically instructed.

Tip: The longer commands in this lab are already typed up in PS1 files located in C:\LabFiles on MIA-LS1.Not all commands are included.


24/364


Exercise 1: Creating and Assigning Client Policies

Scenario

In this exercise, you will use Windows PowerShell to create client policies. You will then use the

Lync Server Control Panel to assign these policies to selected users.

The main tasks for this exercise are as follows:1. Create client policies by using a PowerShell script.2. Verify client policy application to users.

Important: On all virtual machines, verify whether all of the services set to start automatically havestarted. Most notably, check the Exchange, SQL Server, and Lync Server 2010 services. To do so, clickStart, click Administrative Tools, and then click Services. In the Services console, verify that allservices set to Automatic start have started. If not, right-click the service and click Start.

Task 1: Create client policies by using a PowerShell script.1. Sign out of Lync on the host and MIA-CL1.2. On MIA-LS1, use the Lync Server Management Shell to create a Global client policy with the following

features.

Step Value

Scope Global

AttendantSafeTransfer True

BlockConversationFromFederatedContacts True

DisableEmoticons True

EnableHotDesking True

HotDeskingTimeout 00:00:30

IMWarning

Warning: All communicationswithin Fabrikam may be loggedand viewed at any time and for anyreason. Use of the Fabrikam InstantMessaging service is a privilege.Abuse of the system may result inloss of said privilege.

3.

Use the Lync Server Management Shell to create and edit a Miami Site client policy with the followingfeatures.

Step Value

Scope Miami

Description Miami Default Client Policy

EnableClientMusicOnHold True


25/364


Step Value

EnableFullScreenVideo True

EnableVOIPCallDefault True

EnableExchangeContactSync True

IMWarning

Warning: All communications within Fabrikam maybe logged and viewed at any time and for anyreason. Use of the Fabrikam Instant Messagingservice is a privilege. Abuse of the system may resultin loss of said privilege.

4. Use the Lync Server Management Shell to create and edit an Executive User client policy with thefollowing features.

Step Value

Scope Tag:Executive

Description Fabrikam Executive Client Policy

EnableAppearOffline True

EnableClientMusicOnHold True

EnableFullScreenVideo True

EnableVOIPCallDefault True

EnableExchangeContactSync True

5. Use the Lync Server Management Shell to verify that the policies were created, and then review thesettings.

Note: This command is not included in the ps1 file.

6. Use the Lync Server Management Shell to apply the Executive User policy to the members of theExecutives OU.

Task 2: Verify client policy application to users.1. In the Lync Server Control Panel, in Users, verify that the Executives client policy was applied to

Marcel.

2. Log onto Lync 2010 as Marcel on MIA-CL1, and as Conor on the host.3. Verify client policy application to Marcel (Executive) and Conor (Site).Results: After completing this exercise, you should be able to describe how to create client policies inLync 2010, how to apply them, and then see the effects of the client policies.


26/364


Exercise 2: Creating and Assigning Device Policies

Scenario

In this exercise, you will use the Lync Server Management Shell to edit theglobal and create site device

polices. The device policies include PIN and logging requirements, and application of the policies will be

simulated. You will also configure the settings for a common area phone.


1. Create and edit device policies by using a PowerShell script.2. Verify device policy creation.

Task 1: Create and edit device policies by using a PowerShell script.1. On MIA-LS1, use the Lync Server Management Shell to create and edit a Miami Site Device Update

Configuration with the following features.

Step Value

Scope Site: Miami

LogCleanUpInterval 7.00:00:00

2. Use the Lync Server Management Shell to edit the Global Phone Configuration with the followingfeatures.

Step Value

Scope Global

EnforcePhoneLock True

CalendarPollInterval 00:30:00

PhoneLockTimeout 00:05:00

MinPhonePinLength 8

LoggingLevel Off

3. Use the Lync Server Management Shell to create and edit a Miami Site Phone Configuration with thefollowing features.

Step Value

Scope Site:Miami

EnforcePhoneLock True

CalendarPollInterval 00:03:00

PhoneLockTimeout 01:00:00

MinPhonePinLength 8

LoggingLevel Low


27/364


4. Use the Lync Server Management Shell to create and configure a Common Area Phone with thefollowing features.

Step Value

LineUri Tel:+14255551000

SipAddress Sip:[email protected]

Description Lobby Phone in Miami

DisplayName Miami Lobby Phone

DisplayNumber (425) 555-1000

OU cn=Users,dc=Fabrikam,dc=com

RegistrarPool Pool.fabrikam.com

Task 2: Verify device policy creation.1. In the Lync Server Control Panel, in Clients, verify the creation of device configuration policies and

the editing done to the Global device configuration policies and Device Log configuration policies.

2. In the Lync Server Management Shell, verify the creation of the common area phone and review thesettings.

Note: This command is not included in the ps1 file.

Results: After completing this exercise, you should have created device policies and edited the Global

policies by using a PowerShell script. This script also configured a new common area phone.


28/364


Exercise 3: Configuring a Device Update

Scenario

In this exercise, you will use the Lync Server Management Shell to import a Device Update .cab file. After

the file has been imported, you will create a Test Device policy prior to approving the update.

The main tasks for this exercise are as follows:1. Import a Device Update .cab file.2. Create a Test Device policy.3. Approve the device updates.

Task 1: Import a Device Update .cab file.1. Execute UCUpdates.exe from C:\LabFiles and extract the file to C:\.2. Use the Lync Server Management Shell to import the new Device Update files.3. Use the Lync Server Control Panel to verify that the .cab file was successfully loaded.

Task 2: Create a Test Device policy.1. Use the Lync Server Control Panel to create a new Site test device and test the uploaded .cab file.2. Use the following information to create the Site test device.

Wizard step Value

Site Miami

Device Name Test Tanjay

Identifier Type Serial Number

Unique identifier 1111111111 (this is ten ones)

Task 3: Approve the device updates.1. Use the Lync Server Control Panel to approve all of the device updates.Results: After completing this exercise, you should have learned how to install a new device update file,how to load it into Lync Server, how to test it on a specific device, and how to approve it for all devices.

Important: After this lab, we recommend that you take a snapshot of all running virtual machinesbefore starting the next lab. To do so, in Hyper-V Manager, highlight all running virtual machines, right-click, and then click Snapshot.


29/364

Lab Instructions: External User Access 1

Module 5

Lab Instructions: External User Access

Contents:Exercise 1: Configuring the Topology for External Access 8

Exercise 2: Deploying Edge Server and Configuring Remote Access 10

Exercise 3: Testing and Verifying External User Access 13


30/364

2 Lab Instructions: External User Access

Lab: Deploying External User Access

Lab Scenario:You are the Network Administrator for Fabrikam, Inc and have been tasked with installing the

Lync Server 2010 Edge server into your existing infrastructure to provide remote access to external users

for; web conferencing, A/V, audio conferencing, and presence. Your Edge deployment must also provide

access to public IM services for your internal users.

In this lab, you will:

1. Reconfigure the current Lync Server 2010 Lab topology to include an Edge server and relatedcomponents using the Topology Builder.

2. Export the Lync Server configuration to the Edge server.3. Deploy the Edge server role.4. Configure the External Access policy and Access Edge configuration.5. Test and Verify External User Access to the services offered.

Important: We recommended that the steps in this and every lab be split between the two studentsin your pod. It is left up to the students to determine when to share tasks in order for both studentsto 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 others workand possibly lose data.


31/364


Virtual Lab Environment topology diagram:


32/364


Start the virtual machinesFor Labs 5 through 15, a new set of virtual machines will be used and they are split between the two

Hyper-V hosts in the pod. They include:

10533A-MIA-DC1.2 10533A-MIA-SQL1.2 10533A-MIA-ED1.2 10533A-ROM-LS2.2 10533A-ROM-CL3.2 10533A-INT-CL4.2 10533A-MIA-LS1.2 10533A-MIA-AM1.2 10533A-RED-SBS1.2 10533A-MIA-CL1.2 10533A-RED-CL2.2 10533A-MIA-RAS1.2Before you start any virtual machines, verify that the set 1 virtual machines are completely shut down and

off.

For this lab, use the Hyper-V Manager to start and connect to the 10533A-MIA-DC1.2 virtual machine

on Host1 and wait for it to completely start up. Next, start 10533A-MIA-RAS1.2 on the Host2 and wait

for it to completely start up. When both of these machines have completely started, start the rest of the

set 2 virtual machines on both Host1 and Host2.

Host1:

10533A-MIA-SQL1.2

10533A-MIA-ED1.2 10533A-ROM-LS2.2 10533A-ROM-CL3.2 10533A-INT-CL4.2Host2:

10533A-MIA-LS1.2 10533A-MIA-AM1.2 10533A-RED-SBS1.2 10533A-MIA-CL1.2 10533A-RED-CL2.2The virtual machines are configured to automatically log on as Fabrikam\Administrator with the password,

Pa$$w0rd, except for the following virtual machines:

MIA-CL1 as Fabrikam\Andreas, with the password, Pa$$w0rd RED-CL2 as Fabrikam\Tzipi, with the password, Pa$$w0rd


33/364


ROM-CL3 as Fabrikam\Marcel, with the password, Pa$$w0rd INT-CL4 as INT-CL4\Administrator, with the password, Pa$$w0rd MIA-ED1 as MIA-ED1\Administrator, with the password, Pa$$w0rd MIA-RAS1 as MIA-RAS1\Administrator, with the password, Pa$$w0rd


1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.2. In the Virtual Machines list, right-click 10533A-MIA-DC1.2, and click Start.3. Right-click 10533A-MIA-DC1.2 and click Connect.4. In the Virtual Machine Connection window, wait until the virtual machine has booted up completely

before continuing.

5. On Host2, click Start, click Administrative Tools, and then click Hyper-V Manager.6. In the Virtual Machines list, right-click 10533A-MIA-RAS1.2 and click Start.7. Right-click 10533A-MIA-RAS1.2 and click Connect.8. In the Virtual Machine Connection window, wait until the virtual machine has booted up completely

before continuing.

9. On Host1, in the Virtual Machines list, right-click 10533A-MIA-SQL1.2 and click Start.10. Right-click 10533A-MIA-SQL1.2 and click Connect.11. On Host1, in the Virtual Machines list, right-click 10533A-ROM-LS2.2 and click Start.12. Right-click 10533A-ROM-LS2.2 and click Connect.13. On Host1, in the Virtual Machines list, right-click 10533A-MIA-ED1.2 and click Start.14. Right-click 10533A-MIA-ED1.2 and click Connect.15. On Host1, in the Virtual Machines list, right-click 10533A-ROM-CL3.2 and click Start.16. Right-click 10533A-ROM-CL3.2 and click Connect.17. On Host1, in the Virtual Machines list, right-click 10533A-INT-CL4.2 and click Start.18. Right-click 10533A-INT-CL4.2 and click Connect.19. On Host2, in the Virtual Machines list, right-click 10533A-MIA-LS1.2 and click Start.20. Right-click 10533A-MIA-LS1.2 and click Connect.21. On Host2, in the Virtual Machines list, right-click 10533A-MIA-AM1.2 and click Start.22. Right-click 10533A-MIA-AM1.2 and click Connect.23. On Host2, in the Virtual Machines list, right-click 10533A-RED-SBS1.2 and click Start.24. Right-click 10533A-RED-SBS1.2 and click Connect.25. On Host2, in the Virtual Machines list, right-click 10533A-MIA-CL1.2 and click Start.26. Right-click 10533A-MIA-CL1.2 and click Connect.27. On Host2, in the Virtual Machines list, right-click 10533A-RED-CL2.2 and click Start.28. Right-click 10533A-RED-CL2.2 and click Connect.


34/364


29. When 10533A-MIA-CL1.2 has booted up completely, close the Virtual Machine Connection window.30. On Host2, click Start, click All Programs, click Accessories, and then click Remote Desktop

Connection.

31. In the Remote Desktop Connection window, click Options.32. Click the Local Resources tab, and then under Remoteaudio, click Settings.33. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.34. Under Remote audiorecording, click Record from thiscomputer, and then click OK.35. Click the General tab.36. Under Logon settings, in the Computer box, type mia-cl1.fabrikam.com.37. In the User name box, type Fabrikam\Andreas, and then click Connect.38. On the Remote Desktop Connection page, click Connect.39. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.40. On the Remote Desktop Connection window, select the Dont ask me again for connections to this

computer check box, and then click Yes.41. On Host2, when 10533A-RED-CL2.2 has booted up completely, close the Virtual Machine

Connection window.

42. On Host2, click Start, click All Programs, click Accessories, and then click Remote DesktopConnection.

43. In the Remote Desktop Connection window, click Options.44. Click the Local Resources tab, and then under Remoteaudio, click Settings.45. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.46. Under Remote audiorecording, click Record from thiscomputer, and then click OK.47. Click the General tab.48. Under Logon settings, in the Computer box, type red-cl2.fabrikam.com.49. In the User name box, type Fabrikam\Ebru, and then click Connect.50. On the Remote Desktop Connection page, click Connect.51. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.52. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


53. On Host1, when 10533A-ROM-CL3.2 has booted up completely, close the Virtual MachineConnection window.


55. In the Remote Desktop Connection window, click Options.56. Click the Local Resources tab, and then under Remoteaudio, click Settings.57. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.58. Under Remote audiorecording, click Record from thiscomputer, and then click OK.59. Click the General tab.


35/364


60. Under Logon settings, in the Computer box, type rom-cl3.fabrikam.com.61. In the User name box, type Fabrikam\Marcel, and then click Connect.62. On the Remote Desktop Connection page, click Connect.63. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.64. On the Remote Desktop Connection window, select the Dont ask me again for connections to thiscomputer check box, and then click Yes.65. On Host1, when 10533A-INT-CL4.2 has booted up completely, close the Virtual Machine Connection

window.


67. In the Remote Desktop Connection window, click Options.68. Click the Local Resources tab, and then under Remoteaudio, click Settings.69. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.70. Under Remote audiorecording, click Record from thiscomputer, and then click OK.71. Click the General tab.72. Under Logon settings, in the Computer box, type int-cl4.73. In the User name box, type INT-CL4\Administrator, and then click Connect.74. On the Remote Desktop Connection page, click Connect.75. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.76. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


Verify that all services set to Automatic have started on all virtual machines. Most notably, check 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.3. If not, right-click the service and click Start.

Important: All connections to MIA-CL1.2, RED-CL2.2, ROM-CL3.2and INT-CL4.2 will require using

a Remote Desktop Connection with remote audio playback and remote audio recording enabled,unless otherwise specifically instructed.

Note: If the virtual machines are reporting that they need to be activated, run slmgr.vbs rearm froma command prompt and then reboot the server.


36/364


Exercise 1: Configuring the Topology for External Access

Scenario

Define a new Edge server topology to allow remote access for your users and federated partners for

conferencing, A/V and SIP, as well as provide public IM connectivity.

Using Topology Builder: download the current (Lab) virtual Lync Server 2010 deployment, add the EdgeServer, and define the services. Then publish the new topology into the central management store. Export

the new topology, so that it can be used to configure and install the Edge server


1. Add the new Edge server to the existing topology.2. Export the new topology.

Important: On all virtual machines, verify whether all of the services set to start automatically havestarted. Most notably, check the Exchange, SQL Server, and Lync Server 2010 services. To do so, clickStart, 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 click Start.

Task 1: Add the new Edge server to the existing topology.1. Using Topology Builder, define a new Single computer Edge pool to the Fabrikam topology in the

Miami site.

2. Use the information in the following tables to complete the wizard.Wizard Step Value

Edge Pool FQDNmia-ed1.fabrikam.com

Single computer pool

Select features Enable Federation (Port 5061)

3. Define the external FQDNs and IP addresses. Use the following information.External FQDNs Port

sip.fabrikam.com 443

webconf.fabrikam.com 443

avconf.fabrikam.com 443

4. Define the internal IP address as 10.0.10.14.5. Define the external IP addresses. Use the following information.

External FQDNs IP Address

SIP Access 172.16.10.100

Web Conferencing 172.16.10.101

A/V Conferencing 172.16.10.102


37/364


6. Finish the Define New Edge Pool wizard with the following information.Wizard Step Value

Next Hop mia-ls1.fabrikam.com Miami

Associated Front End Pools

mia-ls1.fabrikam.com

red-sbs1.fabrikam.com

rom-ls2.fabrikam.com

7. Edit the Miami site and enable this Edge server as the Site federation route assignment.8. Publish the new topology and verify it was successful published.

Task 2: Export the new topology.1. Using Lync Server Management Shell, export the new configuration as Config.zip.2. Copy the Config.zip file to C:\Labfiles on the Edge server.

Results: After this exercise, you should have defined a new Edge Pool, defined internal and externalFQDNs and IP addresses, and then published the topology. You should have also exported theconfiguration for Edge server role deployment.


38/364


Exercise 2: Deploying Edge Server and Configuring Remote Access

Scenario

Using the Lync Server Deployment Wizard, define and install the Edge server roles. Configure certificates

and start the Edge services. The Lync Server 2010 setup files are located on the Edge server in

C:\LabFiles\LS2010.


1. Install the Edge server role.2. Request and assign certificates.3. Start the Lync Server Edge services.4. Create the necessary Edge DNS records.

Task 1: Install the Edge server role.1. On MIA-ED1, launch Lync Server 2010 Setup.2. Use the Lync Server Deployment wizard to install Local Configuration Store by using the exported

Config.zip file.3. Use the Lync Server Deployment wizard to set up or remove Lync Server components.

Task 2: Request and assign certificates.Note: For the Lab environment and the virtual topology, you will use private certificates from internal

CA, requesting them real time during Lync Server setup. The internal CA is MIA-DC1.Fabrikam.com\FabrikamCA. If your certificate request fails or is denied, restart the Active DirectoryCertificate Services on MIA-DC1 and retry the request steps in this section.

1. Use the Lync Server - Deployment Wizard to request and assign certificates from the internal CA.2. Use the following information in the Certificate Request wizard to request a certificate for the Edge

internal interface.

Wizard Step Value

Internal CA MIA-DC1.Fabrikam.com\FabrikamCA.

Friendly NameMIA-ED1 Internal Certificate

Bit Length: 2048

Organization Fabrikam

Organizational Unit IT

Country/Region United States

State/Province Florida

City/Locality Miami

SIP Domain setting onSubject Alternate Names(SANs)

Fabrikam.com


39/364


3. Use the Certificate Assignment wizard to assign the MIA-ED1 Internal Certificate to the Edge internalinterface.

4. Use the following information in the Certificate Request wizard to request a certificate for the ExternalEdge interface.

Wizard Step Value

Internal CA MIA-DC1.Fabrikam.com\FabrikamCA.

Friendly NameMIA-ED1 External Certificate

Bit Length: 2048

Organization Fabrikam Corporation

Organizational Unit IT

Country/Region United States

State/Province Florida

City/Locality Miami

5. Use the Certificate Assignment wizard to assign the MIA-ED1 External Certificate to the External Edgeinterface.

Task 3: Start the Lync Server Edge services.1. Use the Lync Server Deployment wizard to start the Services on the Edge server.

Task 4: Create the necessary Edge DNS records.You now need to create the necessary DNS records for external user access. The MIA-RAS1 virtual

machine is acting as the public DNS server for this environment and it is where you will create the records.1. On MIA-RAS1, create the necessary HOST and SRV records.2. Use the following table to create the HOST records.

HOST record (A) IP Address

sip 172.16.10.100

webconf 172.16.10.101

avconf 172.16.10.102

3. Use the following table to create the SRV records.Service Protocol

Priority andWeight

Port Host offering the service

_sipexternaltls _tcp Defaults 443 sip.fabrikam.com

_sipfederationtls _tcp Defaults 5061 sip.fabrikam.com

_sip _tls Defaults 443 sip.fabrikam.com


40/364


Results: After this exercise, you should have gone through the process of moving an exported localconfiguration store to an Edge server, and then deploying the Edge server role. You will have alsocreated the necessary public DNS records.


41/364


Exercise 3: Testing and Verifying External User Access

Scenario

You will now test and verify external user access by using Microsoft Lync 2010 on the external client

virtual machine. You will also verify that remote access is available for IM, presence, web, and A/V

conferencing.


1. Grant rights to external user access.2. Test external user access.

Task 1: Grant rights to external user access.1. Using the Lync Server Control Panel, configure the External Access Policy to enable communications

with Federated, remote and public users for everyone.

2. For the Access Edge Configuration policy, enable federation, partner domain discovery, remote useraccess and anonymous user access to conferences.

Task 2: Test external user access.1. On MIA-CL1, ensure you are logged on to Microsoft Lync as [email protected]. On RED-CL2, ensure you are logged on to Microsoft Lync as [email protected]. On ROM-CL3, ensure you are logged on to Microsoft Lync as [email protected]. On INT-CL4, log on to the VM as INT-CL4\Administrator.

NOTE: The local administrator profile is setup for Ebru Ersan.

5. On INT-CL4, log on to Microsoft Lync as [email protected], Fabrikam\Ebru with the password ofPa$$w0rd

6. Have various IM sessions between the internal and external clients.7. Test external Web and A/V Conferencing by adding a third participant to the IM session, RED-CL2

logged in as Fabrikam\Tzipi. Determine what features are available, such as:

Desktop sharing Application sharing Adding AudioNote: This environment does not have an HTTP Reverse Proxy, so not all features will be available.

Results: After completing this exercise, you should have tested and verified your Edge serverdeployment by logging on to Lync from an external client and testing IM and Presence, as well asweb and A/V conferencing.

Important: After this lab, we recommended that you take a snapshot of all running virtual machinesbefore starting the next lab. To do so, in Hyper-V Manager, highlight all running virtual machines,right-click, and then click Snapshot.


42/364

Lab Instructions: Configuring Basic Enterprise Voice Functionality 1

Module 6

Lab Instructions: Configuring Basic Enterprise VoiceFunctionality

Contents:Exercise 1: Configuring the Topology for Enterprise Voice 8

Exercise 2: Configuring Lync Server 2010 Enterprise Voice 10


43/364

2 Lab Instructions: Configuring Basic Enterprise Voice Functionality

Lab: Configuring Basic Enterprise Voice Functionality

Scenario

During this lab, you will perform several tasks related to configuring Microsoft Lync Server 2010 Enterprise

Voice. You will use the Topology Builder to add the necessary PSTN Endpoints and then publish the new

topology.

Then you will begin Lync Server Enterprise Voice deployment by creating three Dial Plans and a series of

Normalization Rules for the two sites and the branch site.

In this lab you will:

Edit the topology to include the PSTN gateways. Publish the new topology. Create dial plans for Miami, Redmond, and Rome. Create normalization rules for the three dial plans.As the administrator for Fabrikam, you want to deploy Enterprise Voice at the Miami, Rome, and

Redmond sites.

Important: We recommend that the steps in this and every lab be split between the two students in

your pod. It is left up to the students to determine when to share tasks in order for both students togain an understanding of the concepts of each lab. If you need help, please inform the instructor. Pleasenote that if you both try to do tasks at the same time, you may overwrite each others work and possiblylose data.


44/364


45/364


a. Right-click 10533A-INT-CL4.2 and click Start.b. Right-click 10533A-INT-CL4.2 and click Connect.

10. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-LS1.2is not running:a. Right-click 10533A-MIA-LS1.2 and click Start.b. Right-click 10533A-MIA-LS1.2 and click Connect.

11. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-AM1.2 is not running:a. Right-click 10533A-MIA-AM1.2 and click Start.b. Right-click 10533A-MIA-AM1.2 and click Connect.

12. On Host2, in the Virtual Machines list, if the virtual machine 10533A-RED-SBS1.2 is not running:a. Right-click 10533A-RED-SBS1.2 and click Start.b. Right-click 10533A-RED-SBS1.2 and click Connect.

13. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-CL1.2 is not running:a. Right-click 10533A-MIA-CL1.2 and click Start.b. Right-click 10533A-MIA-CL1.2 and click Connect.

14. On Host2, in the Virtual Machines list, if the virtual machine 10533A-RED-CL2.2 is not running:a. Right-click 10533A-RED-CL2.2 and click Start.b. Right-click 10533A-RED-CL2.2 and click Connect.


Connection.

17. In the Remote Desktop Connection window, click Options.18. Click the Local Resources tab, and then under Remoteaudio, click Settings.19. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.20. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.21. Click the General tab.22. Under Logon settings, in the Computerbox, type mia-cl1.fabrikam.com.23. In the User namebox, type Fabrikam\Andreas, and then click Connect.24. On the Remote Desktop Connection page, click Connect.25. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.26. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


27. On Host2, when 10533A-RED-CL2.2 has booted up completely, close the Virtual MachineConnection window.


29. In the Remote Desktop Connection window, click Options.30. Click the Local Resources tab, and then under Remoteaudio, click Settings.


46/364


31. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.32. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.33. Click the General tab.34. Under Logon settings, in the Computerbox, type red-cl2.fabrikam.com.35. In the User namebox, type Fabrikam\Ebru, and then click Connect.36. On the Remote Desktop Connection page, click Connect.37. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.38. On the Remote Desktop Connection window, select the Dont ask me again for connections to this




41. In the Remote Desktop Connection window, click Options.42. Click the Local Resources tab, and then under Remoteaudio, click Settings.43. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.44. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.45. Click the General tab.46. Under Logon settings, in the Computerbox, type rom-cl3.fabrikam.com.47. In the User namebox, type Fabrikam\Marcel. and then click Connect.48. On the Remote Desktop Connection page, click Connect.49. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.50. On the Remote Desktop Connection window, select the Dont ask me again for connections to thiscomputer check box, and then click Yes.51. On Host1, when 10533A-INT-CL4.2 has booted up completely, close the Virtual Machine Connection

window.


53. In the Remote Desktop Connection window, click Options.54. Click the Local Resources tab, and then under Remoteaudio, click Settings.55. Under Remote audio playback, verify thatPlay on this computer is selected. If it is not, select it.56. Under Remote audiorecording, clickRecord from thiscomputer, and then click OK.57. Click the General tab.58. Under Logon settings, in the Computerbox, type int-cl4.59. In the User namebox, type INT-CL4\Administrator, and then click Connect.60. On the Remote Desktop Connection page, click Connect.61. On the Windows Security window, in the Passwordbox, type Pa$$w0rd, and then click OK.


47/364


62. On the Remote Desktop Connection window, select the Dont ask me again for connections to thiscomputer check box, and then click Yes.



following steps:


Important: All connections to MIA-CL1.2, RED-CL2.2, ROM-CL3.2and INT-CL4.2 will require usinga Remote Desktop Connection with remote audio playback and remote audio recording enabled,unless otherwise specifically instructed.


48/364




49/364


Exercise 1: Configuring the Topology for Enterprise Voice

Scenario

In this exercise, you will configure PSTN gateways for Miami, Rome, and Redmond. They will all point to

the PSTN emulator running on MIA-CL1.

Create new PSTN gatewaysfor Miami, Rome, and Redmond.

Configure the PSTN IP addresses of the Front End Servers. Publish the new topology.


Task 1: Create new PSTN gateways for Miami, Rome, and Redmond.1. On MIA-LS1, use the Topology Builder to create a new IP/PSTN Gateway for Miami.

Wizard Step Value

Gateway FQDN or IP Address 1.1.1.1

Listening port for IP/PSTN gateway 5060

SIP Transport Protocol TCP

2. On MIA-LS1, use the Topology Builder to create a new IP/PSTN Gateway for Rome.Wizard Step Value




3. On MIA-LS1, use the Topology Builder to create a new IP/PSTN Gateway to Redmond.Wizard Step Value




Task 2: Configure the PSTN IP addresses for the Front End Servers.1. On MIA-LS1, use the Topology Builder to configure MIA-LS1.Fabrikam.com to limit service usage to

selected IP Addresses.

2. Set 10.0.10.12 for the Primary IP address.3. Set 1.1.1.12 for the PSTN IP address.4. Enable the TCP port on the Mediation Server and set the listening port to 5060.


50/364


5. Associate the 1.1.1.1 PSTN Gateway to this Mediation server.6. Use the Topology Builder to configure ROM-LS2.Fabrikam.com to limit service usage to selected IP

Addresses.

7. Set 10.0.30.12 for the Primary IP address.8. Set 1.1.3.12 for the PSTN IP address.9. Enable the TCP port on the Mediation Server and set the listening port to 5060.10. Associate the 1.1.1.3 PSTN Gateway to this Mediation server.11. Use the Topology Builder to configure RED-SBS1.Fabrikam.com to limit service usage to selected IP

Addresses.

12. Set 10.0.20.12 for the Primary IP address.13. Set 1.1.2.12 for the PSTN IP address.14. Enable the TCP port on the Mediation Server and set the listening port to 5060.15. Associate the 1.1.1.2 PSTN Gateway to this Mediation server.

Task 3: Publish the new topology.1. On MIA-LS1, use the Topology Builder to publish the new topology.

Results: After this exercise, you should have configured the topology for Enterprise Voice by configuringPSTN Gateways and limiting service usages to specific IP addresses on all of the front end servers, andthen publishing the new topology.


51/364


Exercise 2: Configuring Lync Server 2010 Enterprise VoiceIn this exercise, you will configure Lync Server 2010 Enterprise Voice Dial Plans and Normalization Rules.

The steps involved are:

Create Dial Plans for Miami, Rome, and Redmond. Create normalization rules for the Miami location. Create normalization rules for the Rome location. Create normalization rules for the Redmond location.

Task 1: Create dial plans for Miami, Rome, and Redmond.1. On MIA-LS1, use the Lync Server Control Panel to create three different Site Dial Plans using the

following information for their simple names.

Site Simple name

Miami Miami.Fabrikam.com

Rome Rome.Fabrikam.com

Redmond Redmond.Fabrikam.com

Task 2: Create normalization rules for the Miami location.1. On MIA-LS1, use the Lync Server Control Panel to create normalization rules for Miami.Miami

NameStartingDigits Length

Digits toRemove Digits to Add Test

Fabrikam USOperator

0 Exactly 1 1 +13055552009 0 to

+13055552009

Fabrikam ItalyOperator

9 Exactly 1 1 +390655554005 9 to

+390655554005

Miami 4 DigitInternal

2 Exactly 4 0 +1305555 2001 to

+13055552001

Redmond 4Digit Internal

3 Exactly 4 0 +1425555 3001 to

+14255553001

Rome 4 Digit

Internal

4 Exactly 4 0 +39065555 4001 to

+390655554001

Miami 7 Digit Exactly 7 0 +1305 5552001 to

+13055552001

US 10 Digit Exactly 10 0 +1 3055552001 to

+13055552001


52/364




US 11 DigitLongDistance

1 Exactly 11 0 + 13055552001 to

+13055552001

USInternational

011 At Least 5 3 + 011390655554001 to

+390655554001

2. Remove the Prefix All rule. Task 3: Create normalization rules for the Rome location.

1. On MIA-LS1, use the Lync Server Control Panel to create or select normalization rules for Redmond.Rome

Name

Starting

Digits Length

DigitstoRemov

e Digits to Add Test

Fabrikam USOperator

0 Exactly 1 1 +13055552009 0 to

+13055552009


9 Exactly 1 1 +390655554005 9 to

+390655554005


2 Exactly 4 0 +1305555 2001 to

+13055552001


3 Exactly 4 0 +1425555 3001 to

+14255553001

Rome 4 DigitInternal

4 Exactly 4 0 +39065555 4001 to

+390655554001

Rome Local andNational

0[1-9] At Least 8 2 + 0554395001

+54395001

RomeInternational

00 At Least 4 2 + 0013055552001 to

+13055552001

2. Remove the Prefix All rule. Task 4: Create normalization rules for the Redmond location.

1. On MIA-LS1, use the Lync Server Control Panel to create or select normalization rules for Redmond.


53/364


Redmond



Fabrikam USOperator

0 Exactly 1 1 +13055552009 0 to

+13055552009


9 Exactly 1 1 +390655554005

9 to

+390655554005


2 Exactly 4 0 +1305555 2001 to

+13055552001


3 Exactly 4 0 +1425555 3001 to

+14255553001

Rome 4 DigitInternal

4 Exactly 4 0 +39065555 4001 to

+390655554001

Redmond 7Digit Local

Exactly 7 0 +1425 5553001 to

+14255553001

US 10 Digit Exactly10

0 +1 4255553001 to

+14255553001

US 11 DigitLong Distance

1 Exactly11

0 + 14255553001 to

+14255553001

USInternational

011 At Least5

3 + 011390655554001 to

+390655554001

2. Remove the Prefix All rule.3. Commit all changes.

Results: After this exercise, you should have created new user dial plans for Miami, Redmond andRome, as well as normalization rules for each dial plan.

Important: After this lab, it is recommended that you take a snapshot of all running virtual machinesbefore starting the next lab. To do so, in Hyper-V Manager, highlight all running virtual machines, right-click and then click Snapshot.


54/364

Lab Instructions: Extending Enterprise Voice Functionality 1

Module 7

Lab Instructions: Extending Enterprise Voice Functionality

Contents:Exercise 1: Configuring Voice Policies and PSTN Usages 7

Exercise 2: Configuring Routes and Site Trunks 9

Exercise 3: Configuring Call Park 12

Exercise 4: Configuring the Unassigned Numbers Feature 13

Exercise 5: Configuring Users for Enterprise Voice 16

Exercise 6: Testing and Verifying Enterprise Voice Functionality 18


55/364

2 Lab Instructions: Extending Enterprise Voice Functionality

Lab: Implementing Enterprise Voice

Scenario

Building on the current voice implementation of Lync Server 2010, management has decided to configure

and enable additional Enterprise Voice features to the company. In this lab, you will configure the Routes

and Trunk options, create and configure a call park orbit, and configure the unassigned number feature.

After configuring the voice features you will test and verify their setup.

Important: We recommend that the steps in this and every lab be split between the two students inyour pod. It is left up to the students to determine when to share tasks in order for both students togain an understanding of the concepts of each lab. If you need help, please inform the instructor. Pleasenote that if you both try to do tasks at the same time, you may overwrite each others work and possiblylose data.

Start the virtual machinesThis lab requires the virtual machines running from the previous lab and depends on the completion of

Lab 5 and 6. The virtual machines are configured to automatically log on as Fabrikam\Administrator with

the password, Pa$$w0rd, except for the following virtual machines:

MIA-CL1 as Fabrikam\Andreas, with the password, Pa$$w0rd RED-CL2 as Fabrikam\Tzipi, with the password, Pa$$w0rd ROM-CL3 as Fabrikam\Marcel, with the password, Pa$$w0rd INT-CL4 as INT-CL4\Administrator, with the password, Pa$$w0rd MIA-ED1 as MIA-ED1\Administrator, with the password, Pa$$w0rd MIA-RAS1 as MIA-RAS1\Administrator, with the password, Pa$$w0rd


56/364



1. On Host1, click Start, click Administrative Tools, and then click Hyper-V Manager.2. In the Virtual Machines list, if the virtual machine 10533A-MIA-DC1.2 is not running:

a. Right-click 10533A-MIA-DC1.2 and click Start.b. Right-click 10533A-MIA-DC1.2 and click Connect.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 10533A-MIA-RAS1.2 is not running:

a. Right-click 10533A-MIA-RAS1.2 and click Start.b. Right-click 10533A-MIA-RAS1.2 and 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 10533A-MIA-SQL1.2 is not running:a. Right-click 10533A-MIA-SQL1.2 and click Start.b. Right-click 10533A-MIA-SQL1.2 and click Connect.

6. On Host1, in the Virtual Machines list, if the virtual machine 10533A-ROM-LS2.2 is not running:a. Right-click 10533A-ROM-LS2.2 and click Start.b. Right-click 10533A-ROM-LS2.2 and click Connect.

7. On Host1, in the Virtual Machines list, if the virtual machine 10533A-MIA-ED1.2 is not running:a. Right-click 10533A-MIA-ED1.2 and click Start.b. Right-click 10533A-MIA-ED1.2 and click Connect.

8. On Host1, in the Virtual Machines list, if the virtual machine 10533A-ROM-CL3.2 is not running:a. Right-click 10533A-ROM-CL3.2 and click Start.b. Right-click 10533A-ROM-CL3.2 and click Connect.

9. On Host1, in the Virtual Machines list, if the virtual machine 10533A-INT-CL4.2 is not running:a. Right-click 10533A-INT-CL4.2 and click Start.b. Right-click 10533A-INT-CL4.2 and click Connect.

10. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-LS1.2 is not running:a. Right-click 10533A-MIA-LS1.2 and click Start.b. Right-click 10533A-MIA-LS1.2 and click Connect.

11. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-AM1.2 is not running:a. Right-click 10533A-MIA-AM1.2 and click Start.b. Right-click 10533A-MIA-AM1.2 and click Connect.

12. On Host2, in the Virtual Machines list, if the virtual machine 10533A-RED-SBS1.2 is not running:a. Right-click 10533A-RED-SBS1.2 and click Start.


57/364


b. Right-click 10533A-RED-SBS1.2 and click Connect.13. On Host2, in the Virtual Machines list, if the virtual machine 10533A-MIA-CL1.2 is not running:

a. Right-click 10533A-MIA-CL1.2 and click Start.b. Right-click 10533A-MIA-CL1.2 and click Connect.

14. On Host2, in the Virtual Machines list, if the virtual machine 10533A-RED-CL2.2 is not running:a. Right-click 10533A-RED-CL2.2 and click Start.b. Right-click 10533A-RED-CL2.2 and click Connect.


Connection.

17. In the Remote Desktop Connection window, click Options.18. Click the Local Resources tab, and then under Remoteaudio, click Settings.19. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.20. Under Remote audiorecording, click Record from thiscomputer, and then click OK.21. Click the General tab.22. Under Logon settings, in the Computer box, type mia-cl1.fabrikam.com.23. In the User name box, type Fabrikam\Andreas, and then click Connect.24. On the Remote Desktop Connection page, click Connect.25. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.26. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


27. On Host2, when 10533A-RED-CL2.2 has booted up completely, close the Virtual MachineConnection window.


29. In the Remote Desktop Connection window, click Options.30. Click the Local Resources tab, and then under Remoteaudio, click Settings.31. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.32. Under Remote audiorecording, click Record from thiscomputer, and then click OK.33. Click the General tab.34. Under Logon settings, in the Computer box, type red-cl2.fabrikam.com.35. In the User name box, type Fabrikam\Tzipi, and then click Connect.36. On the Remote Desktop Connection page, click Connect.37. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.38. On the Remote Desktop Connection window, select the Dont ask me again for connections to this




58/364



41. In the Remote Desktop Connection window, click Options.42. Click the Local Resources tab, and then under Remoteaudio, click Settings.43. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.44. Under Remote audiorecording, click Record from thiscomputer, and then click OK.45. Click the General tab.46. Under Logon settings, in the Computer box, type rom-cl3.fabrikam.com.47. In the User name box, type Fabrikam\Marcel, and then click Connect.48. On the Remote Desktop Connection page, click Connect.49. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.50. On the Remote Desktop Connection window, select the Dont ask me again for connections to this


51.

On Host1, when 10533A-INT-CL4.2 has booted up completely, close the Virtual Machine Connectionwindow.


53. In the Remote Desktop Connection window, click Options.54. Click the Local Resources tab, and then under Remoteaudio click Settings.55. Under Remote audio playback, verify that Play on this computer is selected. If it is not, select it.56. Under Remote audiorecording, click Record from thiscomputer, and then click OK.57. Click the General tab.58. Under Logon settings, in the Computer box, type int-cl4.59. In the User name box, type INT-CL4\Administrator, and then click Connect.60. On the Remote Desktop Connection page, click Connect.61. On the Windows Security window, in the Password box, type Pa$$w0rd, and then click OK.62. On the Remote Desktop Connection window, select the Dont ask me again for connections to this




following steps:


Important: All connections to MIA-CL1.2, RED-CL2.2, ROM-CL3.2and INT-CL4.2 will require usinga Remote Desktop Connection with remote audio playback and remote audio recording enabled,unless otherwise specifically instructed.


59/364




60/364


Exercise 1: Configuring Voice Policies and PSTN UsagesIn this exercise, you will create various voice policies and PSTN Usages for each site. You will create two

user voice policies for each site, one that allows long international calls and one that allows long distance

calls. You will then create a site voice policy that is more restricted and will only allow local calls.

The steps involved are:

1. Create the Miami voice policies and PSTN usages.2. Create the Redmond voice policies and PSTN usages.3. Create the Rome voice policies and PSTN usages.


Task 1: Create the Miami voice policies and PSTN usages.1. On MIA-LS1, use the Lync Server Control Panel to create a user policy that allows International calls

and is called Miami International.

2. Select Enable malicious call tracing.3. Create the following PSTN Usages:

a. Miami Localb. Miami Long Distancec. Miami International

4. Create a user voice policy for Miami that allows long distance and is called Miami Long Distance.5. Select Enable malicious call tracing.6. Select the following PSTN usages:

a. Miami Localb. Miami Long Distance

7. Create a site voice policy for Miami that allows only local calls.8. Select Enable malicious call tracing.9. Select the following PSTN usage:

a. Miami Local Task 2: Create the Redmond voice policies and PSTN usages.

1. On MIA-LS1, use the Lync Server Control Panel to create a user policy that allows International callsand is called Redmond International.

2. Select Enable malicious call tracing.3. Create the following PSTN Usages:

a. Redmond Localb. Redmond Long Distance


61/364


c. Redmond International4. Create a user voice policy for Redmond that allows long distance and is called Redmond Long

Distance.

5. Select Enable malicious call tracing.6. Select the following PSTN usages:

a. Redmond Localb. Redmond Long Distance

7. Create a site voice policy for Redmond that allows only local calls.8. Select Enable malicious call tracing.9. Select the following PSTN usage:

a. Redmond Local Task 3: Create the Rome voice policies and PSTN usages.

1. On MIA-LS1, use the Lync Server Control Panel to create a user policy that allows International callsand is called Rome International.

2. Select Enable malicious call tracing.3. Create the following PSTN usages:

a. Rome Localb. Rome Long Distancec. Rome International

4. Create a user voice policy for Rome that allows long distance and is called Rome Long Distance.5. Select Enable malicious call tracing.6. Select the following PSTN usages:

a. Rome Localb. Rome Long Distance

7. Create a site voice policy for Rome that allows only local calls.8. Select Enable malicious call tracing.9. Select the following PSTN usage:

a. Rome Local

Results: After this exercise, you should have created the voice policies and PSTN usages for each site.This included two user voice policies and one site voice policy for each.


62/364


Exercise 2: Configuring Routes and Site Trunks

Scenario

In the two data sites and the branch office, each must route their local calls to their local PSTN gateway,

and to reduce calling costs to the other sites when a call is identified as local to that site. In this exercise,

you will create various routes, including least-cost routes, for the three sites, and you will also create trunk

configurations for each site.


1. Create routes for the Miami site.2. Create routes for the Redmond site.3. Create routes for the Rome site.4. Create a trunk configuration for the Miami site.5. Create a trunk configuration for the Redmond site.6. Create a trunk configuration for the Rome site.

Task 1: Create routes for the Miami site.1. On MIA-LS1, use the Lync Server Control Panel to create routes for the Miami site.2. Use the following table to create the Miami routes.Miami Routes

Route NameStartingDigits Match Pattern Associated Gateways Associated PSTN Usage

Miami Local +1305 ^\+1305 PstnGateway:1.1.1.1 Miami Local

PstnGateway:1.1.1.2 Redmond Local

MiamiNational

+1 ^\+1 PstnGateway:1.1.1.1 Miami Long Distance

PstnGateway:1.1.1.2

MiamiInternational

+ ^\+(?!(1)) PstnGateway:1.1.1.1 Miami International

Exceptions:+1

PstnGateway:1.1.1.2

US to RomeLCR

+3906 ^\+3906 PstnGateway:1.1.1.3 Redmond Local

PstnGateway:1.1.1.1 Miami Local

US to Italy

LCR

+390 ^\+390 PstnGateway:1.1.1.3 Rome Long Distance

PstnGateway:1.1.1.1

Task 2: Create routes for the Redmond site.1. On MIA-LS1, use the Lync Server Control Panel to create routes for the Redmond site.2. Use the following table to create the Redmond routes.


63/364


Redmond Routes


Redmond

Local

+1425 ^\+1425 PstnGateway:1.1.1.2 Redmond LocalPstnGateway:1.1.1.1 Miami Local

RedmondNational

+1 ^\+1 PstnGateway:1.1.1.2 Redmond Long Distance

PstnGateway:1.1.1.1

RedmondInternational

+ ^\+(?!(1)) PstnGateway:1.1.1.2 Redmond InternationalExceptions:+1

PstnGateway:1.1.1.1

Task 3: Create routes for the Rome site.1. On MIA-LS1, use the Lync Server Control Panel to create routes for the Rome site.2. Use the following table to create the Rome routes.Rome Routes


Rome Local +3906 ^\+3906 PstnGateway:1.1.1.3 Rome Local

PstnGateway:1.1.1.1

RomeNational

+390 ^\+390 PstnGateway:1.1.1.3 Rome Long Distance

PstnGateway:1.1.1.1

RomeInternational

+ ^\+(?!(390)) PstnGateway:1.1.1.3 Rome International

Exceptions:+390

PstnGateway:1.1.1.1

Rome toRedmondLCR

+1425 ^\+1425 PstnGateway:1.1.1.2 Rome Local

PstnGateway:1.1.1.1

Rome toMiami LCR

+1305 ^\+1305 PstnGateway:1.1.1.1 Rome Local

PstnGateway:1.1.1.

10533ad-enu-labmanual

Documents