Planning for clients and devices lync server 2010 (rc)

Planning for Clients and Devices in Microsoft Lync Server 2010 (Release Candidate)

Published: September 2010

This document is provided “as-is”. Information and views expressed in this document, including

URL and other Internet Web site references, may change without notice. You bear the risk of

using it.

Some examples depicted herein are provided for illustration only and are fictitious. No real

association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any

Microsoft product. You may copy and use this document for your internal, reference purposes.

This document is confidential and proprietary to Microsoft. It is disclosed and can be used only

pursuant to a non-disclosure agreement.

Copyright © 2010 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, ActiveSync, ActiveX, Excel, Forefront, Groove, Hyper-V, Internet

Explorer, Lync, MSDN, MSN, OneNote, Outlook, PowerPoint, RoundTable, SharePoint,

Silverlight, SQL Server, Visio, Visual C++, Windows, Windows Media, Windows PowerShell,

Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All

other trademarks are property of their respective owners.

Contents

Planning for Clients and Devices in Lync Server 2010 (Release Candidate).............................1

Planning for Clients..................................................................................................................1

What's New in Client Deployment.........................................................................................1

Deciding Which Clients To Deploy........................................................................................6

Client Comparison Tables.....................................................................................................8

Client System Requirements..............................................................................................15

Lync 2010 and Online Meeting Add-in for Microsoft Lync 2010 System Requirements...15

Lync Server 2010 Attendant System Requirements........................................................17

Lync Web App Supported Platforms................................................................................18

Key Client Policies and Settings.........................................................................................19

Client Configuration Overview............................................................................................22

Planning for Client Migration...............................................................................................40

Client Planning Steps during Migration............................................................................40

Migration Considerations for Meetings............................................................................42

Client Version Check.......................................................................................................46

Migrating User Settings to Lync Server 2010..................................................................47

Planning for Devices..............................................................................................................55

Devices in Lync Server.......................................................................................................55

What's New for Devices......................................................................................................56

Choosing New Devices.......................................................................................................58

Desk Phone Comparison Table.......................................................................................61

Common Area Phone and Conferencing Device Comparison Table...............................62

Planning to Deploy Devices................................................................................................64

Supported Topologies for Devices...................................................................................64

Required Lync Server 2010 Components for Devices.....................................................64

System and Infrastructure Requirements for Devices.....................................................66

Deployment Guidelines and Process for Devices............................................................70

Planning to Manage and Troubleshoot Devices..................................................................72

Tools and Services for Managing and Troubleshooting Devices.....................................72

Updating Devices............................................................................................................75

Monitoring and Troubleshooting Devices.........................................................................77

Common Area Phone Configuration...................................................................................78

Analog Gateway and Device Configuration........................................................................82

Compatibility and Integration..................................................................................................84

Client Interoperability..........................................................................................................85

Lync 2010 Compatibility......................................................................................................89

Lync 2010 Integration.........................................................................................................92

Planning for Clients and Devices in Lync Server 2010 (Release Candidate)The topics in this section describe how to plan for Microsoft Lync Server 2010 communications

software clients and devices on your network.

Planning for Clients

Planning for Devices

Compatibility and Integration

Planning for ClientsThe topics in this section discuss planning considerations for deploying Microsoft Lync Server

2010 communications software clients. Whether you are deploying a new Lync Server 2010

installation or migrating from a previous Office Communications Server deployment, these topics

provide important client planning information. For details about planning for client deployment in a

migration scenario, see Planning for Client Migration.

What's New in Client Deployment

Deciding Which Clients To Deploy

Client Comparison Tables

Client System Requirements

Key Client Policies and Settings

Client Configuration Overview

Planning for Client Migration

What's New in Client Deployment

This section discusses new client and server features you should be aware of when planning for

deployment. Important changes or enhancements are available in the following areas:

Client configuration

Installation and updates

Alternate meeting clients for users without Microsoft Lync 2010 communications software

installed

Enhanced presence privacy

Manager/delegate scenario changes

Lync 2010 User Photo options

1


Client Configuration

In Microsoft Lync Server 2010, the Group Policy settings used in previous Office Communications

Server releases are now controlled by in-band provisioning client policies that are server-based.

In-band provisioning settings are managed by using the Lync Server Control Panel, the Windows

PowerShell command-line interface, or both. These tools replace the Windows Management

Interface (WMI) snap-in used to manage policy settings in earlier versions of Office

Communications Server. For example, in Office Communications Server 2007 R2, you could use

Group Policy to override conferencing policies for specific users. In Microsoft Lync Server 2010,

you can centrally manage all policy settings and apply them at the global level, site level, or tag

level (tags are settings that can be applied to a single user or to a group of users).

If you have an existing Office Communications Server 2007 R2 deployment, Office

Communications Server 2007 R2 clients will continue to use Group Policy during side-by-side

migration. However, if you want policy settings to carry over to Lync Server 2010 clients, you

need to configure the equivalent Lync Server 2010 in-band provisioning settings.

Comparison of In-band Provisioning Settings and Group Policy Settings

In-band provisioning settings Group Policy settings

Administrators can handle all client

configuration tasks in a single location, using a

single user interface.

Administrators must often work with other

departments in the organization (for example,

administrators who manage Active Directory

Domain Services (AD DS) or messaging) in

order to configure clients.

Settings can be configured at the global (that is,

domain or organizational unit), site, or tag level.

Tags are settings that can be applied to a single

user, or to a group of users.

Settings can only be configured at the global

and user levels.

In-band provisioning settings that are server-

based provide a consistent end-user

experience for people who are not joined to the

corporate domain, or who join using devices or

remote clients.

Group Policy settings that are distributed by

using Active Directory require that users be

connected to the corporate domain using a

computer.

Settings take effect immediately. Users must sign out of Windows and then sign

back in for settings to take effect.

In-band provisioning settings that are server-

based help make clients secure because they

do not depend on the client application to

enforce the policy.

Client applications could be modified by a

malicious user.

2


Installation and Updates

New features related to installation and updates are the distribution of setup as an executable file,

and the addition of update link options to Lync Server 2010 Client Version Check.

Lync 2010 Setup Executable

In earlier versions of Microsoft Communicator, setup was provided as an installer (.msi) package.

In Lync 2010 and the Microsoft Lync 2010 Attendee the setup files are provided as executable

(.exe) programs. The Microsoft Silverlight browser plug-in, which is a prerequisite for Lync Web

App, is also installed by using an .exe program. You can either deploy Silverlight for Lync Web

App users, or allow users to install Silverlight upon first use of Lync Web App when prompted.

If you want to use Group Policy to deploy these applications, you must prepare the files for

Windows Installer by creating a .zap file. For details, see "Packaging Software for Deployment" at

http://go.microsoft.com/fwlink/?LinkId=201091, and "Step-by-Step Guide to Software Installation

and Maintenance" at http://go.microsoft.com/fwlink/?LinkId=201092.

Client Version Update Options

Lync 2010 clients can now receive updated software from Windows Server Update Service

(WSUS) or Microsoft Update instead of from a location hosted on Lync Server 2010. When you

set a Client Version Policy for Lync 2010, the options Allow with upgrade and Block with

upgrade are still available. However, you no longer need to specify a location on the server for

updated software. Instead, if you are using WSUS, clients receive updates from WSUS.

Otherwise, clients receive updates from Microsoft Update.

Alternate Meeting Clients

Users without Lync 2010 installed can take advantage of the enhanced conferencing and

collaboration features of Lync Server 2010 by using either Lync Web App or the Lync 2010

Attendee.

In addition, you can determine which clients are available to users by configuring the meeting join

page.

Using Alternate Meeting Clients

You can provide users who don’t have Lync 2010 installed with the following options for joining

Lync Server 2010 meetings:

Lync Web App

Lync 2010 Attendee

Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007

3

http://go.microsoft.com/fwlink/?LinkId=201092



Use the following table to help you decide which of these clients is appropriate for your users and

your organization:

Conferencing Client Comparison Chart

Feature or requirement Microsoft Lync Web

App

Microsoft Lync 2010

Attendee

Microsoft Office

Communicator 2007 R2

or Microsoft Office

Communicator 2007

Web application Yes No No

Deployment or

installation

requirements

Silverlight Client application

(includes Silverlight

installation)

Not applicable

New Lync Server 2010

conferencing features

Yes1 Yes No

Dial-in conferencing Yes2 Yes2 Office Communicator

2007 R2 only

Integrated IP audio

and video

No Yes Yes

Anonymous join by

federated or external

users

Yes Yes Federated only

Authenticated join by

internal users

Yes Yes, if already

signed in with an

earlier client

Yes

Authenticated join by

external users

Yes No No

1All features are available except uploading files that are created using Microsoft PowerPoint

presentation graphics program. Installation of a Microsoft ActiveX control is required for desktop

or application sharing.2Dial-out conferencing is also supported (that is, if it is enabled).

Configuring the Meeting Join Web Page

You can control the clients that are available for joining scheduled Lync Server 2010 meetings by

configuring the meeting join page. A user who tries to join a meeting but does not have Lync 2010

installed is presented with the meeting join web page, which provides access to Lync Web App,

Lync 2010 Attendee, or Office Communicator 2007 R2.

You can configure the client options that display on this page. For example, if you prefer not to

deploy Lync 2010 Attendee, you can remove the download link from the meeting join page. For

details about configuring the meeting join web page, see Migration Considerations for Meetings.

4


Enhanced Presence Privacy

With Lync Server 2010 enhanced privacy mode, a user’s presence is visible to contacts in his or

her contact list but not to other people in the company.

Important:

Do not enable this feature until all users in a given pool have been migrated to Lync

2010. If earlier client versions are present within the pool, privacy management options

can be compromised or reset.

Manager/Delegate Scenario Changes

Lync 2010 fully supports the manager/delegate scenario. Microsoft Lync 2010 Attendant supports

the receptionist scenario only. For the manager/delegate scenario, both manager and delegate

must be signed in with the Lync 2010 client.

Lync 2010 Recording

The recording feature allows presenters to record all aspects of a Lync 2010 session including

who attended, audio, video, and content such as instant messaging (IM) conversations,

application sharing, PowerPoint presentations, handouts, and whiteboards. By default, the ability

to record is turned off. Recording can be enabled by configuring the recording conferencing

policy. For details, see the "Conferencing" section in Client Configuration Overview.

Lync 2010 User Photo Options

Lync 2010 supports display of user pictures. This section lists the default user photo options, and

then describes how you can modify these defaults by using the Lync Server 2010 Management

Shell.

By default, Lync 2010 users can access the following three choices by clicking Options, and then

clicking My Picture.

Default Options for My Picture in Lync 2010

Option Description

Do not show my picture The user’s picture is not shown.

Default corporate picture Shows the user picture in AD DS.

Show a picture from a web address The picture must meet the following criteria:

On a web server that does not require

authentication

30 KB or less in size

If you plan to allow the Default corporate picture option, verify that user pictures are present in

AD DS before deploying Lync 2010.

5


If you plan to allow the Show a picture from a web address option, be aware that users must

already have a personal picture on a public web site such as Windows Live Essentials, Flickr, or

Facebook. For details, see the Lync 2010 Help for this option.

Changing User Photo Default Options

You can change what users see on the My Picture tab by using the Windows PowerShell cmdlet

New-CSClientPolicy. The following table shows the relevant parameters.

CSClientPolicy User Photo Options

CSClientPolicy parameter Description

DisplayPhoto Specify one of the following command-line

options:

NoPhoto Photos are not displayed in

Lync 2010.

PhotosFromADOnly Only photos that

have been published in Active Directory can

be displayed.

AllPhotos (default) Either Active

Directory or custom photos can be

displayed.

MaxPhotoSizeKB Indicates the maximum size (in kilobytes) for

photos displayed in Lync 2010. Setting the

MaxPhotoSize to 0 prevents any photos from

being displayed in .

The default value is 30 kilobytes.

For details, see the Command-line Reference documentation.

Deciding Which Clients To Deploy

Microsoft Lync Server 2010 communications software supports several types of client software

that you can deploy to your organization’s users, including computer-installed client software,

web-based clients, and mobile devices. This topic outlines the different clients that you can use.

For a detailed comparison of the features provided by different clients, see Client Comparison

Tables.

Microsoft Lync 2010

Microsoft Lync 2010 is the default client for Lync Server 2010 meetings. Features include

presence, contact management, instant messaging (IM), telephony, and greatly enhanced

conferencing.

To implement the manager/delegate scenario with Lync 2010, both manager and delegate need

to install and use Lync 2010.

6


Microsoft Lync 2010 Attendee

Microsoft Lync 2010 Attendee is a rich conferencing client that allows users without Lync 2010

installed to fully participate in Lync Server 2010 meetings. Lync 2010 Attendee can be installed on

a per-user basis, so you can choose to selectively deploy this client during migration, or you can

allow users to download and install it as needed.

For details about how to control the conferencing client choices that appear on the online meeting

join page, see the “Configuring the Meeting Join Web Page” section in Migration Considerations

for Meetings.

Microsoft Lync Web App

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

collaboration and sharing features, as well as presenter meeting controls and dial-in and dial-out

voice conferencing.

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

not practical or possible to install Lync 2010 Attendee.

For details about how to control which client options appear on the meeting join page, see the

“Configuring the Meeting Join Web Page” section in Migration Considerations for Meetings.

Microsoft Lync Server 2010 Attendant

Microsoft Lync 2010 Attendant is an integrated call management application that enables a

receptionist to manage multiple conversations at once through rapid call handling, IM, and on-

screen routing.

Lync 2010 Attendant no longer supports the manager/delegate scenario. Both manager and

delegate must have Lync 2010 installed to access these features.

Microsoft Lync 2010 Mobile

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

organization who are connecting from a smartphone or a phone running a Professional edition of

Windows Mobile.

Microsoft Lync 2010 Phone Edition

Microsoft Lync 2010 Phone Edition is software that runs on intelligent Internet Protocol (IP)

phones (for example, USB-attached phones), and supports placing and receiving calls, enhanced

presence, and client audio capabilities for conferences.

Online Meeting Add-in for Microsoft Lync 2010

The Online Meeting Add-in for Microsoft Lync 2010 supports meeting management from within

Outlook. This software is installed automatically with Lync 2010.

7


Client Comparison Tables

The following tables compare the features and capabilities of Microsoft Lync Server

2010 communications software clients in the following categories:

Presence

Contacts and groups

Instant messaging

Conferencing

Telephony

External user support

Mobile access

Archiving and compliance

Enhanced Presence Support in Lync Server 2010 Clients

Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

Publish and

view status

● ● ● ●

View status

based on

calendar

free/busy

information

● ● ● ●

View status

notes and out-

of-office

messages

● ● ● ●

Add a custom

location

● ●

Add a custom

note

● ● ●

8


Contacts and Groups Support in Lync Server 2010 Clients

Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

View contact

list

● ● ● ● ●

Modify contact

list

● ● ● ● ●

Tag contacts ● ● ●

Control privacy

relationships

● ● ●

Search

corporate

address book

● ● ● ● ●

Search

Microsoft

Outlook

contacts

● ● ●

Manage

contact list

groups

● ● ●

Expand

distribution

groups

● ● ● ● ●

Search for

Response

Groups

● ● ●

Display recent

contacts group

● ● ●

Display current

conversations

group

● ● ● ●

9


Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

Display

alternate

contact views

(for example,

tile)

● ●

Instant Messaging (IM) Support in Lync Server 2010 Clients

Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

Initiate IM with

a contact

● ● ●

Navigate

among multiple

IM

conversations

● ● ●

Log IM

conversations

in Outlook

● ●

Initiate an ● ● ●

10


Feature/capability

Microsof

t Lync

2010

Microsof

t Lync

Web App

Microsof

t Lync

2010

Attendee

Microsoft

Lync

2010

Attendant

Microsof

t Lync

2010

Mobile

Microsof

t Lync

2010

Phone

Edition

Online

Meeting

Add-in

for

Microsof

t Lync

2010

Messenger

for Mac 7

email to a

contact

Use prepared

conversation

templates

●

Conferencing Support in Lync Server 2010 Clients

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Add computer

audio

● ● ● ● ●

Add video ● ●

Use in-meeting

presenter

controls

● ● ●

Access detailed

meeting roster

● ● ● ●

Participate in

multiparty IM

● ● ● ● ●

Share the

desktop (if

enabled)

● ●

(requires

plug-in)

●

Share an

application (if

enabled)

● ●

(requires

plug-in)

●

Add anonymous ● ● ●

11


Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

participants (if

enabled)

Use dial-in audio

conferencing

● ● ● ●

Initiate an

meeting

●

Add and present

PowerPoint files

● ●

Whiteboard ● ● ●

Polling ● ● ●

File sharing ● ● ●

Schedule a

meeting or

conference

●

Telephony Support in Lync Server 2010 Clients

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Initiate a voice call ● ● ● ●

Click to call a

contact

● ● ● ●

Manage call

forwarding

● ● ● ●

Manage team call

settings

● ●

Manage delegates ● ●

12


Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Initiate a call to a

Response Group

● ●

Emergency

services support

● ●

Connect to voice

mail

● ● ● ●

Make calls on

behalf of another

contact

(manager/delegate

scenario)

●

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Handle another's

calls if configured

as a delegate

● ● ● ●

Manage a high

volumes of calls

●

External User Support in Lync Server 2010 Clients

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Initiate IM with a

public contact

● ● ●

Initiate IM with a

federated

● ● ●

13


Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

contact

Conduct two-

party or

multiparty calls

with external

users

● ● ● ●

14


Mobile Access Support in Lync Server 2010 Clients

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Call from mobile

device using

work identity

(“Call via Work”)

●

Receive calls

dialed to work

number (single

number reach)

● ●

Publish mobile

presence tag

●

Archiving and Compliance Support in Lync Server 2010 Clients

Feature/capability

Microsoft

Lync 2010

Microsoft

Lync Web

App

Microsoft

Lync 2010

Attendee

Microsoft

Lync 2010

Attendant

Microsoft

Lync 2010

Mobile

Microsoft

Lync 2010

Phone

Edition

Online

Meeting

Add-in for

Microsoft

Lync 2010

Client-side

archiving

● ●

Client-side

recording

●

15



This section describes the hardware and software requirements for Microsoft Lync Server

2010 communications software clients.

Lync 2010 and Online Meeting Add-in for Microsoft Lync 2010 System Requirements

Lync Server 2010 Attendant System Requirements

Lync Web App Supported Platforms

Lync 2010 and Online Meeting Add-in for Microsoft Lync 2010 System Requirements

The following table contains the minimum hardware and software requirements for Microsoft Lync

2010 communications software and the Online Meeting Add-in for Microsoft Lync 2010.

For a complete list of compatible software and operating systems, see Lync 2010 Compatibility.

Hardware and Software Requirements for Lync 2010 and the Online Meeting Add-in for Lync 2010

System component Minimum requirement

Operating system Windows 7

Windows Vista

Windows XP Professional with Service Pack 3

(SP3). Windows Installer 3.1 must be installed

before deploying Lync 2010

Computer/processor Intel Pentium 4, AMD Athlon 64, or equivalent

Data and voice: 1.6 gigahertz (GHz) or higher

processor; 2 GHz 32-bit or 64-bit processor

recommended

Video: Dual Core 1.9 GHz processor or higher

for VGA; Quad Core 2.0 GHz or higher for high

definition

Microsoft RoundTable conferencing device: 2

GHz processor or higher

Display resolution 1024x768 required

Graphics hardware Support for Microsoft DirectX 9 application

programming interface

128 MB of graphics memory (minimum)

Windows Display Driver Model driver

Pixel Shader 2.0 in hardware

16



32 bits per pixel

Memory Windows XP: 1 gigabyte (GB) of RAM

Windows Vista or Windows 7: 2 gigabytes (GB)

of RAM

Telephony Microphone and speakers, headset with

microphone, or equivalent device

Recommended: Microsoft unified

communications (UC) device, or a phone

running Microsoft Lync 2010 Phone Edition.

Video source USB 2.0 video camera or RoundTable device.

Bandwidth requirements Voice:

Peer-to-peer: 40 kbps (minimum); 60 kbps

(typical); 90 kbps (maximum)

Conferencing: 40 kbps (minimum); 95 kbps


Media bypass: 80 kbps (minimum); 95 kbps


Video:

CIF: 50 kbps (minimum); 210 kbps (typical);

250 kbps (maximum)

VGA: 350 kbps (minimum); 500 kbps


High definition: 800 kbps (minimum); 1.2

Mbps (typical); 1.5 Mbps (maximum)

RoundTable device: 50 kbps (minimum);

280 kbps (typical); 350 kbps (maximum)

Data:

Web conferencing (PSOM): 20 kbps

(minimum); 200 kbps (typical); 500 kbps

(maximum)

File Transfer: 20 kbps (minimum); 200 kbps


Application Sharing: 256 kbps (minimum); 1

Mbps (typical); 3.5 Mbps (maximum)

Typical bandwidth values are measurements of

typical activity levels under good network

conditions (for example, with no forward error

17



correction, or FEC). This value can be used for

capacity planning to assess if a network is

provisioned appropriately. The values are

cumulative. For example, for a conference call

with audio, Common Intermediate Format (CIF)

video, and panoramic video, an appropriately

provisioned network would provide a bandwidth

speed of 585 Kbps (95+210+280=585 Kbps).

Installation and updates Administrative credentials, or, in Windows Vista

Standard User mode, administrator credentials.

Other requirements for Lync 2010

Microsoft Office Outlook 2010 and Microsoft Exchange Server 2010 are required for the full

set of new Outlook integration features. For details, see Lync 2010 Compatibility.

Microsoft Silverlight browser plug-inversion 4.0 is installed automatically during setup.

Other requirements for the Online Meeting Add-in for Lync 2010

The Online Meeting Add-in for Lync 2010 is supported with Microsoft Office 2003, Microsoft Office

2007, and Microsoft Office 2010.

Lync Server 2010 Attendant System Requirements

The following table summarizes the minimum software and hardware requirements for Microsoft

Lync 2010 Attendant communications software.

System Requirements for Lync Server 2010 Attendant


Display resolution Required: Super VGA 1024 x 768

Recommended: Super VGA 1280 x 1024 or

higher

Operating system Windows 7

Windows Vista

Windows XP Professional with Service Pack 3

(SP3)

Computer/processor Intel Pentium 4, AMD Athlon 64, or equivalent

Data and voice: 1 GHz or larger processor.

Support for 32-bit and 64-bit

Microsoft RoundTable conferencing device: 2

GHz processor or higher.

Memory Windows XP: 1 gigabyte (GB) of RAM

18



Windows Vista or Windows 7: 2 gigabytes (GB)

of RAM

Installation space At least 100 MB free

Video memory Microsoft DirectX 9-capable display adapter, ATI

Radeon X300 or NVIDIA GeForce 5600 class

equivalent or better with 256 MB of video

memory

Telephony Microphone and speakers, headset with

microphone, or equivalent device

Recommended: Microsoft unified

communications (UC) device, or a phone

running Microsoft Lync 2010 Phone Edition

Bandwidth requirements Voice: 50 kbps (minimum); 80 kbps (high-

quality)

The RoundTable device (audio): 50 kbps

(minimum); 350 kbps (high-quality)

Note:

The required and recommended

bandwidth speeds are cumulative. For

example, if you want to use voice and

the RoundTable device, the minimum

bandwidth would be 50+50=100 kbps.

Other requirements Microsoft Office Outlook 2010 and Microsoft

Exchange Server 2010 are required for the full

set of new Outlook integration features. For

details, see Lync 2010 Compatibility.

The Microsoft .NET Framework 3.5 must be

installed on your computer before you install

Lync 2010 Attendant. To download

Microsoft .NET Framework 3.5 from

http://go.microsoft.com/fwlink/?LinkId=122406.

Lync Web App Supported Platforms

To use Microsoft Lync Web App, you must have one of the following supported operating system

and browser combinations.

19

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


Notes:

Microsoft Silverlight browser plug-in version 4.0 must be installed on your computer.

Lync Web App is not supported on 64-bit browsers.

Operating System and Browser Requirements for Microsoft Lync Web App

Operating

system

Internet

Explorer 8

Internet

Explorer 7

Internet

Explorer 6 Firefox 3.X Safari 5.X Safari 4.X

Windows 7

(32-bit and

64-bit)

Yes Yes Yes

Windows

Vista Service

Pack 2 (SP2)

(32-bit and

64-bit)

Yes Yes Yes

Windows XP

SP3 (32-bit)

Yes Yes Yes Yes

Windows XP

SP2 (64-bit)

Yes Yes Yes Yes

Windows

Server 2008

R2

Yes Yes

Windows

Server 2003

(except IA-

64)

Yes Yes Yes

Windows

Server 2000

SP4

Yes Yes

Mac OS

10.4.8+ (Intel-

based)

Yes Yes

Key Client Policies and Settings

There are several essential policies and in-band provisioning settings that you should check and

reconfigure if necessary before you deploy Microsoft Lync Server 2010 communications software

clients.

20


Some of these policies are client bootstrapping policies that specify, for example, the default

servers and security mode that the client should use until sign-in is complete. Because these

policies take effect before the client signs in and begins receiving in-band provisioning settings

from the server, you can use Group Policy to configure them.

There are also some key client policies and in-band provisioning settings that can significantly

impact client functionality and should be configured before client deployment.

Group Policy for Client Bootstrapping

The client Group Policy settings listed in the following table must be configured before users sign

in to the server for the first time.

Group Policies Needed for Client Bootstrapping

Group Policy setting Description

ConfiguredServerCheckValues Specifies a list of server version names separated by semi-

colons that Microsoft Lync Server 2010 will log in to, in

addition to the server versions that are supported by default.

DisableHttpConnect During sign-in, Lync Server 2010 attempts to connect to the

server using Transport Layer Security (TLS) or Transmission

Control Protocol (TCP). If neither of these transport methods

is successful, Lync tries to connect using HTTP. Use this

policy to disable the fallback HTTP connection attempt.

DisableNTCredentials Requires the user to provide logon credentials for Lync rather

than automatically using the Windows credentials during sign-

on to a Session Initiation Protocol (SIP) server.

DisableServerCheck By default, Lync checks the server name and version before

signing in. Set this policy to 1 in order to bypass the version

check.

EnableSIPHighSecurityMode Helps enable Lync to send and receive instant messages

securely. This policy has no effect on Windows .NET or

Microsoft Exchange Server services.

If you do not configure this policy setting, Lync can use any

transport. But if it does not use TLS and if the server

authenticates users, Lync must use either NTLM or Kerberos

authentication.

EnableStrictDNSNaming Allows Lync to automatically detect and securely

communicate with SIP servers that have non-standard fully

qualified domain names (FQDNs).

HelpMenuText Specifies the text to display to the user in the Help menu for

the Help website.

HelpMenuURL Specifies which website to open when the user selects the

21


Group Policy setting Description

Help menu text item in the Help menu. Both HelpMenuText

and HelpMenuURL need to be specified in order for the Help

menu item to appear in Lync.

PreventRun Prevents users from running Lync. You can configure this

policy setting under both Computer Configuration and User

Configuration, but the policy setting under Computer

Configuration takes precedence.

SavePassword Enables Lync to store passwords.

ServerAddressExternal Specifies the server name or IP address used by federated

contacts when connecting from outside the external firewall.

Set this policy if you want to override the shared setting in

HK_CU\Software\Microsoft\Shared\UcClient\

ServerAddressInternal

ServerAddressInternal Specifies the server name or IP address used by Lync when

connecting from inside the organization’s firewall. Set this

policy if you want to override the shared setting in HK_CU\

Software\Microsoft\Shared\UcClient\ServerAddressInternal.

TourLaunchMode Controls the availability of the Lync Tour.

TourURL Provides an address for the Lync Tour. The address can point

to the local machine, or to an HTTP or HTTPS site in the

Windows Internet Explorer Local intranet or Trusted sites

security zones.

Transport Defines the network protocol used by Lync: TCP or TLS.

Client Version Policy

The default Client Version Policy requires that all clients to be running a minimum of Microsoft

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

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

devices from being unexpectedly blocked or updated when connecting to Lync Server 2010. You

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

override the default rule. Additionally, as cumulative updates are released, you should configure

the Client Version Policy to require the latest updates.

22


Key In-Band Settings

The in-band provisioning settings listed in the following table can significantly impact the user

experience and should be configured before client deployment.

Office Communications Server

2007 R2 Group Policy setting

Lync Server 2010 in-band

provisioning setting Description

Portrange\Enabled ucPortRangeEnabled Specifies whether the port

ranges sent by the server

should be used by the client

for media and signaling.

Used in conjunction with the

subvalues MaxMediaPort

and MinMediaPort.

Portrange\MaxMediaPort ucMaxMediaPort When combined with the

ucMinMediaPort, specifies

the range of ports used for

media. The recommended

minimum is 40 ports.

Portrange\MinMediaPort ucMinMediaPort When combined with the

ucMaxMediaPort, specifies

the range of ports used for

media. The recommended

minimum is 40 ports.

For details, see "Microsoft Office Communications Server 2007 R2 Group Policy Settings

Documentation" at http://go.microsoft.com/fwlink/?LinkID=140494 and "Group Policy for Unified

Communications Clients" at http://go.microsoft.com/fwlink/?LinkId=178987.

See Also

Migrating User Settings to Lync Server 2010


Microsoft Lync Server 2010 communications software includes two new tools you can use to

manage and configure your Lync Server 2010 deployment:

Lync Server 2010 Control Panel A web-based graphical user interface for managing and

configuring servers, users, clients, and devices.

Lync Server 2010 Management Shell A management interface with a rich set of Windows

PowerShell cmdlets and a number of pre-defined scripts.

This topic provides an overview of the client-related settings and policies you can configure with

these two management tools.

23


http://go.microsoft.com/fwlink/?LinkID=140494


Note:

A policy is applied to users or groups of users. A setting or configuration is applied to the

Lync Server 2010 environment as a whole.

For details, see the following:

Lync Server 2010 Control Panel documentation

Lync Server 2010 Management Shell documentation


Client Planning Steps during Migration

Lync Server 2010 Control Panel Overview

The following figure shows the Microsoft Lync Server 2010 Control Panel Home page. Help and

support options as well as common tasks are listed here.

Lync Server 2010 Control Panel Home page

The left navigation bar shows the groups available in Lync Server 2010 Control Panel.

Note:

This topic does not cover Topology and Network Configuration settings.

The following table summarizes the settings and policies available on each group in the left

navigation bar.

24


Overview of Lync Server 2010 Control Panel Settings and Policies

Group Client settings and policies

Users Search

Move user

Enable or disable users for Lync Server

SIP Address, registrar pool, telephony mode

PIN (set, lock, unlock)

User or group policies and settings

Topology (not discussed in this topic) Topology management (for details, see

Managing Computers in Your Topology in the

Operations documentation)

IM and Presence File transfer filtering

Hyperlinks in instant messages

Voice Routing Dial plan

Voice policies: forwarding, delegation, transfer,

park, simultaneous ring, team call, PSTN re-

route, bandwidth policy override, malicious call

trace

Trunk configuration, test voice routing, test

cases

Voice Features Call park extensions

Unassigned number routing

Response Groups Agent group, queue, and workflow configuration

Conferencing Conferencing policies and permissions:

meeting size, recordings, A/V, collaboration,

sharing

Default meeting options

Dial-in access number

Dial-in PIN policy

Clients Client version control

Device settings: update, test, log, configure

External User Access Federation, remote user access, public instant

messaging (IM) connectivity

Monitoring and Archiving Call detail recording

Quality of Experience (QoE) data

25


Group Client settings and policies

Archiving policy and configuration

Security Registrar authentication

Web services policies

Dial-in personal identification number (PIN)

policy

Network Configuration (not discussed in this

topic)

Includes bandwidth management and

emergency services settings (for details, see

Lync Server 2010 Control Panel

documentation)

The following sections list client-related Lync Server 2010 Control Panel settings and policies,

along with their Lync Server 2010 Management Shell (Windows PowerShell cmdlet) equivalents.

Users

The Lync Server 2010 Control Panel Users group contains the following options:

Enable or disable users for Lync Server 2010

Create new users, or modify existing ones

Move individual users or groups of users from one pool to another

Configure a user’s SIP address and registrar pool

Set the telephony mode: Enterprise Voice, PC-to-PC only, or Audio video disabled

For Enterprise Voice users, assign the Line URI, Dial plan policy, and Voice policy

Set, lock, or unlock a user’s PIN

Assign users or groups of users to policies defined in other Lync Server 2010 Control Panel

groups:

Conferencing

Client version

Security (PIN policy)

External access

Archiving

Location

Client and device policies

The User group is also very useful for user or client troubleshooting. You can view a complete list

of policies assigned to a given user, as well as the details of each policy. For details, see

Managing Users in the Operations documentation.

For details about managing users at the command line, see Get-CSUser, Set-CSUser, Enable-

CSUser, Disable-CSUser, and Move-CSUser in the Command-line Reference documentation.

26


IM and Presence

Use IM and Presence options to protect your organization from IM-based security risks. For

example, you can block instant messages containing hyperlinks with specific prefixes, or files with

specific extensions. For details, see Filtering Instant Messages and Client Versions in the

Operations documentation.

For details about managing IM and presence at the command line, see New-

CSFileTransferFilterConfiguration, and New-CSImFilterConfiguration in the Command-line

Reference documentation.

File Filter

File Transfer Filter Options

Option CsFileTransferFilterConfiguration parameter

Name Identity

Enable file filter Enabled

Block specific file types Action: Block

Block all Action: BlockAll

File type extension to block Extensions

URL Filter

URL Filter Options

Option CsImFilterConfiguration parameter

Name Identity

Enable URL filter Enabled

Block URLs with file type extension BlockFileExtension

Hyperlink prefix: Do not filter Action: Allow

Allow message AllowMessage

Hyperlink prefix: Block hyperlinks Action: Block

Hyperlink prefix: Send warning message Action: Warn

Exclude local intranet hyperlinks IgnoreLocal

Filter these hyperlink prefixes Prefixes

Warning message WarnMessage

27


Voice Routing

This section discusses the Voice Policy options available on the Voice Routing page. Other

options available on the Voice Routing page are Dial Plan, Route, PSTN Usage, Trunk

Configuration, and Test Voice Routing.

Voice Policy

When Enterprise Voice is enabled, use the Voice Routing page to define voice policy settings for

individuals or groups of users. For details, see Configuring Voice Policies, PSTN Usage Records,

and Voice Routes in the Deployment documentation.

For details about managing voice policy at the command line, see New-CSVoicePolicy in the

Command-line Reference documentation.

Voice Routing: Voice Policy Options

Option CSVoicePolicy parameter

Name Identity

Description Description

Enable call forwarding AllowCallForwarding

Enable delegation EnableDelegation

Enable call transfer EnableCallTransfer

Enable call park EnableCallPark

Allow simultaneous ringing of phones AllowSimulRing

Enable team call EnableTeamCall

Enable PSTN reroute AllowPSTNReRouting

Enable bandwidth policy override enableBWPolicyOverride

Enable malicious call tracing EnableMaliciousCallTracing

Associated PSTN Usages PstnUsages

Voice Features

Use the settings in Voice Features to define number ranges for the Call Park application and to

configure unassigned number routing. For details, see Configuring Incoming Call Handling

Features in the Deployment documentation.

For details about managing voice features at the command line, see New-CSCallParkOrbit and

New-CsUnassignedNumber in the Command-line reference documentation.

Voice Features: Call Park Options

Option CSCallParkOrbit parameter

Name Identity

28


Option CSCallParkOrbit parameter

Number range NumberRangeStart, NumberRangeEnd

FQDN of destination server CallParkServiceFQDN

Voice Features: Unassigned Number Options

Option CSUnassignedNumber parameter

Name Identity

Number range NumberRangeStart, NumberRangeEnd

Announcement service (ExchangeUM or

Announcement)

Not applicable

Exchange UM: Auto Attendant phone number ExUmAutoAttendantPhoneNumber

Announcement: FQDN of destination server AnnouncementService

Announcement: Announcement AnnouncementName

Response Groups

In Response Group, you have the Group, Queue, and Workflow options.

Note:

You must create groups and queues before you create a workflow that uses them.

Group

Use this Response Group page to define an agent group by using SIP URIs or distribution list

email aliases. For details, see Create an Agent Group in the Deployment documentation.

For details about managing group options at the command line, see New-CSRgsAgentGroup in

the Command-line reference documentation.

Response Group: Group Options

Option CsRgsAgentGroup parameter


Participation policy ParticipationPolicy

Alert time (seconds) AgentAlertTime

Routing method RoutingMethod

Agents: Define a custom group of agents AgentsByUri

Agents: use an existing email distribution list DistributionGroupAddress

29


Queue

Use this Response Group page to define the behavior of the queue where callers wait until an

agent can answer. For details, see Create a Queue in the Deployment documentation.

For details about managing queue options at the command line, see New-CSRgsQueue in the


Response Group: Queue Options

Option CSRgsQueue parameter

Name Identity


Groups AgentGroupID

Enable queue time-out TmeoutThreshold (non-Null value)

Timeout period Timeout Threshold

Call target TimeoutAction

Enable queue overflow OverflowThreshold (non-Null value)

Maximum number of calls OverflowThreshold

Forward the call OverflowCandidate

Call target OverflowAction

Workflow

A workflow defines the behavior of a call from the time the phone rings to the time somebody

answers the call. When you use the Response Group page to create a new workflow, the

Response Group Configuration Tool appears. For details about this tool, see Create a

Workflow in the Operations documentation.

Notes:

If you have more than 300 workflows in a single pool in your Response Group

deployment, it is better to use Lync Server 2010 Management Shell cmdlets to create the

workflows. If you use the Response Group Configuration Tool to create workflows for a

pool that has more than 300 workflows, the web page takes a long time to load.

For details about managing workflow options at the command line, see New-

CSRgsWorkflow in the Command-line Reference documentation.

Conferencing

Conferencing settings include Conferencing Policy, Meeting Configuration, Dial-in Access

Number and PIN Policy.

30


Note:

You can set conferencing bandwidth, networking, and storage options by using the Lync

Server 2010 Management Shell. For details, see CSConferencingPolicy and

CSConferencingConfiguration in the Command-line Reference documentation.

Conferencing Policy

Use the Conferencing Policy page to configure global, site, or user conferencing policies.

Conferencing policies define the default experience for scheduling meetings. For details, see

Managing On-Premises Meetings in the Operations documentation.

For details about managing conferencing policy options at the command line, see New-

CSConferencingPolicy in the Command-line Reference documentation.

Conferencing: Conferencing Policy Options

Option CSConferencingPolicy parameter

Name Identity

Maximum meeting size MaxMeetingSize

Allow participants to invite anonymous users AllowAnonymousParticipantsInMeetings

Recording (None or Enable) AllowConferenceRecording

Allow federated and anonymous participants to

record

AllowExternalUsersToRecordMeetings

Audio/video

Audio/video AllowIPAudio, AllowIPVideo

Enable PSTN conference dial-in EnableDialInConferencing

Allow anonymous users to dial out AllowAnonymousUsersToDialOut

Maximum video resolution allowed for

conferencing

MaxVideoConferenceResolution

Data Collaboration

Enable data collaboration EnableDataCollaboration

Allow federated and anonymous participants to

download content

AllowExternalsUsersToSaveContent

Allow participants to transfer files EnableFileTransfer

Enable annotations AllowAnnotations

Enable polls AllowPolls

Application Sharing

Enable application sharing AllowUserToScheduleMeetingsWithAppSharing

31


Option CSConferencingPolicy parameter

Allow participants to take control AllowParticpantControl

Allow federated and anonymous users to take

control

AllowExternalUserControl

Participant Policy

Disable application and desktop sharing EnableDesktopSharing: None

Enable application sharing EnableDesktopSharing: SingleApplication

Enable application and desktop sharing EnableDesktopSharing: Desktop

Enable peer-to-peer file transfer EnableP2PFileTransfer

Enable peer-to-peer recording EnableP2PRecording

Meeting Configuration

Use the Meeting Configuration page to modify the default meeting join experience. For details,

see Managing On-Premises Meetings in the Operations documentation.

For details about managing conferencing options at the command line, see New-

CSMeetingConfiguration in the Command-line Reference documentation.

Conferencing: Meeting Configuration Options

Option CSMeetingConfiguration parameter

Name Identity

PSTN callers bypass lobby PstnCallersBypassLobby

Designate as presenter (None, Company, or

Everyone)

DesignateAsPresenter

Assigned conference type by default AssignedConferenceTypeByDefault

Admit anonymous users by default AdmitAnonymousUsersByDefault

For details about managing meeting configuration options at the command line, see Set-

CSMeetingConfiguration in the Command-line Reference documentation.

PIN Policy

Use the PIN Policy page to define dial-in conferencing PIN policies. For details, see Configure a

Dial-in Conferencing Personal Identification Number (PIN) Policy in the Operations

documentation.

For details about managing dial-in conferencing PIN policy settings at the command line, see

New-CSPinPolicy in the Command-line Reference documentation.

32


Note:

For convenience, PIN Policy options can also be set in the Security tab.

Conferencing: PIN Policy Options

Option CSPinPolicy parameter

Name Identity


Minimum PIN length MinPasswordLength

Maximum logon attempts MaximumLogonAttempts

Enable PIN expiration PINLifetime (non-Null value

PIN expires after (days) PINLifetime

Allow common patterns AllowCommonParameters

External User Access

The External User Access group includes External Access Policy, Access Edge

Configuration, Federated Domains, and Provider. For details, see Managing External

Connectivity in the Operations documentation.

External Access Policy

Use the External Access Policy page to define a policy controlling communication with

federated, remote, and public users. For details, see Enable and Configure Remote User Access

in the Deployment documentation.

For details about managing external user access policy settings at the command line, see New-

CSExternalAccessPolicy in the Command-line Reference documentation.

External User Access: External Access Policy Options

Option CsExternalAccessPolicy Parameter

Name Identity


Enable communications with federated users EnableFederationAccess

Enable communications with remote users EnableOutsideAccess

Enable communications with public users EnablePublicCloudAccess

Enable video with public users EnablePublicCloudAudioVideoAccess

Access Edge Configuration

33


Use this Access Edge Configuration page to define access for federated and remote users, and

to enable anonymous access to conferences. For details, see Configure Access for Federated

Partners in the Deployment documentation.

For details about managing access edge configuration settings at the command line, see Set-

CSAccessEdgeConfiguration in the Command-line Reference documentation.

External User Access: Access Edge Configuration Options

Option CsAccessEdgeConfiguration parameter

Enable federation AllowFederatedUsers

Enable partner domain discovery EnablePartnerDiscovery

Send archiving disclaimer to federated partners EnableArchivingDisclaimer

Enable remote user access AllowOutsideUsers

Enable anonymous user access to conferences AllowAnonymousUsers

Federated Domains

Use the Federated Domains page to create or modify your list of allowed and blocked federated

domains. For details, see Monitor and Control Federated Partner Access in the Deployment

documentation.

For details about managing federated domains at the command line, see New-CSAllowedDomain

and New-CSBlockedDomain in the Command-line Reference documentation.

External User Access: Federated Allowed Domain Options

Option CsAllowedDomain parameter

Domain name (or FQDN) Domain

Access Edge service (FQDN) ProxyFqdn

Comment Comment

External User Access: Federated Blocked Domain Options

Option CsAllowedDomain parameter

Domain name (or FQDN) Domain

Comment Comment

34


Provider

Use the Provider page to create or modify policies controlling communications with public IM

providers such as AOL, Yahoo!, or MSN. You can also create policies for private hosting providers

(that is, providers who furnish IM, presence, and related services for a federated domain). For

details, see Configure IM Provider Support on Edge Servers in the Deployment documentation.

For details about managing providers at the command line, see New-CSPublicProvider and New-

CSHostingProvider in the Command-line Reference documentation.

External User Access: Edit Public or Hosted Provider Options

Option CsPublicProvider parameter

Enable communications with this provider Enabled

Provider name Name

Access Edge (FQDN) ProxyFqdn

Verification level: Allow communications only

with users verified by this provider

VerificationLevel: UseSourceVerification

Verification level: Allow communications only

with users on recipients’ contact lists

VerificationLevel: AlwaysUnverifiable

Verification level: Allow all communications with

this provider

VerificationLevel: AlwaysVerifiable

Clients

The Clients group includes policies for both clients and devices. Client Version Policy and

Client Version Configuration are discussed here. Device Updates, Test Devices, Device

Configuration, and Phone Configuration are also available.

For details, see Configuring Support for Clients and Devices in the Operations documentation

and Planning for Devices.

Client Version Policy

Use client version policies to specify which clients can be used in your organization. In Lync

Server 2010, you can also provide a download link to the most current version of the client

software.

Important:

The default client version policy enforces a minimum of Office Communicator 2007 R2

with the January 2010 cumulative update installed. If clients in your environment are

running earlier versions, you may need to reconfigure the Client Version rules to prevent

clients and devices from being unexpectedly blocked or updated when connecting to

Lync Server 2010. For details, see Client Planning Steps during Migration.

On the Client Version Policy page, you can modify existing policies or create new ones. A

number of pre-defined client version rules are provided, as shown in the following figure.

35


Client Version Policy: Edit Global page (detail)

When you add a new user agent or modify an existing one, the Client Version Policy page

shows the Create Client Version Rule options listed in the following table. For details, see

Specify the Client Versions Supported in Your Organization in the Lync Server 2010 Control Panel

documentation.

For details about managing client version policy settings at the command line, see New-

CSClientVersionPolicy and New-CSClientVersionPolicyRule in the Command-line Reference

documentation.

Clients: Client Version Policy Rule Options

Option CsClientVersionPolicyRule parameter

User agent UserAgent

Version Number Not applicable

Major version MajorVersion

Minor version MinorVersion

Build BuildNumber

Update QfeNumber

Comparison operation CompareOp

Action (Allow, Allow with URL, Block, Block with

URL)

Action

Action (OC user agent only): same as above,

plus Allow with upgrade and Block with

upgrade)

Action

URL ActionURL

36


Client Version Configuration

Use the Client Version Configuration page to define a default action for clients that do not

already have a version policy defined. For details, see Modify the Default Action for Clients Not

Explicitly Supported or Restricted in the Operations documentation.

For details about managing client version configuration settings at the command line, see New-

CSClientVersionConfiguration in the Command-line Reference documentation.

Clients: Client Version Configuration Options

Option CSClientVersionConfiguration parameter

Name Identity

Enable version control Enabled

Default action: Allow DefaultAction: Allow

Default action: Block DefaultAction: Block

Default action: Block with URL DefaultAction: BlockWithURL

URL DefaultURL

Monitoring and Archiving

Use Monitoring and Archiving to configure Call Detail Recording, Quality of Experience

Data, Archiving Policy, and Archiving Configuration options.

Note:

In Monitoring and Archiving, you configure server-side archiving. Client-side archiving

of instant messages and missed calls to the Outlook Conversation History folder is

controlled by using the Windows PowerShell cmdlet CSClientPolicy with the

EnableCallLogAutoArchiving and EnableIMAutoArchving parameters.

Call Detail Recording

Use the Call Detail Recording page to collect usage and diagnostic information about your

network message traffic. For details, see Configuring Call Detail Recording and Quality of

Experience Data Purging in the Operations documentation.

For details about managing call detail recording at the command line, see New-

CSCdrConfiguration in the Command-line Reference documentation.

Monitoring and Archiving: Call Detail Recording Options

Option CSCdrConfiguration parameter

Name Identity

Enable monitoring of call detail recordings

(CDRs)

EnableCDR

Enable purging of call detail recordings (CDRs) EnablePurging

37


Option CSCdrConfiguration parameter

Keep call detail data for maximum duration

(days)

KeepCallDetailForDays

Keep error report data for maximum duration

(days)

KeepErrorReportForDays

Quality of Experience Data

Use the Quality of Experience Data page to track media quality and the technical details of each

call or session. For details, see Configuring Call Detail Recording and Quality of Experience Data

Purging in the Operations documentation.

For details about managing QoE data at the command line, see New-CSQoEConfiguration in the


Monitoring and Archiving: Quality of Experience Data Options

Options CsQoEConfiguration parameter

Name Identity

Enable monitoring of Quality of Experience

(QoE) data

EnableQoE

Enable purging of Quality of Experience (QoE)

data

EnablePurging

Keep QoE data for maximum duration (days) KeepQoEDataForDays

Archiving Policy

Use the Archiving Policy page to control the server-side archiving of internal and external IM

sessions. For details, see Configuring the Global Policy for Archiving in the Deployment

documentation.

For details about managing archiving policy settings at the command line, see New-

CSArchivingPolicy in the Command-line Reference documentation.

Monitoring and Archiving: Archiving Policy Options

Option CSArchivingPolicy parameter

Name Identity


Archive internal communications ArchiveInternal

Archive external communications ArchiveExternal

Archiving Configuration

38


Use the Archiving Configuration page to control global or site-level archiving, content types,

and purging. For details, see Enabling or Disabling Archiving for Internal or External Users in the


For details about managing archiving configuration settings at the command line, see New-

CSArchivingConfiguration in the Command-line Reference documentation.

Monitoring and Archiving: Archiving Configuration Options

Option CSArchivingConfiguration parameter

Name Identity

Disable archiving EnableArchiving: None

Archive IM sessions EnableArchiving: IMOnly

Archive IM and web conferencing sessions EnableArchiving: IMAndWebConf

Block instant messaging (IM) or web

conferencing sessions if archiving fails

BlockOnArchiveFailure

Enable purging of archiving data EnablePurging

Purge exported archiving data and stored

archiving data after maximum duration (days)

KeepArchivingDataForDays

Purge exported archiving data only PurgeExportedArchivesOnly

Security

Use Security to configure registrar authentication, web service authentication, and dial-in

conferencing PIN policies.

Registrar Authentication

Use the Registrar Authentication page to modify the default authentication protocol issued by

registrars to clients. For details, see Configuring Authentication Settings and Personal

Identification Number (PIN) Policies in the Operations documentation.

For details about managing archiving configuration settings at the command line, see New-

CSProxyConfiguration in the Command-line Reference documentation.

Security: Registrar Authentication Options

Option CsProxyConfiguration parameter

Name Identity

Enable Kerberos authentication UseKerberosForClientToProxyAuth

Enable NTLM authentication UseNtlmForClientToProxyAuth

Enable certificate authentication UseCertificateForClientToProxyAuth

39


Web Service Authentication

Use the Web Service Authentication page to define web services authentication settings. For

details, see Configuring Authentication Settings and Personal Identification Number (PIN) Policies

in the Operations documentation.

For details about managing web service authentication settings at the command line, see New-

CSWebServiceConfiguration in the Command-line Reference documentation.

Security: Web Service Configuration Options

Option CSWebServiceConfiguration parameter

Name Identity

Windows authentication: Negotiate UseWindowsAuth: Negotiate

Windows authentication: NTLM UseWindowsAuth: NTLM

Windows authentication: None UseWindowsAuth: None

Enable PIN authentication UsePinAuth

Enable certificate authentication UseCertificateAuth

Enable certificate chain download EnableCertChainDownload

PIN Policy

Use the PIN Policy page to define dial-in conferencing PIN policies. For details, see Configure a

Dial-in Conferencing Personal Identification Number (PIN) Policy in the Operations

documentation.

For details about managing PIN policy settings at the command line, see New-CSPinPolicy in the


Note:

For convenience, you can also set PIN Policy options under Conferencing.

Security: PIN Policy Options

Option CSPinPolicy parameter

Name Identity


Minimum PIN length MinPasswordLength

Maximum logon attempts MaximumLogonAttempts

Enable PIN expiration PINLifetime (non-Null value

PIN expires after (days) PINLifetime

Allow common patterns AllowCommonParameters

40


Planning for Client Migration

This section outlines client-related considerations when planning a migration to Microsoft Lync

Server 2010 communications software. It discusses the user impact of migrating meetings and

the type of information that is migrated. Because a migration process often requires a period of

time during which various client versions coexist, this section also provides information about

planning for client compatibility and interoperability.


Migration Considerations for Meetings

Client Version Check



When planning for migration to Microsoft Lync Server 2010 communications software, you should

consider how clients will be affected during the various migration phases. To facilitate a smooth

transition, you need to consider how your users will be affected during the period of coexistence,

deploy the appropriate clients to maximize productivity, and ensure that user settings are properly

migrated or configured in the new environment.

This topic discusses important planning considerations for migration and outlines the

recommended client-related steps during the migration process.

Client Considerations for Migration

To help minimize the impact of migration on user productivity, include the following client-related

considerations during the migration planning phases.

Determine how Lync Server 2010 clients will interact with previous client versions, and with

installed versions of Microsoft Office and Microsoft Exchange Server. For details, see

Compatibility and Integration.

Review the user and client settings for the features that you want to support. Some settings,

for example Microsoft Lync 2010 enhanced privacy mode, cannot be enabled until every user

on a given server pool has the most current client versions installed. For details, see What's

New in Client Deployment, Migrating User Settings to Lync Server 2010, and Key Client

Policies and Settings.

If you are deploying conferencing, see Migration Considerations for Meetings.

Decide which clients to deploy. For details, see Deciding Which Clients To Deploy and Client

Comparison Tables.

To allow users who do not have Lync 2010 installed to participate in a Lync Server 2010

meeting, deploy Lync Web App, or deploy Microsoft Lync 2010 Attendee (or you can make

Lync 2010 Attendee available for download).

Client-Related Tasks during the Migration Process

41


The Migration documentation outlines the step-by-step process for migration. For details, see the

Migration documentation. Phases 2 and 9 of the migration process include specific steps for

migrating clients. These steps are summarized below.

During Phase 2: Prepare for Migration, do the following:

Deploy the most recent updates for Microsoft Office Live Meeting 2007, Microsoft Office

Communicator 2007, Microsoft Office Communicator 2007 R2, and Microsoft Office

Communications Server 2007 R2.

Use client version rules on your server running Office Communications Server 2007 R2 to

allow only clients with the most current updates to sign in, and to block Lync Server 2010

clients from signing in.

For details, see Phase 2: Prepare for Migration.

During the first part of Phase 9: Complete Post-Migration Tasks, before users have been migrated

to Lync Server 2010, do the following:

Use client version rules on your new Lync Server 2010 server to allow only clients with the

most current updates installed to sign in.

Configure Group Policy required for client bootstrapping.

Configure other user and client policies to specific users or groups of users by using Microsoft

Lync Server 2010 Control Panel, Windows PowerShell command-line interface, or both.

For details, see Phase 9: Complete Post-Migration Tasks.

At the end of Phase 9: Complete Post-Migration Tasks, after users have been migrated to Lync

Server 2010, do the following:

Confirm that the policies you created at the beginning of Phase 9 are assigned as required.

Deploy Lync Server 2010 clients.

(Optional) If your organization requires Lync 2010 enhanced presence privacy mode, after

migration is complete, define a Client Version Policy Rule to prevent earlier client versions

from signing in. Then, enable enhanced presence privacy mode.

Important:

Do not enable Lync 2010 enhanced presence privacy mode until every user on a

given server pool has the most current client versions installed. Lync 2010 privacy

settings are not honored by earlier client versions. If earlier clients are allowed to sign

in, a Lync 2010 user’s availability, contact information, or photo could be viewed by

someone who has not been authorized to do so. Additionally, a Lync 2010 user’s

privacy management options are reset if that user subsequently logs on with an

earlier version of the client.

You can configure both client version policy rules and enhanced privacy mode by using Windows

PowerShell. For details, see Set-CSClientVersionPolicy, Set-CSClientVersionPolicyRule, Set-

CSClientVersionConfiguration, and Set-CSPrivacyConfiguration in the Command-line Reference

documentation.

You can also configure client policy rules by using the Lync Server 2010 Control Panel. For

details, see Client Configuration Overview.

42


Migration Considerations for Meetings

The following topics are discussed in this section:

Changes to meetings in Microsoft Lync Server 2010

Migrating existing meetings and meeting content

Migrating users based on their conferencing needs

User experience during migration

Microsoft Lync 2010 communications software compatibility with meetings on earlier server

versions


Changes to Online Meetings in Lync Server 2010

In earlier versions of Office Communications Server, there are two types on meetings:

Conference calls (Lync 2010 client, conf:// URL prefix)

Web conferences (Live Meeting client, meet:// URL prefix)

In Microsoft Lync Server 2010, all newly-scheduled meetings use Lync 2010 as the primary client,

and have a URL prefix of https://.

During migration, Lync Server 2010 fully supports the earlier meeting types:

Previously scheduled conference calls and Live Meeting web conferences are moved to the

Lync Server 2010 server.

For users who have been migrated to the Lync Server 2010 server but do not have Lync 2010

installed, previous meeting types can still be modified or created.

For details, see the “User Experience During Migration” section later in this topic.

Default Lync Server 2010 Meeting Options

In earlier versions of Office Communications Server, meetings allowed anonymous users to

attend meetings by default. In Lync Server 2010, meeting access is set to “My company” by

default.

Lync Server 2010 Meeting Clients

You can use the following clients to join meetings scheduled through the Online Meeting Add-in

for Microsoft Lync 2010:

and Microsoft Office Communicator 2007 R2 (that is, only if the administrator has enabled

them. For details, see the “Configuring the Meeting Join Web Page” section later in this

topic.)

You cannot use the following clients to join meetings scheduled through the Online Meeting Add-

in for Lync 2010:

Communicator Web Access

Microsoft Office Live Meeting 2007

The Lync Web App or Lync 2010 Attendee are the recommended alternatives for users who do

not have Lync 2010 or Microsoft Lync 2010 Attendant installed.

Migrating Users Based on Their Conferencing Needs

43


Consider migrating frequent meeting organizers early in the process so that they can take

advantage of the new sharing, collaboration, and lobby management features of Lync Server

2010.

For users who need web conferencing features specific to Live Meeting—particularly support for

large meetings and break-out rooms—you have the following options:

Advise organizers to use Live Meeting service, if available in your organization.

Leave the organizers homed on the earlier version of Office Communications Server, so they

can continue to schedule server-based Live Meeting web conferences.

Migrating Existing Meetings and Meeting Content

When a user account is moved from Microsoft Office Communications Server 2007 R2 to a Lync

Server 2010 server, the following information moves along with the user account:

Meetings already scheduled by the user. This includes Communicator conference calls

(conf:// URL prefix) and Live Meeting conferences (meet:// URL prefix).

The user’s personal identification number (PIN). The user’s current PIN continues to

work until it expires or the user requests a new PIN.

The following information does not move to the new server:

Meeting content. You should advise meeting organizers to reload content into their

scheduled meetings after migration.

Notes:

When the Online Meeting Add-in for Lync 2010 is first used to schedule new meetings, a

new default conference identifier is created. The default conference identifier is the http

address and conference ID that is normally reused for all scheduled meetings.

This should only be an issue for organizers who memorize their conference identifier and

give it out to others. Most meeting attendees will join by clicking the join link in the new

meeting invitation, and previously scheduled Office Communications Server 2007 R2

meetings will continue to work.

User Experience During Migration

This section discusses the conferencing experience of users migrated to Lync Server 2010 both

before and after Lync 2010 is installed.

Before Lync 2010 Is Installed

After a user is migrated to the Lync Server 2010 server, but before new clients are installed, the

following Office Communications Server 2007 R2 client functionality continues to work on the new

server:

All scheduling functionality in the Conferencing Add-in for Microsoft Office Outlook

All meeting links in previously sent meeting invitations

Meet Now conferences in Office Communicator 2007 R2

Escalation to Live Meeting (Share Information Using Live Meeting) from Office Communicator

2007 R2

Dial-in conferencing numbers

44


Note:

Existing dial-in conferencing numbers work whether the meeting is hosted on Office

Communicator 2007 R2 server or a Lync Server 2010 server. However, the latest

Office Communicator 2007 R2 cumulative update is required on the Office

Communicator 2007 R2 server pools.

After Lync 2010 Is Installed

When a migrated user installs the Lync 2010, the Online Meeting Add-in for Lync 2010 is installed

too. This has the following effects:

All subsequently scheduled meetings use the new meeting format, which uses an https://

address instead of the legacy meet:// Live Meeting address.

For an existing meeting that is migrated to Lync Server 2010, the organizer can modify

meeting details, such as the meeting date or time, the presenter list, or meeting access.

However, the meeting automatically converts to the new meeting format and the join URL

changes to the new https://address. After the organizer makes changes, an updated meeting

invitation is sent to all participants.

Conferencing Add-in for Microsoft Office Outlook is removed, unless the user has configured

a Live Meeting service account. In this case, both add-ins coexist and the user can continue

to schedule Live Meeting service meetings using Conferencing Add-in for Microsoft Office

Outlook.

The following meeting functionality continues to work for users who have installed Lync 2010:

All meeting links in previously sent meeting invitations, including Communicator conference

calls (conf:// URL prefix) and Live Meeting conferences (meet:// URL prefix).

Audio conferencing information in previously sent meeting invitations, including meeting IDs.

Sharing functionality in Office Communicator 2007 R2 meetings.

Sharing functionality in peer-to-peer conversations or conferences that include Office

Communicator 2007 R2 users.

Note:

In previous versions of Office Communications Server, all users could initiate desktop

sharing in meetings. In Lync Server 2010 only meeting presenters can initiate

desktop sharing. In recurring meetings that are migrated to Lync Server 2010,

attendees can no longer initiate desktop sharing. If they need to do so, they must

have a meeting presenter promote them to presenter so that they can initiate desktop

sharing.

Meetings with Federated Organizations that Use Previous Clients

Users in federated organizations who are using Microsoft Office Communicator 2007 or Microsoft

Office Communicator 2005 clients cannot join Lync Server 2010 meetings in your organization if

those meetings are locked by the organizer. You need to reschedule these meetings in Lync

Server 2010 so that when federated participants join the meeting by using the new https://

meeting URL, they have the option of using either Lync 2010 Attendant or Lync Web App.

Lync 2010 Compatibility with Meetings on Earlier Versions of Office Communications Server

45


Users who have Lync 2010 installed can attend meetings hosted on earlier versions of Office

Communications Server, but the following considerations apply:

For Communicator meetings, new Lync 2010 features are not available

For Live Meeting web conferences, Lync 2010 users must also have the Live Meeting client

installed in order to attend. The email invitation contains instructions for installing the Live

Meeting client.


You can control the clients that are available for joining scheduled Lync Server 2010 meetings by

configuring the meeting join page. This page opens each time a user clicks a meeting link and

provides a way for users to join online meetings using an alternate client.

The meeting join page detects whether a client is already installed on the computer. It then starts

the default client and opens the meeting join web page, which contains links for alternate clients.

The scenarios are as follows:

If Lync 2010 is installed, Lync 2010 starts. The meeting join web page also appears, giving

the user the option to use Lync Web App.

If Lync 2010 is not installed and Lync 2010 Attendee is installed, Lync 2010 Attendee starts.

The meeting join web page also appears, giving the user the option to use Lync Web App.

If neither Lync 2010 nor Lync 2010 Attendee is installed, the meeting join web page appears

and gives the user the following options:

Use Lync Web App

Download Lync 2010 Attendee (this link is enabled by default)

Use a previous version of Communicator (this link is disabled by default)

For the scenario in which neither Lync 2010 nor Lync 2010 Attendee is installed, you can

configure the meeting join page in Microsoft Lync Server 2010 Control Panel (that is, under the

Security, Web Service settings). You can also configure these same settings by using the New-

CsWebServiceConfiguration or Set-CsWebServiceConfiguration Windows PowerShell

cmdlets with the ShowDownloadCommunicatorAttendeeLink and

ShowJoinUsingLegacyClientLink parameters.


The Client Version Check application provides you with a way to define a set of rules that specify

the version of clients that are supported in your Microsoft Lync Server 2010 environment. When

two clients of differing versions interact, the features that are available to either client can be

limited by the capabilities of the other released client. To make the greatest use of features

included in Microsoft Lync Server 2010 communications software and to improve the overall user

experience, you can use the Client Version Check to restrict the client versions that are used in

your Lync Server environment.


When a supported client logs on or is invited to a session, Client Version Check checks the SIP

User Agent header to determine the client version. Depending on the version of the client, and the

rules that you have configured, the Client Version Check application does one of the following:

46


Allows the client to log on to the pool (that is, the Allow option).

Allows the client to log on and receive updates from Windows Server Update Service or

Microsoft Update (that is, the Allow and Upgrade option). This action is available only when

Microsoft Lync 2010 is selected.

Allows the client to log on and presents the user with a message that indicates the user is can

upgrade their client. The message comes with the URL that you specify, and the user can

click on that URL to go to the page represented (that is, the Allow with URL option) and

upgrade their client.

Prevents the client from logging on to the pool (that is, the Block option).

Prevents the client from logging on and allows the client to receive updates from Windows

Server Update Service or Microsoft Update (that is, the Block and Upgrade option). This

action is available only when Microsoft Lync 2010 is selected.

Prevents the client from logging on and presents the user with a message that indicates the

user is using a client that is not supported. The message comes with the URL that you

specify, and the user can click on that URL to go to the page represented (that is, the Block

with URL option).

Each pool maintains a client version control list that you configure. This list contains rules that

specify the client versions you want to filter and the appropriate action for each client version. The

Client Version Check can act according to a specific client version number. It can also act

according to a client version that is less than or equal to or greater than or equal to the version

number that you specify. The Client Version Check also includes a configuration option that

specifies the default action for clients that are not included in the client version control list.

When you configure the Client Version Check, you specify the way in which clients are handled

during logon. The Client Version Check provides options for configuring the following:

User Agent header. This is the name of the agent for the client version.

Identity. This is the scope that the rule should be applied to. If multiple rules with different

levels of scope are triggered, the scope with the lowest level of granularity is applied. For

example, if a service level rules states that the client should be blocked, but a user level rule

also states that the client should be allowed, the client will be allowed as a user level rule is

the most granular.

Client version number. This includes the major version number, the minor version number,

the build number, and the QFE number. The number is presented in the following format:

<major version>.<minor version>.<build number>.<qfe number>.

Matching rules. These specify the comparison operations to perform to identify the specific

version or range of versions of the client to which the filtering action is to apply.

Action to take based on client version. Available values are Allow, Block, Allow with

URL, Block with URL, Allow and Upgrade, and Block and Upgrade.

Client download URL. This is used only for the Block with URL and Allow with URL

options.

47


A default list of rules is installed when you install Lync Server 2010. To customize the set up rules

for your deployment, you can edit an existing rule, or you can create a new rule. If you do not

want to block earlier version of the client, you will need to modify this list.

Note:

The default list of rules automatically blocks earlier versions of Microsoft Communicator

and Microsoft Communicator Phone Edition that try to connect to Lync Server 2010. If

you would like to change this behavior, you can create a new rule to allow earlier clients

to connect to the Lync Server 2010 server and then add this to the top of the list.

Although you can also edit the default the default rules to allow earlier clients to connect,

we do not recommend this approach.

Important:

The rules are listed in their order of precedence. For example, if you have a rule that

allows Communicator clients with a version 1.5 or later to connect, followed by a rule

blocking clients earlier than version 2.0, the first rule will match and thus takes

precedence. As a result, Communicator 1.5 clients can connect.

Client version checks in the version control list act on specific criteria. However, you also need to

configure a default rule to apply to clients that do not match any other client version rule,

specifying one of the following: Allow, Block, or Block with URL.


In Microsoft Lync Server 2010 communications software, most of the group policy settings used in

previous versions of Office Communications Server are now controlled by server-based, or in-

band provisioning, client policies.

This topic provides the information you need to successfully migrate user and client settings from

Microsoft Office Communications Server 2007 R2 to Lync Server 2010:

Obsolete or superseded Office Communicator 2007 R2 group policies

Lync Server 2010 in-band provisioning setting and Windows PowerShell command-line

interface cmdlet equivalents for Office Communicator 2007 R2 Group Policy settings

Selected new Lync Server 2010 user and client settings

Important:

Some Office Communications Server 2007 R2 Group Policy settings are still required for

client bootstrapping. For details, see Key Client Policies and Settings.

If you are migrating from Microsoft Office Communications Server 2007 to Lync Server 2010, see

"Group Policy for Unified Communications Clients" at http://go.microsoft.com/fwlink/?

LinkId=178987.

Obsolete Group Policies

The following table lists the Office Communicator 2007 R2 Group Policy settings that are either

obsolete or superseded in Lync Server 2010.

48




Obsolete Group Policies

Obsolete Group Policy Lync Server 2010 in-band

provisioning setting

Windows PowerShell cmdlet

AbsUseFallback None

DisablePC2PCVideo EnableP2PVideo Set-CSConferencingPolicy

DisableRCCForwarding AllowCallForwarding Set-CSVoicePolicy

EnableUPNP ucEnableSipSecurityMode

MaxAudioVideoBitRate AudioBitRate

VideoBitRate

ucMaxVideoRateAllowed

Set-CSConferencingPolicy

Set-CSMediaConfiguration

Configuring Clients by Using Windows PowerShell

In Lync Server 2010, client policies-except for those required for bootstrapping-are configured by

using Windows PowerShell cmdlets or the Lync Server Control Panel.

This section summarizes the Windows PowerShell cmdlets and parameters which correspond to

Office Communications Server 2007 R2 Group Policy settings.

CSClientPolicy

The majority of Group Policy settings from previous versions of Office Communications Server

can be configured by using the Windows PowerShell cmdlets New-CSClientPolicy or Set-

CSClientPolicy.

Most CSClientPolicy parameters have the same name as the equivalent Office Communications

Server 2007 R2 Group Policy. This overview section summarizes the renamed, unchanged, and

new policies that can be set by using CSClientPolicy.

Policies Renamed in Lync Server 2010


2007 R2 Group Policy


provisioning setting /


CallLogAutoArchivingPolicy EnableCallLogAutoArchiving Enable/disable

automatic archiving of

call logs to Microsoft

Outlook mailbox

IMAutoArchivingPolicy EnableIMAutoArchiving Enable/disable

automatic archiving of IM

conversations to Outlook

mailbox

MusicOnHoldAudioFile MusicOnHoldAudioFile Enable/disable ability for

49



2007 R2 Group Policy


provisioning setting /


the user to specify the

Music On Hold file.

MusicOnHoldDisabled EnableClientMusicOnHold Enable/disable Music On

Hold.

PC2PCASEncryption P2PAppSharingEncryption Enables or disables

application sharing

encryption in peer to

peer (2 user)

conversations.

SafeTransfer AttendantSafeTransfer Attendant - Safe

Transfer

The following table summarizes the unchanged policies that can be set by using

CSClientPolicy.

Unchanged Client Policy Names

Lync Server 2010 in-band provisioning setting /


BlockConversationFromFederatedContacts Block conversation from federated contacts

CalendarStatePublicationInterval Time interval to publish calendar data to

presence

CustomStateURL Custom presence states URL

DisableCalendarPresence Disable calendar presence

DisableEmailComparisonCheck Disable email comparison check for Outlook

public IM connectivity integration

DisableEmoticons Disable emoticons in instant messages

DisableFederatedPromptDisplayName Prevent showing the display name of federated

contacts in the notification dialog (does not

include contact who use public IM connectivity)

DisableFreeBusyInfo Disable publishing free/busy info

DisableHandsetOnLockedMachine Configure handset use on locked computer

DisableHTMLIM Prevent HTML text in instant messages

DisableInkIM Prevent Ink in instant messages

50




DisableMeetingSubjectAndLocation Disable publishing meeting subject and location

information

DisableOneNote12Integration Disable Microsoft OneNote 12 integration

DisableOnlineContextualSearch Disable online contextual search

DisablePhonePresence Disable call presence

DisablePICPromptDisplayName Prevent showing the display name of public IM

connectivity contacts in the notification dialog

DisablePresenceNote Disable presence note

DisableRTFIM Prevent rich text in instant messages

DisableSavingIM Prevent users from saving instant messages

EnableAppearOffline Enable the state Appear Offline

EnableEventLogging Turn on event logging for communicator

EnableFullScreenVideoPreviewDisabled Enables Full Screen Video and video preview

disabled for all Lync 2010 video calls

EnableSQMData Specify instrumentation

EnableTracing Turn on tracing for Lync 2010

EnableURL Allow hyperlinks in instant messages

51


The following table summarizes the new policies that can be set by using CSClientPolicy.

New Lync Server 2010 Client Policies



AbsUsage (in-band) / AddressBookAvailability

(Windows PowerShell)

Can be set to download the Address Book only,

use Address Book web search only, or use

both.

ConferenceIMIdleTimeout Indicates the number of minutes that a user can

remain in an instant messaging session without

either sending or receiving an instant message.

CustomizedHelpURL Replaces the default Lync 2010 help link with

the location of your organization-specific online

help. Use in conjunction with

EnableEnterpriseCustomizedHelp.

CustomLinkInErrorMessages URL for a web site that can be added to error

messages in Lync 2010.

DisableContactCardOrganizationTab Enables or disables the contact card

organization tab.

DisableFeedsTab Enables or disables the activity feeds tab.

DisablePoorDeviceWarnings Disables device warnings that appear

whenever a faulty or obsolete device is

detected.

DisablePoorNetworkWarnings Disables network quality warnings that may

appear during a conversation.

DisplayPhoto Determines whether or not photos (of both the

user and his or her contacts) are displayed.

DisplayPublishedPhotoDefault Sets the default for display of other contacts’

published photos. Can be overridden by users.

EnableContactSync Enables Lync 2010 to synchronize contacts

with Microsoft Exchange.

EnableDelegation Enables the call delegation. See also

EnableExchangeDelegationSync in this table.

EnableDiagnosticsLogsCollection Enables or disables the Collect Logs button,

which is used to collect logs for the

investigation of audio, video, or connectivity

issues. This feature allows the user to capture

52




the necessary logs and metrics and compress

them into a .cab file. The user then manually

uploads logs per the administrator’s

instructions, who sends the logs to Microsoft for

troubleshooting purposes.

EnableEnterpriseCustomizedHelp Allows you to replace the default Lync 2010

help link with the location of your organization-

specific online help. Use in conjunction with

CustomizedHelpURL.

EnableExchangeContactSync When enabled, Lync 2010 creates a

corresponding personal contact in Microsoft

Outlook for each person on a user’s contact list.

EnableExchangeDelegateSync When enabled, the client retrieves the

Exchange calendar delegates (users who have

authoring and editing rights on the manager’s

calendar) and uses these settings to update

delegates in Lync Server 2010. Use this setting

in conjunction with the EnableDelegation

setting, which is configurable in the CS-

VoicePolicy cmdlet or in Lync Server Control

Panel.

EnableHotdesking When enabled, a user can log on to a Lync

2010 Phone Edition phone in a shared

workspace using his or her Lync Server 2010

account.

EnableVOIPCallDefault When enabled, a Lync 2010 call is placed any

time a user employs the click-to-call feature.

AllowExchangeContactStore When enabled, a user’s contacts are stored on

Microsoft Exchange Server 2010 instead of

Lync Server 2010.

ExcludedContactFolders Indicates which Microsoft Outlook contact

folders (if any) should not be searched any time

Lync 2010 searches for new contacts.

HotdeskingTimeout Timeout interval for a user logged on to a

"hotdesked" phone.

MaximumDGsAllowedInContactList Indicates the maximum number of distribution

groups that a user can configure as a contact.

53




MaxPhotoSizeKB Set this policy to 0 to remove photos from Lync

2010 and disable the photo user interface.

Default: 10.

PhotoUsage Enable or disable display of photos.

PolicyEntry Provides a way to add settings not covered by

the default parameters.

SearchPrefixFlags Represents the Address Book attributes that

should be searched any time a user searches

for a new contact.

ShowManagePrivacyRelationships Enables or disables the Manage Privacy

Relationships option in the View by menu.

ShowRecentContacts Shows or hides the Recent Contacts option in

the Display Options menu.

ShowSharepointPhotoEditLink Controls whether users see the Edit in Mysite

selection in their My Picture options. Edit in

Mysite allows users to show a picture from

Microsoft SharePoint MySite.

For details, see the following topics:

Set-CSClientPolicy in the Command-line Reference documentation


Lync 2010 New Features in the Getting Started documentation

Additional Client Policies

The following table lists the Lync Server 2010 in-band provisioning settings and Windows

PowerShell cmdlets that are either not configurable through Windows PowerShell or configured

by using a Windows PowerShell cmdlet other than CSClientPolicy. Many of these settings

correspond to Communications Server 2007 R2 Group Policy settings and have been renamed in

Lync Server 2010.

Communications Server 2007 R2 Group Policy Equivalents

Office Communications

Server 2007 R2 Group

Policy setting

Lync Server 2010 in-

band provisioning

setting Windows PowerShell cmdlet Cmdlet parameters

AbsInsideURL AbsExternalServ

erUrl

None

AbsOutsideURL AbsInternalServe None

54



Server 2007 R2 Group

Policy setting

Lync Server 2010 in-

band provisioning

setting Windows PowerShell cmdlet Cmdlet parameters

rUrl

EnableDelegation

Portrange\

MaxMediaPort

ucMaxMediaPort TBD

Portrange\

MinMediaPort

ucMinMediaPort TBD

Portrange\Enabled ucPortRangeEna

bled

TBD

DisableApplicationSh

aringControl

AllowParticipantC

ontrol

CSConferencingPolicy AllowExternalUserContro

l

DisableDataConferen

cing

EnableDataColla

boration

CSConferencingPolicy EnableDataCollaboration

DisableAVConferenci

ng

AllowIPAudio,

AllowIPVideo

CSConferencingPolicy;

CS-User

AllowIPAudio,

AllowIPVideo;

AudioVideoDisabled

DisableFileTransfer AllowFileTransfer CSFileTransferFilterConfi

guration

(Communicator)CSConfe

rencingPolicy (Web

conferencing)

--

IMWarning IMWarning CSIMFilterConfiguration WarnMessage

MRASServerURI mrasURI TBD

PC2PCAVEncryption ucPC2PCAVEncr

yption

CSMediaConfiguration EncryptionLevel

msRTCLine line CSUser LineURI

TelephonyMode TelephonyMode CSUser UCEnabled,

RemoteCallControlTelep

honyEnabled

ExUMEnabled ExUMEnabled CSUser MCSVoiceMail

DisableSimultaneous

Ringing

AllowSimultaneo

usRinging

CSVoicePolicy AllowSimulRing

VoicemailURI VoicemailURI TBD

55


Planning for DevicesMicrosoft Lync Server 2010 communications software offers a comprehensive and integrated set

of tools for deploying and managing supported unified communication (UC) devices and expands

the line of available UC devices to include a new line of IP phones.

Devices in Lync Server

What's New for Devices

Choosing New Devices

Planning to Deploy Devices

Planning to Manage and Troubleshoot Devices

Common Area Phone Configuration

Analog Gateway and Device Configuration

Devices in Lync Server

This topic covers what device means in a Microsoft Lync Server 2010 communications software

environment, the types of phones this release supports, and the key device-related tools.

Definition of “Device”

In Lync Server 2010, device can refer to any unified communication (UC) device, including

headsets and webcams, but the primary UC device that is discussed in this chapter is the phone.

Phones running Microsoft Lync 2010 Phone Edition allow users to interact with the Lync Server

2010 communication and collaboration features. They provide basic and advanced phone

features, including new voice features such as Enhanced 9-1-1 (E9-1-1) and the Call Park

application, as well as voice connections to Microsoft Lync 2010 and Live Meeting sessions. Lync

Server 2010 supports IP, USB, and analog devices.

Notes:

Support for analog devices is new for this release. For details, see What's New for

Devices.

For details about the new voice features, see New Enterprise Voice Features in the

Getting Started documentation.

Types of UC Phones

Lync Server 2010 supports three types of phones:

Desk phones are handset IP, USB, or analog phones that are designed to be used by

employees at their desk. Desk phones are also known as information worker or knowledge

worker phones.

Conferencing devices are hands-free IP or USB phones that are designed to be used in

meeting rooms.

56


Common area phones are handset IP phones that are designed to be used in shared areas

—such as lobbies, kitchens, factory floors, and shared workspaces—and that can be

customized to provide different sets of Lync Server features.

For details about all three phone types, see Choosing New Devices.

Note:

Support for analog phones, the IP conferencing device, and common area phones is new

for this release. There is also a newly released IP desk phone. For information about all

the new phones, see What's New for Devices.

Tools for Managing Devices

When you use devices with Lync Server 2010, your primary tools will be any of the following:

Lync Server Control Panel, the new web-based user interface (UI) for Lync Server features.

For devices, use the Control Panel to prepare to deploy phones, manage the Device Update

service (that is, to deploy new versions of software to IP phones), and modify phone-related

settings, policies, and plans.

Lync Server 2010 Management Shell, the command-line tools for Lync Server features. For

devices, use the Shell to prepare to deploy UC phones and to manage them.

Gateway Management Console, for preparing to use analog devices with Lync Server. Use

this console to configure analog gateways to enable analog devices to make and receive

calls by using Lync Server 2010.

IP Phone Inventory Report, for monitoring IP phones. Use this tool to monitor usage and to

generate usage and inventory reports for the IP phones in your organization. For details, see

the “Improved Monitoring Capability” section in What's New for Devices.

What's New for Devices

The updated infrastructure in Microsoft Lync Server 2010 communications software includes new

features and capabilities that can potentially reduce your total cost of ownership (TCO) and

improve your experience and the experience of your users. When using devices, you’ll notice

support for new devices and new and improved management and troubleshooting tools.

New Line of IP Phones

Lync Server 2010 introduces support for five new IP phones. Compared to the previously

released IP phones, the new phones are:

More versatile. For the first time, unified communication (UC) phones designed for

common-area use and IP phones for conference rooms are available.

Less expensive. The new IP phones can be sold at a lower price point because they do not

include fingerprint readers and touch screens, and the new conferencing device does not

include cameras.

Easier to use. Features that contribute to improved ease of use include faster Internet

speeds; sharper resolution; personal identification number (PIN) authentication so that users

do not need to enter domain credentials for basic usage; and UI improvements, such as a

calendar from which you can join a meeting with one click.

57


The new phones are built by Aastra and Polycom and include two desk phones, two common

area phones, and a conferencing device.

For details about the new IP phones, see Choosing New Devices.

Support for Analog Devices

For the first time, Lync Server 2010 provides support for analog devices. Specifically, the

supported analog devices are analog audio phone and analog fax machines. In order to support

other types of analog devices such as a pager, modem, or Teletypewriting Device for the

Deaf/Teletypewriter (TTD/TTY), the customer needs to contact the qualified gateway vendor to

ensure that the specific device is supported on the gateway.

Now you can configure the analog gateways and devices in your organization to use Lync Server

2010. After you do this, analog devices use Lync Server to make and receive calls, and Lync

Server makes routing decisions and log calls in call detail records (CDRs) for analog devices, just

as it does for any device.

Note:

Analog phones that use Lync Server 2010 can make and receive calls like IP and USB

phones that use Lync Server with one exception: they cannot park calls using by the Call

Park application. They can, however, retrieve parked calls by dialing a call-retrieve

number.

For details how to configure analog gateways and devices, see Analog Gateway and Device

Configuration.

New Peripherals

Multiple vendors are working on providing new peripherals for use with Lync Server 2010. All

supported devices, including peripherals, are listed at Phones and Devices Optimized for

Microsoft Office Communicator, at the TechNet website. This list is updated as new devices are

approved.

Improved Management Experience

In Lync Server 2010, your deployment and management tasks should be more consistent,

efficient, and simple, because of the following changes:

Microsoft Lync Server 2010 Control Panel is Web-based and has a consistent and

streamlined user interface. For details, see Tools and Services for Managing and

Troubleshooting Devices.

The Lync Server 2010 Management Shell is the primary scripting interface and allows you to

do everything you can do in Lync Server 2010 Control Panel, as well as some unique tasks,

at the command prompt. For details, see Tools and Services for Managing and

Troubleshooting Devices.

is the new configuration data store, replacing WMI and providing a schematized, simpler way

of storing and sending configuration and topography.

Improved Monitoring Capability

Lync Server 2010 provides a simple mechanism for tracking and reporting on the IP phones that

are currently deployed in your organization. The new IP Phone Inventory Report tool is provided

58

http://technet.microsoft.com/en-us/office/ocs/bb970310.aspx



with the Monitoring Server Reports, as show in figure 1 (<Figure 1 to come.>), for device asset

tracking and monitoring. CDR captures device information—manufacturer, hardware version,

MAC address, user alias, and software version—based on registration activities. The IP Phone

Inventory tool lets you use CDR information to track:

Manufacturing and hardware versions so that you can see what devices are in deployment.

Software versions, which is useful to look at after deploying a new update, as it lets you

identify which devices have been successfully updated and which devices are still running

older builds. You can use this information to identify devices that may be having issues with

upgrading.

Misplaced devices, by running a report based on the user alias and MAC address of the

misplaced device so that you can find out if the device is being used on the network.

Usage, to find out when a user last logged in to a device.

General device inventory, to determine the number of devices currently deployed and identify

all device owners.

In addition, the improved user interface gives users more information about issues and possible

solutions.

Improved Troubleshooting Tools

This release includes new troubleshooting tools and improvements to logging. Device logs now

include more information, and the logging level can be adjusted—to low, medium, or high—to

allow you to get the right level of information when troubleshooting. The new troubleshooting tools

are Synthetic Transitions, power-on self test (POST), and Factory and Hard Reset.

For more information, see Tools and Services for Managing and Troubleshooting Devices and

Monitoring and Troubleshooting Devices.

Choosing New Devices

We recommend deploying only qualified unified communication (UC) devices that display the

"Optimized for Microsoft Office Communicator" wordmark. For a list of recommended devices,

see "Phones and Devices Optimized for Microsoft Office Communicator" at

http://go.microsoft.com/fwlink/?linkid=149031, and note that while this list does not yet include the

new line of IP phones, these phones are optimized for Microsoft Lync 2010 communications

software. The new line includes the Aastra 6725ip and 6721ip and the Polycom CX600, CX500,

and CX3000, all of which are described in this topic.

Note:

The new IP phones are not yet released to the public.

To select the devices that are right for your organization, consider what capabilities you want to

give users and how each device’s requirements affect your total cost of ownership (TCO).

Features and Functionality of UC Devices

After you determine and prioritize the capabilities that you want to provide users, try to find a

device that provides all the capabilities that are most important to you, and then evaluate whether

the requirements of that device support or detract from your TCO.

59



Desk Phones

In Microsoft Lync Server 2010, you have three options for IP desk phones and one USB phone

option. IP phones provide a broader set of UC features and do not need to be connected to a

computer that is running Lync 2010 to provide communication and collaboration features. USB

phones require this connection.

The supported IP desk phones are the new Aastra 6725ip, the new Polycom CX600, and the

Polycom CX700. The supported USB desk phone is the Polycom CX300.

Some desk phones provide large touch screens and/or fingerprint readers. All supported desk

phones provide the following:

Headset, speakerphone, mute, and volume-control buttons

In-call, voice-message, call-forwarding, and multi-color presence indicators

Wideband audio, full-duplex speakerphone, automatic gain control, dynamic noise reduction,

and acoustic echo cancellation

A two-port switch

For a summary of the key details about supported desk phones, see Desk Phone Comparison

Table. For updates related to Lync Server 2010 and details about the new phones, see the

Polycom website at http://polycom.com/ and the Aastra website at http://www.aastra.com. For

details, see the "Polycom CX700 data sheet" at

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/

communicator_cx700_datasheet.pdf and the "Polycom CX300 data sheet"

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/cx300-

datasheet.pdf.

Conferencing Devices

The supported conferencing devices are the Polycom CX5000, which replaced the discontinued

Microsoft RoundTable conferencing device, and the Polycom CX3000, the new IP conferencing

device.

The previously released Polycom CX5000 enables users in two or more locations to interact by

using concurrent video and audio transmissions. It uses an array of five cameras and six

microphones to capture 360-degree audio and video in your meeting and share it with remote

conference participants who connect to the conference by using Lync 2010 or Live Meeting. The

capabilities and requirements of the Polycom CX5000 and RoundTable device are identical. For

complete details about the Polycom CX5000’s capabilities and information about requirements,

see the "Polycom CX5000 data sheet" at

http://www.polycom.com/global/documents/products/voice/conferencing_solutions/

cx5000_datasheet.pdf.

The new IP conferencing device, the Polycom CX3000, provides all the audio features of the

Polycom CX5000 and Microsoft RoundTable conferencing device without the video support.

Unlike the Polycom CX5000 and RoundTable devices, the Polycom CX3000 does not require a

USB connection to a computer that is running Lync 2010 in order to provide telephony

functionality. Additionally, the Polycom CX3000 provides wideband audio, whereas the Polycom

CX5000 and RoundTable devices provide narrowband audio. Complete details about the

Polycom CX3000 are not currently documented.

60

http://www.polycom.com/global/documents/products/voice/conferencing_solutions/cx5000_datasheet.pdf

http://www.polycom.com/global/documents/products/voice/conferencing_solutions/cx5000_datasheet.pdf

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/cx300-datasheet.pdf

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/cx300-datasheet.pdf

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/communicator_cx700_datasheet.pdf

http://www.polycom.com/global/documents/support/sales_marketing/products/voice/communicator_cx700_datasheet.pdf

http://www.aastra.com/

http://polycom.com/


For a summary of the key details about supported conferencing devices, see the Common Area

Phone and Conferencing Device Comparison table.

When deciding which conferencing device to buy, decide how important it is that your

organization invest in full conferencing-device capabilities. You might also look at the supported

speaker phones, to see if one meets your conferencing needs. To learn about supported speaker

phones, see Phones and Devices Optimized for Microsoft Office Communicator. Note that this list

may not yet include all of the new devices.

Common Area Phones

You have two options for common area phones, the new Aastra 6721ip and the new Polycom

CX500. The Polycom CX3000 is another variant common area phone. All of the common area

phones are IP phones, so they do not need to be connected to a computer to provide Lync Server

2010 UC functionality. To provide this functionality, you can configure the phone as a hot-desk

phone, that is, a shared phone that allows users full desk-phone functionality. When a common

area phone is configured as a hot-desk phone, it allows users to log into their own user accounts;

when they do, the features, policies, and settings that are associated with the user account will

apply for as long as the user is logged in. When the user logs out, the phone provides basic

common area phone usage. (Most often, you will configure phones in shared workspace as hot-

desk phones. If the common area phone is in a lobby or kitchen or on factory floor, you’ll probably

configure it to have a dedicated user account only.)

Common area phones can be configured to provide the same software features as IP desk

phones. The differences between common area phones and IP desk phones are in the hardware.

For example, common area phones have only one Ethernet port, because they don’t need to

connect to a computer and don’t provide click-to-call integration; they also don’t have speakers.

For key details about the supported common area phones, see Common Area Phone and

Conferencing Device Comparison Table.

When deciding which common area phone to buy, consider contacting the manufacturers, after

the phones’ release, to find out and then to compare details about audio performance and the

warranty, level of support, and pricing-including shipping costs. (For contact information, see the

Polycom website at http://www.polycom.com and the Aastra website at http://www.aastra.com.)

You might also look at the supported desk phones, to see if one meets your common area calling

needs. To learn about supported desk phones, see Desk Phone Comparison Table.

Peripherals

To compare the capabilities of all supported UC peripherals (that is, speakerphones, handsets,

headsets, and webcams), see "Phones and Devices Optimized for Microsoft Office

Communicator" at http://go.microsoft.com/fwlink/?linkid=149031. This list is updated as new

devices are approved.

In addition, a basic headset, with high-quality audio, is available through Plantronics and available

only through direct sales.

61



http://www.polycom.com/



Tip:

If you’re looking for headsets to use with USB phones, choose an analog headset (RJ-22

connector) instead of a USB headset. USB peripherals and USB phones shouldn’t be

used together.

Computers

To learn about computers that provide integrated, high-quality audio and video capabilities and

display the “Optimized for Microsoft Office Communicator” watermark, see "Phones and Devices

Optimized for Microsoft Office Communicator" at http://go.microsoft.com/fwlink/?linkid=149031.

Desk Phone Comparison Table

This topic compares the new IP desk phones, the older IP desk phone, and the USB desk phone.

For a comparison of common area phones and conferencing devices, see Common Area Phone

and Conferencing Device Comparison Table.

Feature

Aastra 6725ip*

Polycom CX600* Polycom CX700 Polycom CX300

Connection type IP IP USB

Display size 3.5-inch QVGA 5.75-inch color

QVGA

Two-line monochrome

Screen resolution 320x240 24-bit pixels 320x240 18-bit

pixels

256x48 pixels

Touch screen No Yes No

Fingerprint reader No Yes No

Navigation Two-way up-down

navigation, with

Select, Home, and

Previous buttons

Three soft keys under

LCD

Scroll wheel up-

down navigation

Menu bar (touch)

Scroll bar (touch)

N/A

Help Available from a menu

option

Available from a

Help button

Not available

Text input Numbers only, on a

3x4 numeric keypad

Dial pad for search

(T9)

Full on-screen

keyboard

Dial pad for search

(T9)

Numbers only, on a

4x3 numeric keypad

Audio processing Digital signal

processing (DSP) on

No DSP on chip N/A

62



Feature

Aastra 6725ip*

Polycom CX600* Polycom CX700 Polycom CX300

chip

Internet connection 1000/100/10 Mbps 10/100 Mbps N/A

Authentication method PIN on device

NTLM or Kerberos,

when the device is

connected to a

computer

NTLM or Kerberos N/A

In-call indication LED indicator, on-

screen display

On-screen display On-screen display

*New for Microsoft Lync Server 2010 and not yet released to the public.

When choosing between the Aastra 6725ip and Polycom CX600 you may want to compare the

audio performance and the terms of the warranty, levels of support, and prices that the different

manufacturers provide. After the phones release, contact the manufacturers to obtain these

details and for purchasing information. For contact information, see the Aastra website at

http://www.aastra.com and the Polycom website at http://www.polycom.com.

Common Area Phone and Conferencing Device Comparison Table

This topic compares the new common area phones, the new conferencing device, and the older

conferencing devices.

For a comparison of desktop phones, see Desk Phone Comparison Table.

Feature

Aastra 6721ip*

Polycom CX500* Polycom CX3000*

Polycom CX5000

Microsoft RoundTable

conferencing device

For use in Common area Conference rooms Conference rooms

Connection type IP IP USB to computer, for

in-room audio and

video

IP, for device updates

PSTN, for telephony

Display size 3.5-inch color QVGA 3.5-inch color QVGA High-resolution backlit

graphical LCD

Handset Yes No No

Speakerphone No Yes Yes

63




Feature

Aastra 6721ip*

Polycom CX500* Polycom CX3000*

Polycom CX5000

Microsoft RoundTable

conferencing device

Cameras No No Yes (five)

Hands-free

microphones

No Yes (This information is

currently not

documented.)

Yes (six, two of which

are satellite)

Navigation Two-way navigation

keys

Three LCD softkeys

Menu, Select, Home,

and Back keys

Two-way navigation

keys

Three LCD softkeys

Menu, Select, Home,

and Back keys

Touch screen

information navigation

and delete key

Text input Full numerical

keypad (0-9, #,*)

Full numerical keypad

(0-9, #,*)

12-key touch-screen

telephone keypad

Audio Wideband Wideband Narrowband

Authentication method PIN on device PIN on device

NTLM or Kerberos,

when the device is

connected to a

computer

N/A

Indicators In-call LED

Mute

In-call LED

Presence

Mute

Device status icons

Ports No USB

One Ethernet 10/100

One USB Type B

One Ethernet 10/100

Two USB

PoE support Yes Yes No

*New for Microsoft Lync Server 2010 and not yet released to the public.

Note:

All of the phones provide on-device Help.

When choosing between the Aastra 6721ip and Polycom CX500, you may want to compare the

audio performance and the terms of the warranty, levels of support, and prices that the different

manufacturers provide. After the phones release, contact the manufacturers to obtain these

details and for purchasing information. For contact information, see the Aastra website at

http://www.aastra.com and the Polycom website at http://www.polycom.com.

64




Planning to Deploy Devices

This section helps you prepare to deploy IP and USB phones and to use analog devices with

Microsoft Lync Server 2010 communications software by describing requirements and the

deployment process.

Supported Topologies for Devices

Required Lync Server 2010 Components for Devices

System and Infrastructure Requirements for Devices

Deployment Guidelines and Process for Devices

Supported Topologies for Devices

To deploy devices, your topology must be set up for Enterprise Voice. If Enterprise Voice is not

currently deployed in your organization, we recommend that you use the Microsoft Lync Server

2010, Planning Tool to set up your topology for Enterprise Voice.

If you want to allow external access for devices, including the ability to use the Device Update

service from an IP phone outside of the firewall, you must also deploy Edge servers. To learn

about how to set up your topology for external user access, see Topologies for External User

Access in the Planning for External User Access documentation.

Note:

Analog devices will not appear in Topology Builder.

See Also

Updating Devices

Required Lync Server 2010 Components for Devices

Before you deploy unified communications (UC) phones, ensure that the following required

Microsoft Lync Server 2010 communications software components are in place.

Web Services

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

with Web Services, on the Front End Server. To check whether Web Services has been started or

to start Web Services, see Start or Stop Lync Server 2010 Services in the Operations

documentation.

Important:

In Lync Server 2010 Enterprise Edition, you may have multiple servers in the pool. For

each instance of Web Services running on servers in a pool, there is a separate instance

of Device Update service running in the pool. When you make a configuration change to

the Device Update service, the changes are propagated to all the servers in that pool but

not to servers in any other pool. For details about required configurations, see System

and Infrastructure Requirements for Devices.

65


Enterprise Voice

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

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

presence information or location information for contacts in your organization’s address book.

Enterprise Voice must be enabled for each device user. To check whether Enterprise Voice is

enabled for a user, in Microsoft Lync Server 2010 Control Panel find the user, then view the

user’s details. If the user is enabled for Enterprise Voice, the check box Enabled for Lync Server

will be selected, and the Telephony drop down will have Enterprise Voice selected.

Contact Objects

(Applies to Common area phones and analog devices only) Phones that are not associated

with a specific user must be associated with an Active Directory contact object. Like user

accounts, contact objects can be assigned policies and voice plans, thereby giving you a way to

manage the device.

For details about creating contact objects for common area phones and analog devices, see

Common Area Phone Configuration and Analog Gateway and Device Configuration.

Important:

When you create a contact object for an analog device (for example, when you use the

New-CSAnalogDevice command), make sure that you correctly specify the correct

categorization of the analog device. This needs to be a fax machine, such as fax,

modem, TTY or not (in other words, a voice device). The correct designation of fax affects

how the call will be routed.

Dial Plans, Voice Polices, and Outbound Call Routes

Dial plans, voice polices, and call routes must be set up for users. Dial plans are named sets of

normalization rules that translate phone numbers for a named location, individual user, or contact

object into a single standard (E.164) format, allowing UC device users to make calls to the public

switched telephone network (PSTN). Voice policies are records that define call permissions for

users, sites, or an entire organization and include various calling features that may be enabled or

disabled as appropriate. Voice policies must be set up for device users. Call routes are rules that

specify how Lync Server 2010 handles outbound calls from UC devices.

To verify whether dial plans, voice polices, and call routes are set up for users, or to set up or

modify these user polices, see Planning Outbound Call Routing in the Planning for Enterprise

Voice documentation. For details about configuring polices for common area phones or analog

devices, see Common Area Phone Configuration and Analog Gateway and Device Configuration.

Important:

We recommend that you also configure Exchange Unified Messaging (UM) and Lync

Server 2010 to work together and that you enable users for Exchange UM call answering

and Outlook Voice Access. For more information, see the Exchange Server 2010 product

documentation at http://go.microsoft.com/fwlink/?linkid=186202.

66



PIN Authentication and Policy

If you’re deploying phones from the new line of IP phones, you must enable personal

identification number (PIN) authentication on Lync Server, and an appropriate PIN policy need to

be in place. This allows authentication to be automatic when a user signs in on an Aastra 6721ip,

Polycom CX600, Polycom CX500, or Polycom CX3000 phone. You set the PIN policy on the PIN

Policy page of the Security group in Lync Server 2010 Control Panel. Also in Security, click

Web Service, and verify that PIN authentication is enabled in the Global policy.

System and Infrastructure Requirements for Devices

This section describes the hardware, port, Domain Name System (DNS), DHCP, and security

configurations that must be in place before you deploy IP phones and analog devices. These

requirements are in addition to the required components described in Required Lync Server 2010

Components for Devices. For details about analog devices, see Analog Gateway and Device

Configuration.

Note:

Review the manufacturer’s data sheet for the devices that you are deploying to learn

about additional requirements.

Hardware Requirements

IP phones running Microsoft Lync 2010 Phone Edition support Link Layer Discovery Protocol-

Media Endpoint Discovery (LLDP-MED) and Power over Ethernet (PoE). To take advantage of

LLDP-MED, the switch must support IEEE802.1AB and ANSI/TIA-1057. To take advantage of

PoE, the switch must support PoE802.3AF or 802.3at.

To enable LLDP-MED, the administrator must enable LLDP by using the switch console window

and set the LLDP-MED network policy with the correct voice VLAN ID.

In addition, if your deployment includes analog devices, you must configure the analog gateway

to use Microsoft Lync Server 2010, and the gateway must be one of the following:

1. An analog telephone adapter (ATA)

2. A SIP-PSTN analog gateway

3. A Survivable Branch Appliance that includes a SIP-PSTN analog gateway

4. A Survivable Branch Appliance that includes a SIP-PSTN gateway that communicates with an

ATA

To learn how to configure an analog gateway, see Analog Gateway and Device Configuration.

Important:

You can configure the switch for Enhanced 9-1-1 (E9-1-1), if the switch supports this.

Port Requirements

IP phones use port 443 for the Device Update service.

Note:

To configure ports for analog devices, use the Gateway Management Console, as

described in <information to come.>

67


DNS Requirements

IP phones require certain DNS records. The following table describes the records that you must

create and publish to a DNS service, within the corporate network, if you’re deploying IP phones.

For details about the DNS records that are required for external IP phones, see the DNS Records

for External Devices table later in this topic.

DNS Records for External Devices

Type Value Note

A Fully qualified domain names

(FQDNs) for the pool(s) hosting

the Enhanced Registrars

The new Lync Server 2010 DNS load

balancing feature requires you to specify

the server FQDN and the pool FQDN,

using the same IP address, for each

server in the pool and to create A

records for all pools that contain an

Enhanced Registrar. For example:

RegistrarServerOneInPool.<SIP

domain>: 1.2.3.4, RegistrarPool.<SIP

domain>: 1.2.3.4,

RegistrarServerTwoInPool.<SIP

domain>: 1.2.3.5, and

RegistrarPool.<SIP domain>: 1.2. 3.5.

If you are using hardware load

balancing, just specify A records for each

pool that contains an Enhanced

Registrar. Allows external devices to

connect by using SIP over TLS to the

Enhanced Registrar internally.

SRV _sipinternal._tcp.<SIP domain>

_sipinternaltls._tcp.<SIP

domain>

Specifies the two SIP FQDNs for internal

routing, one for communications over

TCP, and one for TCP communications

secured by TLS.

A ucupdates-r2.<SIP domain> Specifies the Web Services portion of

the Device Update services URL. The

device appends

“:443/RequestHandler/ucdevice.upx”.

Make sure the HLB translates external

requests to use

“:443/RequestHandler/ucdevice.upx.”

(The external port is 443.)

68


Note:

If the pool is already deployed, this information can be referenced from the Lync Server

Control Panel Topology tab by selecting the Edge server properties.

DHCP Requirements

IP phones require the Web Services URL and Enhanced Registrar FQDN from the DHCP server,

for connectivity. To make sure that the DHCP server can provide IP phones with the following

information:

Turn on this functionality by using this Lync Server 2010 Management Shell command: set-CsRegistrarConfiguration –EnableDHCPServer $true

Ensure that broadcast packets from devices can reach the DHCP server(s) by configuring

DHCP relay agents to forward DHCP packets to the Lync Server DHCP servers.

For internal communications, ensure that the following options are set up on the

organization’s DHCP servers:

DHCP Options for Internal IP Phones

Option Value Note

43 CS Pool

Certificate

Provisioning

Service URL

Specify the internal URL in the form

https://lyncWebPoolFQDN:443/CertProv/CertProvisioningService.svc*

120 FQDN for

the CA Pool

Registrar

Specify the FQDN of the pool that will be the first logon server for the

device. Typically this is a Director pool. If you do not deploy a Director

pool, this is the Front End pool FQDN. The pool FQDN suffix must

match the user's SIP URI.*

43 VLAN ID We strongly recommended that you use a VLAN. However, if you

decided not to use a VLAN for unified communications, or if you use

LLDP-enabled switches in the enterprise to provide VLAN IDs, do not

set this option. Note that option 43 is not an independent option.

Depending on the Vendor Class ID it is configured for, the option may

have different values. The client identifies the vendor for which it

wants the information as option 60 in the DHCP Request.

*These are general examples. For details, see Appendix: Configuring DHCP Options on

DHCP Servers other than Windows DHCP Server in the Deployment Guide.

Tips:

If you are not allowing external access, set up DHCP option 4 (TimeServer).

We strongly recommend that you deploy Lync Server DHCP servers in subnets where the

Lync Server servers are located and that you use Lync Server DHCP servers in the

central site and in small branch sites where Lync Server clients and servers are in the

same subnet.

69


Security Requirements

If you are allowing external access for IP phones, a PKI infrastructure must be in place, and

devices must have a valid Lync Server certificate, which they obtain when they log on and is

issued from a public certification authority (CA) (recommended) or a private CA that allows the

devices to connect to the Device Update service from outside the intranet. For details, see

Certificate Infrastructure Requirements in the Determining Your Infrastructure Requirements

documentation.

Edge Server Requirements

If you’re allowing external access for IP phones, deploy Edge servers by following the instructions

in Deploying Edge Servers at the TechNet website, but during the Set Up the Infrastructure for

Edge Server process, use the following configuration information to enable external access to the

Device Update service:

In the Configure a Reverse Proxy step, configure the reverse HTTP proxy to use the Device

Update service virtual directory https://<external Server FQDN>:443 for the external URL for

Web Services and the Device Update service.

In the Configure DNS step, use the following information:

DNS Records for External Devices

Type Value Note

SRV Edge server:_sipexternal._tls.<SIP

domain>, and _sipexternaltls.<SIP

domain>

Allows external devices to

connect via SIP over TLS

to the Enhanced Registrar

internally.

A Reverse proxy FQDN:<server

name>.<SIP domain>

Allows external devices to

connect via TLS over

HTTP to the Update

Service.

Note:

If the Edge server is already deployed, this information can be referenced from the

Lync Server Control Panel Topology tab by selecting the Edge server properties.

Mediation Server Requirements

If your deployment includes fax machines that interact with Lync Server 2010 so that CDR reports

are logged for FAX calls, you must enable media bypass for the trunk to the gateway to which the

FAX machines connect. Similarly, bypass should be enabled globally. The fax machines need to

be correctly configured in the contact object configuration, as described in “Contact Objects,” in

Required Lync Server 2010 Components for Devices The gateway must present FAX calls to

Lynch Server 2010 as G.711 audio calls; if presented as image calls, they will be rejected. These

calls will be hairpinned back to the gateway from which they were received; bypass will cause the

hairpin to be moved to the gateway.

Gateway Requirements

70


Fax devices must be connected to a gateway with PSTN connectivity for inbound and outbound

calls.

Deployment Guidelines and Process for Devices

This topic helps you plan to deploy devices by providing an overview of the deployment process

as well as best practices.

Best Practices for Deploying Devices

For the best audio quality, we recommend the following:

To separate Voice over IP (VoIP) traffic from other network traffic, configure the virtual local

area network (VLAN) that the devices connect to, to provide only VoIP connectivity.

Advise users to attach their USB device to a wired network, instead of a wireless network. (IP

phones are required to do this.)

Deploy Direct Access, instead of Remote Access, to remote users who are using USB

phones.

Checklist for Deploying Devices

When planning to deploy unified communications (UC) phones in an enterprise, use this checklist

of steps to guide you through the process.

Step 1: Select Devices and Documentation

Decide how many devices to deploy and what kind. For details, see Choosing New Devices.

If you’re buying new phones, identify and purchase the devices that you want. For details,

see Choosing New Devices.

Identify the information that users can read to guide them through setup and use and the

medium through which the information will be delivered. For details, see relevant Quick Start

and Work Smart documents.

Step 2: Ensure Lync Server 2010 Prerequisites

If you are allowing external use, deploy Edge server. For details, see System and

Infrastructure Requirements for Devices.

Deploy the mediation server/gateways for telephony. For details, see Deploying the

Enterprise Voice Workload in the Deployment documentation.

Start Web Services. For details, see Start or Stop Lync Server 2010 Services in the


Identify users, and enable Enterprise Voice for them. For details, see Deploying the

Enterprise Voice Workload in the Deployment documentation.

Tip:

Run a script to verify that users are enabled correctly for Enterprise Voice. For a list of all

enabled users, at the command prompt, type Get-CsUser | Where-Object

{$_.EnterpriseVoiceEnabled –eq $True} | Select Identity, EnterpriseVoiceEnabled. For a

list of all users that includes information about which users are enabled, at the command

71


prompt, type Get-CsUser | select DisplayName, EnterpriseVoiceEnabled.Set up dial

plans and call routes for users. For details, see Configuring Voice Routing in Operations.

Step 3: Make required configurations

If you’re deploying IP phones, open the required port and create the required DNS and DHCP

records. For details, see System and Infrastructure Requirements for Devices.

Create a contact object for each device. This is only applies to as conferencing or common

area phones.

Set up the appropriate voice policies for users, or review default polices by running the Grant-

cmdlet for the policy. (Run Get-Help Grant-CsClientPolicy –Full | more from the Lync Server

2010 Management Shell.) If you’re deploying common area phones, plan usage scenarios,

and configure polices and objects, as needed. For details, see Common Area Phone

Configuration.

If your deployment includes analog devices, configure the gateway and devices. For details,

see Analog Gateway and Device Configuration.

Step 4: Provision and prepare users

If you are deploying the new IP phones, assign an authentication PIN to each user, or decide

to let users set the PIN for him or herself.. An administrator can set the PIN from the Lync

Server Control Panel or from Lync Server 2010 Management Shell (Set -CSClientPIN). For

details, see Set-CSClientPin in the Command-line Reference documentation, or, Set a User's

Dial-in Conferencing PIN in the Operations documentation. A user can set the PIN by visiting

the Dial-in Conferencing Settings and PIN Management page.

Set the logging levels. For details, see Modify Settings for Log Files of Device Update Activity

in the Operations documentation.)

Download the latest software updates from Microsoft.com, and deploy them to test devices.

For details, see View Software Updates for Devices in Your Organization in the Operations

documentation. After you are satisfied with these, deploy them to all phone devices.

Ensure that users can access the end-user documentation that you are providing.

Step 5: Set Up Devices

Give the user the device, documentation, and PIN, if available.

Check call detail recording (CDR) to make sure that the user has received and made calls

and successfully logged in, while in the corporate environment. For details, see the CDR

Database Schema documentation.

Step 6: Support and Monitor the Deployment

Use Quality of Experience (QoE) reports. For details, see the QoE Database Schema

documentation.

Generate device update reports. (From IP Phone Inventory tool.)

72


Use other monitoring tools, including CDR reports. For details, see the CDR Database

Schema documentation.

Check Microsoft.com every three months for updates.

Step 7: Plan for the Migration and Coexistence of Devices

If you are migrating devices from earlier versions of Office Communications Server, the device

will be on running Lync Server 2010. If you need to point the device to a different server, you

need to move the users from Microsoft Office Communications Server 2007 R2 to Lync Server

2010 and have the users sign off and then sign back in.

Planning to Manage and Troubleshoot Devices

This section helps prepare you for updating, monitoring, and troubleshooting devices by giving

you an overview of device-related tools and services and the updating, monitoring, and

troubleshooting process.

Tools and Services for Managing and Troubleshooting Devices

Updating Devices

Monitoring and Troubleshooting Devices

Tools and Services for Managing and Troubleshooting Devices

The primary tools for managing and monitoring IP phones are the new Microsoft Lync Server

2010 Control Panel, the new Lync Server 2010 Management Shell, and the Device Update

service. This topic provides details about this service, these tools, and other key device-related

tools and services.

Tool/Service Purpose Location Learn more

Lync Server 2010

Control Panel

(New) Useful when

planning to deploy devices

and when updating and

monitoring IP phones. This

is the management console

for Microsoft Lync Server

2010 communications

software. For devices, you

can use Lync Server 2010

Control Panel to set up dial

plans, voice policies, call

routes, device logs, and

PINs, as well as start Web

Services and manage

Device Updates.

Open Lync Server

2010 Control Panel.

Lync Server 2010

Control Panel

Lync Server 2010 (Updated) Useful when Open Lync Server Lync Server

73



Management Shell planning to deploy devices,

and when troubleshooting.

This is the Windows

PowerShell command-line

interface, from which you

can use cmdlets to set up

contact objects and policies

for devices.

2010 Management

Shell.

Management Shell

Device logs Useful when provisioning,

monitoring, and

troubleshooting.

Update Server Web

Services and then

browse to the correct

folder.

<information to

come.>

Device Update

service

Useful when deploying new

devices and when Microsoft

releases updates to device

software. This service

allows you to download

updates from

Microsoft.com, test them,

and deploy them. You can

also roll back to previously

installed software versions.

Accessible through

the Lync Server

2010 Control Panel

or Windows

PowerShell.

Updating Devices

IP Phone Inventory

Report tool

(New) Useful when

monitoring and

troubleshooting issues on

IP phones. This tool allows

you to create reports

Monitoring Server

Reports

<information to

come.>

Power-on self test

(POST)

(New) Useful when

monitoring and


the new IP phones

(Polycom CX600, Polycom

CX500, Polycom CX3000,

Aastra 6725ip, and Aastra

6721ip). This tool allows

you to test the health of the

DDR2 RAM.

On the device.

(While the device is

starting up, press * +

7 to start POST. If

the test passes, the

startup process

continues. If the test

fails, the preboot

code returns an error

message (for

example, “POST

Failed. Device

cannot start”) and

N/A

74



the startup process

ends.)

Monitoring Server

Reports

Useful when monitoring and

troubleshooting issues

related to user activity and

media quality. There is a

Quality of Experience

(QoE) report for user

activity that searches for

call detail records based on

user alias and another

report for media quality that

searches individual detail

records for signal values

captured from the user’s

device microphone or

speaker Purpose

Monitoring Server

Reports

<information to

come.>

Reset (Hard,

Factory)

(New) Useful when


the new IP phones

(Polycom CX600, Polycom

CX500, Polycom CX3000,

Aastra 6725ip, and Aastra

6721ip). The Hard Reset

lets users delete all user-

created data (such as

device logs, registry

settings, and credentials).

The Factory Reset lets

users revert the device

back to the last working

software version, in the

event that the phone is

updated to a version that is

problematic and causing

issues for the users.

On the device.

(While the device

starts up, press # + 4

+ Backspace to start

the reset.)

N/A

Updating Devices

Note:

This topic applies only to IP phones.

75


Microsoft Lync Server 2010 includes the Device Update service, which is automatically installed

with Web Services. This service allows you to download updates from Microsoft, test them, and

then deploy the updates to all the IP phones in your organization. You can also use Device

Update service to roll back devices to previous software versions. We recommend that you check

for updates every three months.

Important:

Before you can use the Device Update service, you must fulfill the topology, component,

and other requirements described in Planning to Deploy Devices.

This topic helps prepare you to use the Device Update service by providing an overview of the

components and update process.

Usage Scenarios

Use the Device Update service in the following management scenarios:

Testing and deploying updates Retrieve updates from Microsoft and upload them to Device

Update service. Test, and then approve or reject, specific updates for deployment to your

organization’s IP phones to make sure that all updates are valid and functional, instead of having

to troubleshoot after deployment.

Rolling back an update Roll back a defective update and retain a tested prior update as the

latest update. The next time an IP phone polls the Device Update service for an update, it is sent

a URL to a prior (rolled back) version of the update. The phone now automatically installs this

update and effectively removes the defective update.

Introducing new device models Make available all software updates relevant to a new model

of an IP phone that is being introduced to the market.

Inventory management for devices in organizations Use the log files and audit information

stored in the Device Updates folder to view the IP phones in your organization and information

about them, such as the current firmware version.

Components of the Device Update Service

The Device Update service is made up of the following components:

Device Request Handler

The device request handler performs the following tasks:

Receives requests for software updates from IP phones.

Receives device logs and stores them on the server.

Generates audit logs for device update activity.

Device Updates Cabinet Files

Microsoft makes updates available in cabinet (.cab files) that you can download from the

Microsoft Help and Support Web site. An update .cab file contains updates for one or more

unified communications (UC) devices. After obtaining the .cab file, you upload it to Device Update

service by using the Lync Server 2010 Management Shell.

The following file types are contained in an update:

.cat: Security catalog

76


.nbt: Software image

.xml: Description file

Lync Server 2010 Control Panel

Use the following tabs, in the Clients category of the Microsoft Lync Server 2010 Control Panel, to

manage the Device Update service:

Device Update Provides the ability to view updates in the device update store, create

device update rules in Central Management store and approve or reject device updates for

deployment, approve or reject updates for test devices, and roll back updates to a previous

version.

Test Device Provides the ability to specify the devices that are to receive pending updates

for testing purposes.

Device Updates Filestore

The Device Updates filestore serves as the central repository for the update information, logs,

and audit information. It provides the installation point for devices that require updates.

In Lync Server 2010 Standard Edition, this folder is automatically created by the installer and

located in the Web Services folder, under the installation folder. The default path is as follows:

%ProgramFiles%\Microsoft Lync Server\Web Services\DeviceUpdateFiles.

In Lync Server 2010 Enterprise Edition, prior to installation, the administrator creates a shared

folder to contain both client and device update files. The administrator then specifies the location

of this folder when running the Create Front End Pool wizard during deployment.

Important

It is highly recommended that you create a quota on the Device Update service log file

store at %ProgramFiles%\Microsoft Lync Server\Web Services\DeviceUpdateFiles, using

the File Server Resource Manager. A quota will help to ensure that the number of log files

does not increase greater than the size of the filestore, which could cause problems on

the Web Services role. The Device Update Service log filestore is installed as part of the

Web Services role, and it is recommended that the quota be set up whether or not you

are using the Device Update service.

For more information on setting up a quota using the File Server Resource manager, see

"File Server Resource Manager Step-by-Step Guide for Windows Server 2008" at


The Device Update Process

The Device Update process begins with you downloading an update from Microsoft.com, and

then using the Lync Server 2010 Control Panel to test, approve, or reject the update. Approved

updates become pending updates that devices retrieve via the following process.

The first time a user starts an IP phone and signs in, the device gets information via in-band

provisioning from the server. The information contains the internal URL of the server running the

Device Update service.

77



If the device is turned on, but no user signs in, and no user has ever signed in on the device, then

the device sends a DNS lookup request to ucupdates-r2.<DNSDomainNameProvidedByDHCP>,

and obtains the internal URL of the server running the Device Update service.

The device checks for updates every time it is turned on, every time the user signs in, and every

24 hours, by default. It checks by sending an HTTP request over port 443 to the Web Services

server that hosts the Device Update service. The request includes the current version of software

that the phone is running, and the response is determined by the device is and whether there is a

new update on the server to download.

Internal Devices

If device is inside of the organization’s firewall, and the user is signed in, the Device Update

service returns a response that contains one of the following:

If no approved updates exist for the current version of the firmware, or if the current version of

the firmware matches the version of the approved update, the response contains NumOfFiles

= 0. For test devices, pending updates are also considered.

If an approved update is available for the current firmware version, the response contains the

path to the location from where the update can be downloaded.

External Devices

If the device is outside of the organization’s firewall, and the user is signed in, the Device Update

service returns a response indicating that anonymous access is not supported. The device then

sends an HTTPS update request over port 443 to the Device Update service. The Device Update

service returns one of the responses listed previously in the internal case.

If the device is outside the organization’s firewall, and the user is not signed in, the Device

Update service denies the request.

When the update is complete, the device uses the update as its current version, and the previous

version is stored in the firmware as a backup.

Monitoring and Troubleshooting Devices

Microsoft Lync Server 2010 communications software includes monitoring and troubleshooting

tools for devices.

Monitoring Devices

Learn about monitoring tools by reviewing Tools and Services for Managing and Troubleshooting

Devices. When preparing to monitor devices, you might want to modify the default settings on the

device log files. By default, log files are purged after 10 days, to free up disk space. You can

change this so that log files are purged more or less frequently. You can also set the time and day

when log files are to be purged and/or choose to purge log files manually. For details, see Modify

Settings for Log Files of Device Update Activity in the Operations documentation.

Troubleshooting Devices

Lync Server 2010 provides new and updated tools for troubleshooting device issues. For an

overview, see Tools and Services for Managing and Troubleshooting Devices. Before you use

troubleshooting tools, if you are deploying IP phones, it is important to understand devices

connect to your network.

78


For example, in Lync Server 2010, after an IP phone is plugged in to power and the network and

turned on, the bootstrapping process is as follows:

1. Find the virtual local area network (VLAN).

2. Obtain an IP address.

3. Find the address of the Web Services server that hosts the Device Update service.

4. Check for an update.

5. Obtain the Enhanced Registrar fully qualified domain name (FQDN) and Web Services URL.

6. Connect to the Web Services and the specified URL.

7. Download the root certificate chain from Web Services.

8. Get Web authentication.

9. Get and publish the Lync Server certificate.

10. Log on to the Lync Server.

Issues can occur in each of these stages, and the issues may differ depending on whether the

device is inside or outside of your organization’s firewall and on whether it is a new or older IP

phone.

Common issues with IP phones include problems with set up and sign in, obtaining an IP

address, dialing, hardware, audio quality, and installing updates. Troubleshooting tools help you

target these issues quickly, which is important to both user satisfaction and your total cost of

ownership (TCO).

Note:

Common issues with USB phones include problems getting started and dialing and with

hardware and audio or video quality. Users will be able to do most of their own

troubleshooting by referring to the User’s Guide for USB Phones.

For details about how all unified communications (UC) devices connect to the network, common

issues related to devices, and troubleshooting tools for devices, see <information to come>.

Common Area Phone Configuration

Before you deploy common area phones, you can configure call control behavior. For example,

you may want to allow call transfers from a common area phone in a conference room but not

from a common area phone in a lobby. You can also set up phones to block external usage and

compromised accounts and configure hot-desk phones, that is, phones on which users can log on

to their own user account and, once logged on, use Microsoft Lync Server 2010 communications

software features and their own user profile settings.

To do this:

1. Create a new contact object for each common area phone. If an Active Directory object

already exists, ensure that this object is not SIP enabled. If the object is SIP enabled, then

the command Disable-csUser should be used to remove Lync Server 2010 attributes, before

using the command New-csCommonAreaPhone.”

79


2. Create required policies for all common area phone usage scenarios. (This section provides

information on creating three most relevant policies on common area phones, but other

policies may be relevant to your enterprise.)

Important:

Before you complete the following steps, make sure that all of the required components

are in place (for details, see Required Lync Server 2010 Components for Devices) and

that you meet the requirements described in System and Infrastructure Requirements for

Devices.

Step 1: Create and Configure a New Contact Object

To create a new instance of a common area phone, use the New-CsCommonAreaPhone

cmdlet. For example:

New-CSCommonAreaPhone -LineUri "tel:+14255551212" -RegistrarPool "ocs-w14-se.ocspm-topo.net" -OU "OU=PM Users,DC=ocspm-topo,DC=net" -description "Room number 30-1000" -DisplayName "Building 30 Lobby" -DisplayNumber “1 (425) 555-1212”

This cmdlet creates a new contact object in Active Directory Domain Services (AD DS) for the

specified phone. Like user accounts, these contact objects can be assigned policies and voice

plans. As a result, you will be able to maintain control over common area phones even though

those phones are not associated with an individual user.

For details about creating contact objects for common area phones, run Get-Help New-

CsCommonAreaPhone –Full | more from the Lync Server 2010 Management Shell.

If you are deploying many common area phones, you may want to write a Windows PowerShell

command-line interface script to create multiple new objects at the same time by using a table as

an input for batch processing. Include entries for phone number, location, voice policy, client

policy, and any other policy and object settings that you want applied.

Notes:

For details about the Lync Server 2010 Management Shell and individual cmdlets, see

the Lync Server 2010 Management Shell documentation.

For information about monitoring and troubleshooting common area phones, see

Planning to Manage and Troubleshoot Devices.

Step 2: (Optional) Create Required Policies

Creating specific policies for common area phones is optional. If you do not create a new policy

for a common area phone, the phone will automatically use the policy defined for the site that the

phone contact object is homed on. If no site policy exists, the global policy will be used. But if

your organization has specific requirements for common area phones, use the Lync Server 2010

Management Shell cmdlets described below to create the client, voice, and conferencing policies

(the three policies most relevant to common area phones) that will apply to the common area

phone account being created. Create a policy for each usage scenario. For example, all lobby

phones can have lobby-specific policies, and phones in executive meeting rooms can have a less

restrictive set of policies than phones in regular meeting room phones.

80


If you create a new policy or want to use an existing per-user policy, you must grant that policy to

any contact objects (phones) that you want that policy applied to. To do this, call the Grant-

cmdlet of the policy. For example, to grant the client policy that we created earlier in this section

to the phone created in Step 1, run the following command:

Grant-CsClientPolicy –Identity "Building 30 Lobby" -PolicyName ADClientPolicy

Notes:

For details about granting client policies, run Get-Help Grant-CsClientPolicy –Full | more

from the Lync Server 2010 Management Shell.

For details about additional polices, see the Lync Server 2010 Management Shell

documentation.

Client Policy

To create a new client policy, use the New-CSClientPolicy cmdlet. For example, to create a

policy for common area phones that are used as hot-desk phones, run a command such as the

following:

New-CsClientPolicy –Identity HotDeskPhonesPolicy –EnableHotdesking $True –HotdeskingTimeout 1800

This example creates a new client policy with the identity HotDeskPhonesPolicy. We’ve set the

EnableHotdesking parameter to True ($True), which allows users to log onto the common area

phone using their Lync Server account. We’ve also set the HotdeskingTimeout parameter to

1800, which means that users who log onto the phone to which this policy is applied will be

allowed to remain logged on for a maximum of 1,800 minutes.

Note:

Other properties of a client policy that may be most relevant to common area phones

include ShowRecentContact, DisableFreeBusyInfo, and AddressBookAvailability.

Voice Policy

To create a new voice policy, use the New-CSVoicePolicy cmdlet. For example:

New-CsVoicePolicy -Identity CAPvoicepolicy –PstnUsages @{add="Internal","Local"} -allowsimulring $False -Allowcallforwarding $False -Name CAPvoicepolicy -EnableDelegation $False -EnableTeamCall $FALSE -EnableCallTransfer $FALSE

This example creates a new voice policy with the Identity CAPvoicepolicy. This new policy sets

several properties that would most likely apply to common area phones. It turns off simultaneous

ring (-AllowSimulRing $False), so calls to the phone that this policy is applied to cannot

simultaneously ring on another phone, such as a mobile phone. It also turns off call forwarding (-

AllowCallForwarding $False), call delegation (-EnableDelegation $False), the ability to transfer

calls (-EnableCallTransfer $False), and the ability to set up a team of users whose phones will

ring when this phone does (-EnableTeamCall $False).

81


Notes:

As shown in the preceding example, the following voice policy settings are recommended

for common area phones:

AllowCallForwarding : False

EnableDelegation : False

EnableTeamCall : False

EnableCallTransfer : False

To see a list of all available voice policy properties and their descriptions, run Get-Help

New-CsVoicePolicy –Full from the Lync Server 2010 Management Shell.

Conferencing Policy

To create a new conferencing policy, use the New-CSConferencingPolicy cmdlet. For example:

new-csconferencingpolicy -identity CAPconferencingpolicy -allowIPAudio $false -allowIPvideo $False -EnableFileTransfer $False -EnableP2PFileTransfer $False -EnableDataCollaboration $False

This is an example of a conferencing policy with settings that could be applicable to a common

area phone. This example creates a conferencing policy with an Identity CAPconferencingpolicy.

This new policy disables the following:

The ability to use computer audio in a meetings (-AllowIPAudio $False)


The ability to transfer files as part of the conference (-EnableFileTransfer $False)

Peer-to-peer file transfers during the conference (-EnableP2PFileTransfer)


Notes:

The following conferencing policy settings are typically set for common area phones, but

these and others can be changed depending on enterprise needs:

AllowIPAudio : False

AllowIPVideo : False

EnableFileTransfer : False

EnableP2PFileTransfer : False

EnableDataCollaboration : False


New-CsConferencingPolicy –Full | more from the Lync Server 2010 Management

Shell.

Note:

After you configure common area phones, provision them by installing them where they

will be used and just sign in. If the phone will be used at a hot desk, the phone must be

82


provisioned according to the process described in Setting Up Authentication on the New

IP Phones, in the Deployment Guide.

Analog Gateway and Device Configuration

To add analog devices to your deployment, do the following:

1. Create a new contact object for each analog device.

2. (Optional) Create required policies, and grant them.

Important:

Before you complete the following steps, make sure that all of the required components

are in place (for details, see Required Lync Server 2010 Components for Devices) and

that you meet the requirements described in System and Infrastructure Requirements for

Devices.

Step 1: Create and Configure a New Contact Object

A user cannot sign in on an analog device, so the device cannot be associated to a user. Creating

a new contact object in Active Directory Domain Services (AD DS) for an analog device gives you

a way to manage the device, even though the device isn’t associated with an individual user. This

is because, like a user account, a contact object can be assigned policies and voice plans.

To create a new instance of an analog device that you can manage with Microsoft Lync Server

2010, use the New-CsAnalogDevice cmdlet. For example:

New-CsAnalogDevice -LineUri tel:+14255556001 -DisplayName "Building 14 Receptionist" -RegistrarPool redmond-Cs-001.litwareinc.com -AnalogFax $False -Gateway 192.168.0.240 -OU "ou=Telecommunications,dc=litwareinc,dc=com"

This command creates a new analog device with the phone number (LineUri) 1-425-555-6001.

(Note that the phone number must be specified using the E.164 format.) In addition to the -

LineUri parameter, the other parameters used in this command are -DisplayName (to set the

Active Directory display name of the device); -RegistrarPool (to specify the registrar pool); -

AnalogFax (set to $False, to indicate that this is a phone and not a fax machine); -Gateway (set

to the IP address of the gateway); and -OU (the distinguished name of the Active Directory OU

where the device's contact object should be created).

For details about creating contact objects for analog devices, run Get-Help New-

CsAnalogDevice –Full | more from the Lync Server 2010 Management Shell.

If you are deploying many analog devices, you may want to write a Windows PowerShell

command-line interface script to create multiple new objects at the same time by using a table as

an input for batch processing. Include entries for phone number, location, voice policy, and any

other applicable policies such as voice policy and other settings that you want applied.

Note:

For details about the Lync Server 2010 Management Shell and individual cmdlets, see

the Lync Server 2010 Management Shell documentation.

83


Step 2: (Optional) Create Required Policies and Grant Them

Creating specific policies for analog devices is optional. If you do not create a new policy for an

analog device, the device will automatically use the policy defined for the site that the device

contact object is homed on. If no site policy exists, the global policy will be used. If your

organization has specific requirements for analog devices, use the Lync Server 2010

Management Shell cmdlets described below to create the voice and conferencing policies (these

policies most relevant to analog devices) that will apply to the analog device account being

created. Create a policy for each usage scenario.

If you create a new policy or want to use an existing per-user policy, you must grant that policy to

any contact objects (phones) that you want that policy applied to. To do this, call the Grant-

cmdlet of the policy. For example, to grant the client policy that we created earlier in this section

to the phone created in Step 1, run the following command:

Grant-CsClientPolicy –Identity "Building 30 Lobby" -PolicyName ADClientPolicy

Notes:

For more information about granting client policies, run Get-Help Grant-CsClientPolicy –

Full | more from the Lync Server 2010 Management Shell.

For details about additional polices, see the Lync Server 2010 Management Shell

documentation.

Voice Policy

To create a new voice policy, use the New-CSVoicePolicy cmdlet. For example:

New-CsVoicePolicy -Identity ADvoicepolicy –PstnUsages @{add="Internal","Local"} -allowsimulring $False -Allowcallforwarding $False -Name ADvoicepolicy -EnableDelegation $False -EnableTeamCall $FALSE -EnableCallTransfer $FALSE

This example creates a new voice policy with the Identity ADvoicepolicy. This new policy sets

several properties that would most likely apply to analog devices. It turns off simultaneous ring (-

AllowSimulRing $False), which makes it so that calls to the phone that this policy is applied to

cannot simultaneously ring on another phone, such as a mobile phone. It also turns off call

forwarding (-AllowCallForwarding $False), call delegation (-EnableDelegation $False), the ability

to transfer calls (-EnableCallTransfer $False), and the ability to set up a team of users whose

phones will ring when this phone does (-EnableTeamCall $False).

Notes:

As shown in the preceding example, the following voice policy settings are recommended

for analog devices:

AllowCallForwarding : False

EnableDelegation : False

EnableTeamCall : False

EnableCallTransfer : False

84



New-CsVoicePolicy –Full from the Lync Server 2010 Management Shell.

Conferencing Policy

To create a new conferencing policy, use the New-CSConferencingPolicy cmdlet. For example:

new-csconferencingpolicy -identity ADconferencingpolicy -allowIPAudio $false -allowIPvideo $False -EnableFileTransfer $False -EnableP2PFileTransfer $False -EnableDataCollaboration $False

This is an example of a conferencing policy with settings that could be applicable to an analog

device. This example creates a conferencing policy with an Identity ADconferencingpolicy. This

new policy disables the following:


The ability to use computer video (-AllowIPVideo $False)

The ability to transfer files as part of the conference (-EnableFileTransfer $False)


The ability to join the conference over the Internet (-EnableDataCollaboration $False)

Notes:

The following conferencing policy settings are typically set for analog devices, but these

and others can be changed depending on enterprise needs:

AllowIPAudio : False

AllowIPVideo : False

EnableFileTransfer : False

EnableP2PFileTransfer : False

EnableDataCollaboration : False


New-CsConferencingPolicy –Full | more from the Lync Server 2010 Management

Shell.

Compatibility and IntegrationThis section discusses the client compatibility and integration issues you should consider during

migration to Microsoft Lync Server 2010 communications software and Microsoft Lync 2010.

The basic requirements for support of Lync Server 2010 clients are as follows:

Client computers running Windows XP Service Pack 3 (SP3) or later

Microsoft Office 2007 suites or later, and Microsoft Exchange Server 2007 or later (for

integration between Lync 2010 and Microsoft Outlook)

Support for Microsoft Silverlight browser plug-in version 4.0 (required by Lync 2010 and

installed during setup)

85


Client Interoperability

Lync 2010 Compatibility

Lync 2010 Integration

See Also


Client Interoperability

This topic discusses the ability of Microsoft Lync Server 2010 communications software clients to

coexist and interact with clients from earlier versions of Office Communications Server.

There are two types of client compatibility, as follows:

Multiple points of presence (MPOP) The ability of a single user to sign in to a server with

multiple clients and multiple client versions.

Interoperability The ability to interact with another user who is signed in using a different

client type, or an earlier version of the same client.

Planning for Compatibility

Important:

In order to fully test the new Lync Server 2010 features during migration, you must

ensure that previous client versions have the most recent updates, or hotfixes, installed.

For details, see Planning for Client Migration.

Lync Server 2010 fully supports interoperability among Lync Server 2010 clients.

Most instant messaging (IM), presence, and voice features are also supported when interacting

with Microsoft Office Communications Server 2007 R2 and Microsoft Office Communications

Server 2007 clients. For details, see the "Lync Server 2010 Interoperability with Previous Client

Versions" section later in this topic.

For best results with meetings, see Migration Considerations for Meetings.

Compatibility among Lync Server 2010 Clients

All Lync Server 2010 clients can interoperate with other Lync Server 2010 clients.

Most Lync Server 2010 clients also support the multiple points of presence scenario—that is, a

single user can be signed in at multiple locations—with the following exception:

Microsoft Lync 2010 Attendant users can only be signed in simultaneously with phones

running Microsoft Lync 2010 Phone Edition. Simultaneous sign-in with other Lync Server

2010 clients is not supported.

Multiple Points of Presence (MPOP) with Previous Client Versions

The following table describes the client versions that are supported when a single user is signed

in to Lync Server 2010 at multiple locations.

Note:

Lync Server 2010 clients cannot sign in to previous server versions.

86


Client Versions Supported for Sign-in from Multiple Locations

Current client version

Planned client version MPOP support (with

required updates)

Lync 2010

Microsoft Lync 2010 Attendee

Microsoft Office Communications Server 2007

R2

Microsoft Office Communications Server 2007

2007 R2 release of Microsoft Office

Communicator Web Access

Microsoft Office Communicator Web Access

(2007 release)

Phones running Microsoft Office Communicator

2007 R2 Phone Edition

Phones running Microsoft Office Communicator

2007 Phone Edition

Microsoft Messenger for Mac 7

Microsoft Lync 2010 Attendant Phones running Microsoft Lync 2010 Phone

Edition

Phones running Microsoft Lync 2010 Phone

Edition

Microsoft Office Communicator 2007 R2

Microsoft Office Communicator 2007

Messenger for Mac 7

2007 R2 release of Microsoft Office

Communicator Mobile

Microsoft Office Communicator 2007 R2

Microsoft Office Communicator 2007

Microsoft Office Communicator 2007 R2 Phone

Edition

Microsoft Office Communicator 2007 Phone

Edition

Messenger for Mac 7

Note:

Messenger for Mac 7 supported features are described in the "Microsoft Messenger for

Mac 7 Deployment Guide" at http://go.microsoft.com/fwlink/?LinkId=177909.

Lync Server 2010 Interoperability with Previous Client Versions

This section discusses Lync Server 2010 interoperability support for clients that shipped with

Office Communications Server 2007 R2 and Office Communications Server 2007.

Note:

Communicator Web Access and Microsoft Office Live Meeting 2007 cannot be used to

join new meetings scheduled on Lync Server 2010. Lync 2010, Microsoft Lync 2010

87



Attendee, and Microsoft Lync Web App are the recommended alternatives. For details,

see Migration Considerations for Meetings.

IM, Presence, Voice, and Video Interoperability

The following table describes the availability of these features during migration.

IM, Presence, and Voice Interoperability with Previous Client Versions

Lync Server 2010

clients


Server 2007 R2 clients


Server 2007 clients

Lync Server 2010

Clients

IM, presence, voice,

and video supported

IM, presence, voice, and

video supported

IM, presence, and video

supported; some voice

feature limitations (see

the following section in

this topic)

Interaction with Microsoft Office Communicator 2005 clients (basic presence and IM) is supported

only if the Office Communicator 2005 user is on a federated network.

Note:

The Call Park application and Response Group application require that you deploy Lync

Server 2010 Edge Server and Director roles.

Voice Interoperability Considerations

Voice interoperability issues to be aware of when you are using the release candidate are as

follows:

Office Communicator 2007 does not support voice features added in Communicator 2007 R2

and Lync 2010, such as call park, team call, and response group service.

Call park issues you should be aware of during migration are as follows:

A call parked by a Lync 2010 user cannot be unparked by clients or devices signed in to

an earlier version of Office Communications Server.

You cannot park a call to an Office Communications Server 2007 client or device.

Conferencing Interoperability Considerations

When a user account is moved from Communications Server 2007 R2 to a Lync Server 2010

server, the following information moves along with the user account:

Meetings already scheduled by the user.

The user’s PIN (there is no need for new PIN assignment).

The following information does not move to the new server:

Meeting content. You should advise meeting organizers to reload content into their scheduled

meetings after migration.

The following tables describe two conferencing interoperability scenarios:

Previous client version interoperability with Lync Server 2010 online meetings

Lync 2010 interoperability with meetings hosted or scheduled on previous server versions

88


Previous Client Versions and Lync Server 2010 Meetings

Communicator 2007

R2and Communicator

2007 interoperability

Schedule Lync Server

2010 Meetings

Join Lync Server 2010

Meetings

Behavior in Lync

Server 2010 Meetings

Before user is moved

to Lync Server 2010

Not supported. Supported if enabled.

See Migration

Considerations for

Meetings for details.

No access to new

collaboration features

unless meeting is

escalated to use Lync

Web App.

No access to new

lobby management

features.

After user is moved to

Lync Server 2010, but

before new clients are

installed

Continue using the

Conferencing Add-in

for Microsoft Office

Outlook to schedule

conference calls and

Live Meeting web

conferences.

Supported if enabled.

See Migration

Considerations for

Meetings for details.

No access to new

collaboration features

unless meeting is

escalated to use Lync

Server 2010.

No access to new

lobby management

features.

For details, see Migration Considerations for Meetings.

Lync 2010 Interoperability With Meetings Hosted or Scheduled on Previous Versions of Office Communications Server

Lync 2010 interoperability with meetings on

previous versions of user experience Lync 2010 user experience

Scheduling Lync 2010 users cannot schedule meetings on

earlier server versions.

When modifying the end date, subject, or

attendee list of meetings migrated from

previous server versions to Lync Server 2010,

users are prompted to convert the meeting to

Lync Server 2010.

Joining No issues.

In meeting New Lync 2010 features are unavailable.

Manager/Delegate Interoperability

For the manager/delegate scenario, both manager and delegate must be using Lync 2010.

89


Interoperability with Existing Custom Applications

For the purposes of this discussion an existing custom application is defined as follows:

The application uses the Microsoft Office Communicator Automation API or the Microsoft

Unified Communications Client API.

The application runs in a migration environment, on a machine where either Communicator

2007 R2 or Communicator 2007 is connected to a server running Lync Server 2010.

Existing custom applications can sign in to a Lync Server 2010 server and interact with Lync

Server 2010 clients. However, the following limitations apply:

Existing custom applications do not have access to Lync 2010 features.

Running a Unified Communications Client API custom application on the same computer as

Lync 2010 is not recommended.

If your organization plans to enable enhanced presence privacy mode (see Communicator

2010 New Features), Unified Communications Client API custom applications may need to be

rewritten. For details, see Client Planning Overview and the Microsoft Lync 2010 SDK

documentation.

Lync 2010 Compatibility

This section discusses the compatibility of Microsoft Lync 2010 communications software with

various versions of Microsoft Office suites, Microsoft Exchange Server, Windows operating

systems, and selected public instant messaging (IM) clients.

Microsoft Office

The following table describes the Lync 2010 features that are supported by various versions of

Microsoft Office:

Lync 2010 and Microsoft Office Compatibility

Feature

Microsoft Office 2003

with Service Pack 3

(SP3) Microsoft Office 2007 Microsoft Office 2010

Presence in Microsoft

Outlook To and Cc

boxes

Presence on hover Presence always

displayed

Presence always

displayed

Reply with conference

call from Presence

menu

No Yes Yes

Presence in a Meeting

Request on the

Scheduling Assistant

tab

No Yes Yes

Reply with IM or call No Yes Yes

90


Feature

Microsoft Office 2003

with Service Pack 3

(SP3) Microsoft Office 2007 Microsoft Office 2010

from received e-mail

toolbar or ribbon

Presence in Outlook

From box

Yes Yes Yes

Reply with IM or voice

from Presence menu

Yes Yes Yes

IM and presence in

Microsoft Word and

Microsoft Excel (smart

tags enabled)

Yes Yes Yes

IM and Presence in

Microsoft SharePoint

(Outlook must be

installed)

Yes Yes Yes

The following features are available only with Microsoft Office 2010 and Lync 2010:

New Contact Card with expanded options such as video call and desktop sharing

Quick search from the Outlook Find a Contact box

Reply with an IM or call from the Outlook Home ribbon in the Mail, Calendar, Contacts, and

Tasks folders

Lync Contact List in Outlook To-Do Bar

Office Backstage (File tab) presence, application sharing, and file transfer

Presence menu in Microsoft Office SharePoint Workspace 2010 (formerly Microsoft Office

Groove 2007)

Presence menu extensibility

Exchange Server

The following table describes Lync 2010 support for various versions of Exchange Server. Office

Outlook must be installed on the client computer to handle Extended MAPI calls, and some

features require the use of Exchange Web Services (EWS).

Lync 2010 and Exchange Server Compatibility

Exchange Server version Lync 2010 support

Exchange 2000 Server Extended MAPI only. Features that require

Exchange Web Services (EWS) are not

available (see later).

91


Exchange Server version Lync 2010 support

Exchange Server 2003 Extended MAPI only. EWS-only features are

not available (see later).

Exchange Server 2007 SP1 The following features are available only

through EWS:

Read or delete Conversation History items

Read or delete voice mail items

Display working hours

For a complete list of the communication

interfaces that are used by Lync 2010, see Lync

2010 Integration.

Public folders are optional in Exchange Server

2007

Exchange Server 2010 Same as Exchange Server 2007 SP1. For

details, see Lync 2010 Integration.

Windows Operating Systems

The following table describes Lync 2010 compatibility with various versions of Windows.

Lync 2010 and Windows Compatibility

Windows version Lync 2010 support

Windows 7 32-bit operating system Supported

Windows 7 64-bit operating system Supported in Windows on Windows 64 mode

Windows Vista 32-bit operating system Supported

Windows Vista 64-bit operating system Supported in Windows on Windows 64 mode

Windows XP Professional with SP3 Supported. Windows Installer 3.1 and Microsoft

Core XML services (MSXML) 6.0 SP1 must be

installed before deploying Lync 2010.

Windows Server 2003 SP2 or greater

Windows Server 2008 SP2 or greater

Supported

Windows 2000 SP4 Not supported

Public Instant Messaging Clients

If you have configured your server for public IM connectivity, Lync 2010 supports IM and basic

presence when communicating with the following public instant messaging networks:

Microsoft Live (Live Messenger and Messenger for Mac 7)

92


AOL

Yahoo!

Presence states are filtered to those supported by the public IM client.

Lync 2010 Integration

This topic details how Microsoft Lync 2010 communications software integrates with the following

versions of Microsoft Office and Microsoft Exchange:

Microsoft Office 2007 suites

Microsoft Office 2010 suites

Microsoft Exchange Server 2007 Service Pack 2 (SP2)

Microsoft Exchange Server 2010

Note:

Outlook 2003 SP2 and earlier versions of Exchange are compatible with Lync 2010, but

do not support the full degree of integration discussed in this topic. For details, see Lync

2010 (Release Candidate) Compatibility.

Integrating Microsoft Lync 2010 and Microsoft Office provides users with in-context access to the

instant messaging (IM), enhanced presence, telephony, and conferencing capabilities of Lync

2010.

Microsoft Office users can access Lync 2010 features from within Outlook and other Office

applications, or from a SharePoint Server page. Users can also view a record of Lync 2010

conversations in the Office Outlook Conversation History folder.

The following topics are discussed in this section:

Planning for integration between Lync 2010, Outlook, and other Office applications

Exchange Server interfaces that are used by Lync 2010 and Outlook to access and update

shared information

In-band provisioning settings that can be used to control the level of Lync 2010 integration

with Outlook

Lync 2010 integration with other Office applications

Suggestions for avoiding common Lync 2010 integration issues

93


Planning for Lync 2010 Integration

Review the following configuration issues to ensure that you have everything required for

integration between Lync 2010 and other Office applications:

Configure integration between Microsoft Lync Server 2010 and Exchange Server.

Review the integration features which can be configured during Lync 2010 deployment by

using in-band server settings. For details, see the "Controlling Integration" section later in this

topic.

Note that the Online Meeting Add-in for Microsoft Lync 2010 is installed at the same time as

Lync 2010.

In organizations with multiple versions of Communicator or Office installed, review the

compatibility tables in Lync 2010 (Release Candidate) Compatibility.

Review the list of suggestions for preventing common integration errors in the "Common Lync

2010 and Outlook Integration Issues" section later in this topic.

Integration and Exchange Server

To support Lync 2010 integration, both Lync 2010 and Outlook read and write information directly

to Exchange Server. This section discusses the Exchange Server interfaces used by Lync 2010

and Outlook.

To display information about a contact in an e-mail message, Outlook first looks for the contact’s

SIP address locally, and then makes an RPC call to Exchange Server if required. During a single

Outlook session, the number of RPC calls decreases as more SIP addresses are cached.

In Lync 2010, integration features that use either MAPI or Exchange Web Services calls directly

to the Exchange Server are as follows:

Access Conversation History and missed calls

Play back voice mail message

Display Free/Busy information and working hours

Display meeting subject, time, and location

Display Out of Office status and note

Notes:

Outlook 2007 makes RPC calls to resolve SIP addresses only if the Display online

status next to a person name option is selected. To view this option in Outlook 2007:

from the Tools menu, select Options, select Other, and then look under Person Names.

In Outlook 2010: On the File tab, click Options, select Contacts, and then look under

Online status and photographs.

94


Exchange Server Communication Interfaces

The following table describes the communication interfaces used by Lync 2010 to access and

update features shared with Outlook. Exchange Server calls are made either directly, through

MAPI or Exchange Web Services (EWS), or indirectly, through the Outlook Object Model.

Exchange Server Communication Interfaces Used by Lync 2010

Communication interface Function

Outlook Object Model Send email message

Schedule a meeting

Receive seed information for EWS

Open voice mail folder

Open the Conversation History folder

MAPI only Exchange delegates

MAPI if available, otherwise EWS (persistent

subscription)

Create the Conversation History folder

Voice mail notifications

Missed Conversation notifications

Read Contacts folder

Write Contacts (on demand)

EWS (persistent subscription) if available,

otherwise MAPI

Write Conversation History items (on demand)

EWS only (persistent subscription) Read or delete Conversation History items

Read or delete voice mail items

EWS (polling) if available, otherwise MAPI Read free/busy times

Read Out of Office note

EWS only (polling) Read working hours information

Publishing Free Busy Information

A Lync 2010 user cannot access another user’s availability and schedule directly, so Free/Busy

and Out of Office details are published as part of a contact’s extended presence information. This

works as follows:

1. On User A’s computer, Lync 2010 uses Exchange Web Services calls to determine the user’s

own Free/Busy and Out of Office status.

2. Lync 2010 then updates User A’s enhanced presence data with this information.

3. Other Lync 2010 and Office 2007 users can now view User A’s schedule details and Out of

Office status, if applicable.

95


The availability of Free/Busy and Out of Office information about a contact is also controlled by a

user’s Privacy Relationship settings. For details, see Lync 2010 New Features in the Getting

Started documentation.

Note:

Free/Busy times and Out of Office information are obtained through MAPI—rather than

through EWS—for client-server combinations other than Lync 2010 or Office

Communicator 2007 R2, and Exchange Server 2007 or Exchange Server 2010.

Controlling Outlook Integration

All the Outlook 2007 or Outlook 2010 integration features are enabled by default, but can be

controlled individually from within Lync 2010 or through Microsoft Lync Server 2010 in-band

provisioning settings.

The following table lists the in-band server settings that administrators can use to enable or

disable individual integration features, either during deployment, or later as part of a maintenance

or upgrade cycle.

For details about configuring Lync 2010 users and settings, see Client Configuration Overview.

Outlook Integration Options In-band Provisioning Settings

Policy Description

DisableCalendarPresence Disables the loading of free or busy data from

Outlook.

DisableFreeBusyInfo Prevents Lync 2010 from displaying Outlook

information about free or busy states to other

contacts.

DisableMeetingSubjectAndLocation Prevents Lync 2010 from publishing the subject

and location information of a meeting. This

value is not used if DisableCalendarPresence

is set, or if the Update my status based on

calendar data option is not set.

DisablePresenceNote Prevents selection or clearing of the

corresponding user setting.

EnableIMAutoArchiving Controls automatic archiving of IMs to the

Outlook Conversation History folder. If set to

False, the corresponding user setting is

unavailable, but users can still manually save

individual conversations.

EnableCallLogAutoArciving Controls the automatic saving of information

about incoming and outgoing phone calls.

When set to False, the corresponding user

dialog box setting is unavailable.

96


Many aspects of Lync 2010 and Outlook integration are controlled by Outlook, and not by Lync

Server 2010. The following new Outlook 2010 integration features, which appear when Lync 2010

is present, are examples of this:

New Contact Card with expanded options such as video call and desktop sharing

Quick search from the Outlook Find a Contact box

Reply with an IM or call from the Outlook Home ribbon in the Mail, Calendar, Contacts, and

Tasks folders

Lync 2010 Contact List in Outlook To-Do Bar

Some Office-based integration features can be controlled by using Office Group Policy Objects

(GPOs). For details, see the Office 2010 Resource Kit at http://go.microsoft.com/fwlink/?

LinkID=201591, or the Office 2007 Resource Kit at http://go.microsoft.com/fwlink/?

LinkID=201599.

Integration with Office Applications

The Office Sharing Add-in for Lync 2010 adds collaboration and sharing features to Word,

PowerPoint, and Excel. The add-in is installed automatically on computers where Office 2007 or

Office 2010 is also installed. The add-in is not compatible with Office 2003.

The sharing add-in allows Office 2007 or Office 2010 users to initiate a Lync 2010 collaboration or

IM session from within an Office document. The added options are as follows:

Lync 2010 Collaboration Features in Word, PowerPoint, and Excel

Option Description

Office menu (2007) or File tab (2010): Send by

Instant Message

Review tab: Send by IM

Initiates an IM session with the contacts you

choose. The document you are working on is

included as an attachment, and changes or

feedback must be incorporated manually.

Office menu (2007) or File tab (2010): Share

Document Window

Review tab: Share Now

Initiates an application sharing session with the

contacts you choose. Others can view the

document you are working on (but not your

entire desktop) and request permission to make

changes.

Two additional Lync 2010 integration features are specific to Office 2010:

File tab presence: click Info, and then look under Related People

Presence menu in Microsoft Office SharePoint Workspace 2010 (formerly Microsoft Office

Groove 2007)

Integration with SharePoint Server

In both Windows SharePoint Services and Microsoft SharePoint Server, users must have Office

2003 SP2, Office 2007, or Office 2010 installed to view extended presence.

97






To display the presence button and menu, SharePoint uses a Microsoft ActiveX control called

name.dll. The ActiveX control makes calls directly to the Microsoft Lync 2010 API, and then Lync

2010 makes MAPI or Exchange calls-if required-to supply the requested information.

For more information about how presence is displayed in an Office SharePoint Server page, see

this SharePoint developer blog entry on the Microsoft Developer Network (MSDN) at


Smart Tags in Office 2003 and Office 2007

For the presence button and menu to appear next to (or above) a contacts name in Word 2003 or

Word 2007, and Excel 2003 or Excel 2007, smart tags must be enabled.

For instructions on how to enable smart tags from within Word or Excel, see the following

Microsoft Knowledge Base article 300950, "How to troubleshoot custom Smart Tags in Office," at


For information about how to do large-scale customization of end-user settings in your

organization by using Office 2007 group policies, see the Office 2007 Resource Kit at


Note:

Smart tags are supported in Word 2010, but do not appear with the dotted purple

underline present in previous versions of Word. Excel 2010 does not support smart tags.

Common Lync 2010 and Outlook Integration Issues

This section lists some common configuration issues which might prevent Lync 2010 integration

with Outlook from working as expected.

In organizations with Office 2003, and Office 2007 or Office 2010, installed, ensure that you

have deployed the most current version of the Microsoft Office Compatibility Pack for Word,

Excel, and PowerPoint File Formats. For details, see http://go.microsoft.com/fwlink/?

LinkId=147186.

Check that end-user integration settings in both Outlook and Lync 2010, which are normally

enabled by default when Lync 2010 is installed, are set correctly:

In Outlook, verify that the Display online status next to a name option is selected.

To view this option in Outlook 2007: From the Tools menu, select Options, select Other,

and then look under Person Names.

In Outlook 2010, click the File tab, click Options, click Contacts, and then look under

Online status and photographs.

In Lync 2010, verify that Microsoft Exchange or Microsoft Outlook is selected as the

user’s personal information manager.

98






Date post:	28-Jan-2015
Category:	Technology
Upload:	daniel-ullmark
View:	131 times
Download:	8 times

Planning for clients and devices lync server 2010 (rc)

Technology