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
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...............................................................................................16
Lync 2010 and Online Meeting Add-in for Microsoft Lync 2010 System Requirements...16
Lync Server 2010 Attendant System Requirements........................................................18
Lync Web App Supported Platforms................................................................................19
Key Client Policies and Settings.........................................................................................20
Client Configuration Overview.............................................................................................23
Planning for Client Migration...............................................................................................41
Client Planning Steps during Migration............................................................................41
Migration Considerations for Meetings............................................................................43
Client Version Check.......................................................................................................46
Migrating User Settings to Lync Server 2010...................................................................48
Planning for Devices..............................................................................................................55
Devices in Lync Server.......................................................................................................56
What's New for Devices......................................................................................................57
Choosing New Devices.......................................................................................................59
Desk Phone Comparison Table.......................................................................................62
Common Area Phone and Conferencing Device Comparison Table................................63
Planning to Deploy Devices................................................................................................64
Supported Topologies for Devices...................................................................................64
Required Lync Server 2010 Components for Devices.....................................................65
System and Infrastructure Requirements for Devices......................................................67
Deployment Guidelines and Process for Devices............................................................71
Planning to Manage and Troubleshoot Devices..................................................................73
Tools and Services for Managing and Troubleshooting Devices......................................73
Updating Devices............................................................................................................75
Monitoring and Troubleshooting Devices.........................................................................78
Common Area Phone Configuration...................................................................................79
Analog Gateway and Device Configuration.........................................................................82
Compatibility and Integration..................................................................................................85
Client Interoperability..........................................................................................................86
Lync 2010 Compatibility......................................................................................................90
Lync 2010 Integration..........................................................................................................93

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 Clients
The 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

Planning for Clients and Devices in Microsoft Lync Server 2010 (Release Candidate)
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 Administrators must often work with other
configuration tasks in a single location, using a departments in the organization (for example,
single user interface. 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, Settings can only be configured at the global
domain or organizational unit), site, or tag level. and user levels.
Tags are settings that can be applied to a single
user, or to a group of users.

In-band provisioning settings that are server- Group Policy settings that are distributed by
based provide a consistent end-user using Active Directory require that users be
experience for people who are not joined to the connected to the corporate domain using a
corporate domain, or who join using devices or computer.
remote clients.

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- Client applications could be modified by a
based help make clients secure because they malicious user.
do not depend on the client application to
enforce the policy.

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.

2

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


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 Microsoft Lync 2010 Microsoft Office
App Attendee Communicator 2007 R2
or Microsoft Office
Communicator 2007

Web application Yes No No

Deployment or Silverlight Client application Not applicable
installation (includes Silverlight
requirements installation)

New Lync Server 2010 Yes1 Yes No
conferencing features

Dial-in conferencing Yes2 Yes2 Office Communicator
2007 R2 only

Integrated IP audio No Yes Yes
and video

Anonymous join by Yes Yes Federated only
federated or external
users

Authenticated join by Yes Yes, if already Yes
internal users signed in with an
earlier client

Authenticated join by Yes No No
external users

1
All 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.
2
Dial-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.
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.

5

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.

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

6

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

Online
Meeting
Microsof Add-in
Microsof Microsoft Microsof t Lync for
Microsof Microsof t Lync Lync t Lync 2010 Microsof
t Lync t Lync 2010 2010 2010 Phone t Lync Messenger
Feature/capability 2010 Web App Attendee Attendant Mobile Edition 2010 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

Online
Meeting
Microsof Add-in

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


Online
Meeting
Microsof Add-in

View contact ● ● ● ● ●
list

Online
Meeting
Microsof Add-in

Display ● ●
alternate
contact views
(for example,
tile)

Instant Messaging (IM) Support in Lync Server 2010 Clients

Online
Meeting
Microsof Add-in

Initiate IM with ● ● ●
a contact

Navigate ● ● ●
among multiple
IM
conversations

Log IM ● ●
conversations
in Outlook

10


Online
Meeting
Microsof Add-in

Initiate an ● ● ●
email to a
contact

Use prepared ●
conversation
templates

Conferencing Support in Lync Server 2010 Clients

Online
Microsoft Meeting
Microsoft Microsoft Microsoft Microsoft Lync 2010 Add-in for
Microsoft Lync Web Lync 2010 Lync 2010 Lync 2010 Phone Microsoft
Feature/capability Lync 2010 App Attendee Attendant Mobile Edition Lync 2010

Add computer ● ● ● ● ●
audio

Add video ● ●

Use in-meeting ● ● ●
presenter
controls

Access detailed ● ● ● ●
meeting roster

Participate in ● ● ● ● ●
multiparty IM

Share the ● ● ●
desktop (if (requires
enabled) plug-in)

Share an ● ● ●
application (if (requires
enabled) plug-in)

Add anonymous ● ● ●

11


Online
Microsoft Meeting

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

Online
Microsoft Meeting

Initiate a voice call ● ● ● ●

Click to call a ● ● ● ●
contact

Manage call ● ● ● ●
forwarding

Manage team call ● ●
settings

Manage delegates ● ●

Initiate a call to a ● ●
Response Group

12


Online
Microsoft Meeting

Initiate a voice call ● ● ● ●

Emergency ● ●
services support

Connect to voice ● ● ● ●
mail

Make calls on ●
behalf of another
contact
(manager/delegate
scenario)

Online
Microsoft Meeting

Handle another's ● ● ● ●
calls if configured
as a delegate

Manage a high ●
volumes of calls

External User Support in Lync Server 2010 Clients

Online
Microsoft Meeting

Initiate IM with a ● ● ●
public contact

Initiate IM with a ● ● ●
federated
contact

13


Online
Microsoft Meeting

Conduct two- ● ● ● ●
party or
multiparty calls
with external
users

14


Mobile Access Support in Lync Server 2010 Clients

Online
Microsoft Meeting

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

Online
Microsoft Meeting

Client-side ● ●
archiving

Client-side ●
recording

15


Client System Requirements
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
32 bits per pixel

16



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);
• Media bypass: 80 kbps (minimum);
Video:
• CIF: 50 kbps (minimum); 210 kbps
(typical); 250 kbps (maximum)
• VGA: 350 kbps (minimum); 500
kbps (typical); 600 kbps (maximum)
• 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 (typical); 200 kbps
(maximum)
• Application Sharing: 256 kbps
(minimum); 1 Mbps (typical); 3.5 Mbps
(maximum)
Typical bandwidth values are measurements of
typical activity levels under good network

17



conditions (for example, with no forward error
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

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 Internet Internet Internet
system Explorer 8 Explorer 7 Explorer 6 Firefox 3.X Safari 5.X Safari 4.X

Windows 7 Yes Yes Yes
(32-bit and
64-bit)

Windows Yes Yes Yes
Vista Service
Pack 2 (SP2)
(32-bit and
64-bit)

Windows XP Yes Yes Yes Yes
SP3 (32-bit)

Windows XP Yes Yes Yes Yes
SP2 (64-bit)

Windows Yes Yes
Server 2008
R2

Windows Yes Yes Yes
Server 2003
(except
IA-64)

Windows Yes Yes
Server 2000
SP4

Mac OS Yes Yes
10.4.8+ (Intel-
based)

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
Help menu text item in the Help menu. Both HelpMenuText

21


Group Policy setting Description

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_CUSoftwareMicrosoftSharedUcClientServerAddressInt
ernal

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_CUSoftwareMicrosoftSharedUcClientServerAddressInt
ernal.

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 Lync Server 2010 in-band
2007 R2 Group Policy setting provisioning setting Description

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

PortrangeMaxMediaPort ucMaxMediaPort When combined with the
ucMinMediaPort, specifies
the range of ports used for
media. The recommended
minimum is 40 ports.

PortrangeMinMediaPort 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

Client Configuration Overview
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

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
• Migrating User Settings to Lync Server 2010
• 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
Archiving policy and configuration

25


Group Client settings and policies

Security Registrar authentication
Web services policies
Dial-in personal identification number (PIN)
policy

Network Configuration (not discussed in this Includes bandwidth management and
topic) 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.

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

26

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

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.

27

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

Number range NumberRangeStart, NumberRangeEnd

FQDN of destination server CallParkServiceFQDN

28

Voice Features: Unassigned Number Options

Option CSUnassignedNumber parameter

Name Identity

Number range NumberRangeStart, NumberRangeEnd

Announcement service (ExchangeUM or Not applicable
Announcement)

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

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

29

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.

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.

30

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 AllowExternalUsersToRecordMeetings
record

Audio/video

Audio/video AllowIPAudio, AllowIPVideo

Enable PSTN conference dial-in EnableDialInConferencing

Allow anonymous users to dial out AllowAnonymousUsersToDialOut

Maximum video resolution allowed for MaxVideoConferenceResolution
conferencing

Data Collaboration

Enable data collaboration EnableDataCollaboration

Allow federated and anonymous participants to AllowExternalsUsersToSaveContent
download content

Allow participants to transfer files EnableFileTransfer

Enable annotations AllowAnnotations

Enable polls AllowPolls

Application Sharing

Enable application sharing AllowUserToScheduleMeetingsWithAppSharing

Allow participants to take control AllowParticpantControl

Allow federated and anonymous users to take AllowExternalUserControl
control

Participant Policy

Disable application and desktop sharing EnableDesktopSharing: None

Enable application sharing EnableDesktopSharing: SingleApplication

Enable application and desktop sharing EnableDesktopSharing: Desktop

31


Option CSConferencingPolicy parameter

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 DesignateAsPresenter
Everyone)

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.

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

32


Option CSPinPolicy parameter

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

33


Option CsAccessEdgeConfiguration parameter

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 VerificationLevel: UseSourceVerification
with users verified by this provider

Verification level: Allow communications only VerificationLevel: AlwaysUnverifiable
with users on recipients’ contact lists

Verification level: Allow all communications with VerificationLevel: AlwaysVerifiable
this provider

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 Action
URL)

Action (OC user agent only): same as above, Action
plus Allow with upgrade and Block with
upgrade)

URL ActionURL

Client Version Configuration

36

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 EnableCDR
(CDRs)

Enable purging of call detail recordings (CDRs) EnablePurging

Keep call detail data for maximum duration KeepCallDetailForDays

37


Option CSCdrConfiguration parameter

(days)

Keep error report data for maximum duration KeepErrorReportForDays
(days)

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 EnableQoE
(QoE) data

Enable purging of Quality of Experience (QoE) EnablePurging
data

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

Planning for clients and devices lync server 2010 (rc)

Planning for clients and devices lync server 2010 (rc)

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Similar a Planning for clients and devices lync server 2010 (rc)

Similar a Planning for clients and devices lync server 2010 (rc) (20)

Último

Último (20)

Planning for clients and devices lync server 2010 (rc)