Download.microsoft.com



[pic]

 

Microsoft Lync Server 2010 Client and Device Deployment Guide

Microsoft Lync Server 2010

Published: March 2012

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.

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.

Copyright © 2012 Microsoft Corporation. All rights reserved.

Contents

Deploying Clients and Devices 1

Configure the Meeting Join Page 1

Deploying Lync 2010 and the Online Meeting Add-in for Lync 2010 2

Preparing to Install Lync 2010 3

Configuring Client Bootstrapping Policies for Lync 2010 3

Configuring Key Server Settings for Lync 2010 4

Configuring Supported Client Versions 5

Installing Lync 2010 5

IT-Managed Installation of Lync 2010 5

User-Managed Installation of Lync 2010 7

Verifying Lync 2010 Installation 7

Uninstalling Lync 2010 8

Configuring Enhanced Presence Privacy Mode 8

Customizing Lync 2010 9

Adding Commands to Lync 2010 Menus 10

Integrating a Third-Party Collaboration Application with Lync 2010 13

Configuring Custom Presence States 18

Customizing the Lync 2010 Help Menu 19

Adding a Custom Link to Lync 2010 Error Messages 20

Adding Custom Text to Instant Messages 21

Starting Lync 2010 from Another Application 21

Customizing the Online Meeting Add-in for Lync 2010 23

Lync 2010 Compatibility 25

Lync 2010 Integration 30

Deploying Lync 2010 Attendant 37

IT-Managed Installation of Lync 2010 Attendant 38

User-Managed Installation of Lync 2010 Attendant 39

Lync 2010 Attendant Group Policy 40

Deploying Lync 2010 Attendee 42

Deploying Lync 2010 Group Chat 43

Overview of Lync 2010 Group Chat Planning and Deployment 44

Lync 2010 Group Chat Terminology and Concepts 44

Lync 2010 Group Chat Group Policy 46

Preparing to Install Lync 2010 Group Chat 48

System Requirements for Lync 2010 Group Chat Computers 48

Software Requirements for Lync 2010 Group Chat Installation 49

Lync 2010 Group Chat and Privacy Mode 49

Installing Lync 2010 Group Chat 50

Configuring Lync 2010 Group Chat to Connect to Lync Server 2010, Group Chat 50

Configure Lync 2010 Group Chat Automatically 50

Configure Lync 2010 Group Chat Manually 51

Uninstalling Lync 2010 Group Chat 52

Instant Messaging with Lync 2010 Group Chat and Lync 2010 52

Additional Resources for Lync 2010 Group Chat 53

Deploying Lync 2010 Phone Edition 53

Checklist for Deploying Lync 2010 Phone Edition 54

Using DHCP to Assign IP Addresses to Devices 56

Using DHCPUtil 58

Configuring DHCP Options to Enable Sign-in for IP Phones 68

Using NTP to Set the Correct Time and Date for Devices 71

Provisioning IP Phones 72

Setting Up Authentication on the New IP Phones 72

Configuring Common Area Phones 73

Configuring the New IP Desk Phones 77

Certificates for Lync 2010 Phone Edition 77

Configure Enhanced 9-1-1 80

Configure an E9-1-1 Voice Route 81

Create Location Policies 82

Configure Site Information for E9-1-1 84

Add a Location Policy to a Network Site 84

Associate Subnets with Network Sites for E9-1-1 85

Configure the Location Database 85

Populate the Location Database 85

Validate Addresses 88

Publish the Location Database 88

Configure Advanced E9-1-1 Features 89

Configure an SNMP Application 89

Configure a Secondary Location Information Service 89

Setting Up the Authentication PIN for IP Phones 90

End-User Documentation about Lync 2010 Phone Edition 90

Device Update Web Service 90

Appendix: Configuring DHCP Options on DHCP Servers other than Windows DHCP Server 91

Deploying Lync Web App 93

Deploying Mobile Clients 93

Deploying Lync for Windows Phone 94

Installing Lync for Windows Phone 94

Removing Lync for Windows Phone 95

Deploying Lync for Android 95

Installing Lync for Android 95

Removing Lync for Android 96

Deploying Lync for iPhone and iPad 96

Installing Lync for iPhone and iPad 96

Removing Lync for iPhone and iPad 97

Deploying Lync for Nokia 97

Installing Lync for Nokia 97

Removing Lync for Nokia 99

Deploying Clients and Devices

This section outlines the procedures for deploying Microsoft Lync Server 2010 clients and devices.

In This Section

• Configure the Meeting Join Page

• Deploying Lync 2010 and the Online Meeting Add-in for Lync 2010

• Deploying Lync 2010 Attendant

• Deploying Lync 2010 Attendee

• Deploying Lync 2010 Group Chat

• Deploying Lync 2010 Phone Edition

• Deploying Lync Web App

• Deploying Mobile Clients

See Also

Planning for Clients and Devices in Lync Server 2010

Configure the Meeting Join Page

You can control the Microsoft Lync Server 2010 clients that are available for joining scheduled Lync Server 2010 meetings by configuring the meeting join page. When a user clicks a meeting link in a meeting request, the meeting join page detects whether a Lync Server client is already installed on the user’s computer. If a client is already installed, the default client opens and joins the meeting. If a client is not installed, the meeting join page displays options for joining the meeting with alternate clients.

The meeting join page always contains the option to use Microsoft Lync Web App. In addition to this option, you can decide whether to show links for downloading Microsoft Lync 2010 Attendee or using a previous version of Microsoft Office Communicator (Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007).

The meeting join scenarios are as follows:

• If Microsoft Lync 2010 or Microsoft Lync 2010 Attendant is installed, the client starts and joins the meeting.

• If neither Lync 2010 nor Lync 2010 Attendant is installed and Lync 2010 Attendee is installed, Lync 2010 Attendee starts and joins the meeting.

• If no Lync Server client is installed, the meeting join page opens and gives the user the following options:

• Use Lync Web App.

• Download Lync 2010 Attendee. (This link is hidden by default.)

• Use a previous version of Office Communicator. (This link is hidden by default.)

For the scenario in which no client is installed, you can configure the meeting join page by using the Microsoft Lync Server 2010 Control Panel (the Web Service page in the Security group). You can also configure the same settings by using the New-CsWebServiceConfiguration or Set-CsWebServiceConfiguration Lync Server Management Shell cmdlets with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters.

[pic]To configure the meeting join page by using the Lync Server 2010 Control Panel

|1. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the |

|different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools. |

|2. In the left navigation bar, click Security. |

|3. Click Web Service. |

|4. Select or clear the Show Lync Attendee download link check box, depending on whether you want to give users the option |

|to download and join meetings by using Lync 2010 Attendee. |

|5. Select or clear the Show the link for user to join meeting using legacy client check box, depending on whether you want|

|users to be able to join meetings by using a previous version of Communicator. |

[pic]To configure the meeting join page by using Lync Server Management Shell

|1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then |

|click Lync Server Management Shell. |

|2. Run the following cmdlet: |

|Get-CsWebServiceConfiguration |

|This cmdlet returns the web service configuration settings. |

|3. Run the following command, with the ShowDownloadCommunicatorAttendeeLink and ShowJoinUsingLegacyClientLink parameters |

|set to True or False, depending on your preference (for details about the parameters for this cmdlet, see the Lync Server |

|Management Shell documentation): |

|Set-CsWebServiceConfiguration -Identity global -ShowDownloadCommunicatorAttendeeLink $True -ShowJoinUsingLegacyClientLink |

|$True |

Deploying Lync 2010 and the Online Meeting Add-in for Lync 2010

The topics in this section describe how to deploy Microsoft Lync 2010 in your organization. The Online Meeting Add-in for Microsoft Lync 2010, which supports meeting management from within the Microsoft Outlook messaging and collaboration client, installs automatically with Lync 2010.

These topics assume that you have already completed a fresh installation of Microsoft Lync Server 2010 or a migration from a previous version of Microsoft Office Communications Server (Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007).

In This Section

• Preparing to Install Lync 2010

• Installing Lync 2010

• Uninstalling Lync 2010

• Configuring Enhanced Presence Privacy Mode

• Customizing Lync 2010

• Customizing the Online Meeting Add-in for Lync 2010

• Lync 2010 Compatibility

• Lync 2010 Integration

See Also

Planning for Clients and Devices in Lync Server 2010

Preparing to Install Lync 2010

Before you install Microsoft Lync 2010 on users’ computers, follow the steps described in this section.

In This Section

• Configuring Client Bootstrapping Policies for Lync 2010

• Configuring Key Server Settings for Lync 2010

• Configuring Supported Client Versions

Configuring Client Bootstrapping Policies for Lync 2010

Before you deploy Microsoft Lync Server 2010 clients, you should check and, if necessary, configure the policies and in-band provisioning settings described in Key Client Policies and Settings in the Planning documentation.

There are several client bootstrapping policies that you should configure before users sign in to the server for the first time. 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. One way to define Group Policy settings is by using an administrative template (.adm) file, which contains specific information about the Group Policy settings the client implements, where policies are stored, and how to configure policies.

Policies configured on the server take precedence over Group Policy settings and client options configured by the user. The following table summarizes the order in which settings take precedence when a conflict occurs.

Group Policy Precedence

|Precedence |Location or Method of Setting |

|1 |Lync Server 2010 in-band provisioning |

|2 |HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator |

|3 |HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator |

|4 |The Lync - Options dialog box in Microsoft Lync 2010 |

[pic]To define Group Policy settings by using the Lync 2010 administrative template file

|1. Download the Microsoft Lync 2010 Client Group Policy Documentation from the Microsoft Download Center at |

|. Copy the Communicator.adm file to the %windir%/inf folder. |

|2. Use the Microsoft Management Console (MMC) Group Policy Object Editor to enable or disable specific policy settings. |

|[pic]Note: |

|You can deploy Lync 2010 Group Policy without affecting users who are running previous versions of Microsoft Office |

|Communicator (Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007). |

Configuring Key Server Settings for Lync 2010

In addition to client bootstrapping policies, there are certain essential Microsoft Lync Server 2010 settings that can significantly impact client functionality and should be configured before client deployment. You can use Lync Server Management Shell cmdlets to modify these settings.

For details about these key settings, see Key Client Policies and Settings in the Planning documentation.

[pic]To use cmdlets to configure conferencing settings for Lync 2010

|1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then |

|click Lync Server Management Shell. |

|2. Run the following cmdlet: |

|Get –CsConferencingConfiguration |

|This cmdlet returns the conferencing configuration settings. |

|3. Run the following cmdlet with the parameters and values you want to change (for details about the parameters for this |

|cmdlet, see the Lync Server Management Shell documentation): |

|Set-CsConferencingConfiguration |

|[pic]Note: |

|You can create additional sets of conferencing configuration settings for specific sites. Use the New- |

|CsConferencingConfiguration cmdlet with a site identity. When you create new conferencing configuration settings for |

|sites, the site settings take precedence over the global settings. For details, see the Lync Server Management Shell |

|documentation. |

See Also

Configuring Client Bootstrapping Policies for Lync 2010

Configuring Supported Client Versions

In Microsoft Lync Server 2010, you can set up client version policies to specify the versions of Lync Server 2010 clients that are supported in your environment. Additionally, you can use the global client version configuration to specify a default action for clients that do not already have a version policy defined and, therefore, are not explicitly supported or restricted.

You can also use client version policies to manage Lync Server client updates. When you set a client version policy and use the options Allow and upgrade and Block and upgrade, clients will receive updated software from the Windows Server Update Service (if you are using this service) or from Microsoft Update.

See Also

Specify the Client Versions Supported in Your Organization

Modify the Default Action for Clients Not Explicitly Supported or Restricted

Installing Lync 2010

To deploy Microsoft Lync 2010, you can perform an IT-managed rollout or allow your end users to install Lync 2010 individually. The method you choose depends on the size and security requirements of your organization, the deployment methods you already have in place, and the experience level of your users, among other factors. The following sections discuss these methods in more detail.

In This Section

• IT-Managed Installation of Lync 2010

• User-Managed Installation of Lync 2010

• Verifying Lync 2010 Installation

IT-Managed Installation of Lync 2010

Microsoft Lync 2010 setup files are provided as executable (.exe) programs. The Lync 2010 setup executable program is the recommended method for installing clients because it performs the following actions:

• Checks for prerequisites, and informs the user of applications that must close

• Installs the required versions of Microsoft Visual C++ components and the Microsoft Silverlight browser plug-in

• Uninstalls Microsoft Lync 2010 Attendee

• Uninstalls previous versions of Microsoft Office Communicator (Microsoft Office Communicator 2007 R2 and Microsoft Office Communicator 2007)

• Uninstalls previous versions of the Office Communicator multi-user language pack

• Notifies the user that Windows Media Player 11 must be installed for recording features to work properly

You can deploy Lync 2010 in a managed-desktop environment by using the following methods:

• Microsoft Systems Management Server (SMS) 2003 or Microsoft System Center Configuration Manager 2007 R2. Use these products for more complex software installation scenarios, where scheduling, inventory, reporting, status, and support for an installation across a wide area network (WAN) are required. For details, see the System Center TechNet Library at .

• Windows logon script. The logon script performs an unattended installation of Lync 2010 when a user logs on. You can use Group Policy objects to direct logon scripts to specific devices or users.

• Active Directory Domain Services (AD DS) Group Policy. You can create a Group Policy object to deploy Lync 2010 to specific users or computers based on group memberships. For details about how to use Group Policy, see the Windows Server Group Policy TechNet Library at . If you want to use Group Policy to deploy clients, you must extract the Windows Installer (.msi) file from the executable program and use the Group Policy setting UseMSIForLyncInstallation to allow the .msi to run on client computers. Because the .exe setup program performs additional checks and software updates, you must also address all other actions listed previously that are typically performed by the .exe setup program.

[pic]Note:

You can extract the .msi file by running the client installation executable on a supported Windows client, which creates the Lync.msi file in %Program Files%\OCSetup\Lync.msi or %Program Files(x86)%\OCSetup\Lync.msi. For details and additional required steps, see Microsoft Knowledge Base article 2477965, “The installation of Lync 2010 by using Windows Installer (MSI) fails,” at .

Installing on Computers with Multiple Users

After Lync 2010 is installed on an individual computer, it is available to all users of that computer. Lync 2010 cannot be installed on a per-user basis on an individual computer.

Lync 2010 Setup Command-Line Arguments

When using a script to deploy Lync 2010, you can use the Lync 2010 setup program command-line arguments listed in the following table.

[pic]Note:

You must be logged on as a member of the Administrators group in order to install Lync 2010.

|Command-Line Argument |Description |

|/Silent |Suppresses the installation user interface, and uses default |

| |values for other installation options (for example, installation |

| |directory). This argument can be used along with the /Install, |

| |/Uninstall, and /Repair arguments. |

|/Install |(Default) Installs the client. |

|/Uninstall |Removes previous versions of Office Communicator and add-ins. |

|/Repair |Reinstalls the client to repair any installation issues. |

|/InstallDir |Specifies the installation directory. |

|/help |Displays the Help text in a dialog box. |

|/reg:[FileName] |Registers the settings in the specified file during installation.|

| |This registry file is then used during run time. |

|/uninstalladdin |Removes the Conferencing Add-in for Microsoft Office Outlook, |

| |which is the previous version of the add-in (used for scheduling |

| |Microsoft Office Live Meeting server- and service-based |

| |meetings). |

|/fulluisuppression |Enables Lync 2010 to run in user interface suppression mode. |

User-Managed Installation of Lync 2010

You can deploy Microsoft Lync 2010 in your organization by using a file server on your network as a software distribution point for the Lync 2010 setup files. At rollout time, you can send an email to users explaining the installation process and provide a link to the distribution point.

See Also

IT-Managed Installation of Lync 2010

Verifying Lync 2010 Installation

Verifying Lync 2010 Installation

To complete a quick check of address book and telephony integration on a client computer, locate a contact name, and then try to send an instant message to the contact or call the contact from within Microsoft Lync 2010.

Uninstalling Lync 2010

You can uninstall Microsoft Lync 2010 manually or by using a script. For details about command-line arguments, see IT-Managed Installation of Lync 2010.

[pic]Important:

If you want to use a script with the /uninstalladdin argument to remove previous versions of the add-in, be sure to precede it with a command that closes Microsoft Outlook. If Outlook is open on the user’s computer, the add-in will fail to uninstall.

[pic]To uninstall Lync 2010 manually

|1. Log on to your computer as a member of the Administrators group. |

|2. Click Start, click Control Panel, and then click Programs and Features. |

|3. Click Microsoft Lync 2010. |

|4. Click Uninstall at the top of the window. |

Configuring Enhanced Presence Privacy Mode

With enhanced presence privacy mode, users can restrict their presence information so that it is visible only to the contacts listed in their Microsoft Lync 2010 Contacts list. The CsPrivacyConfiguration Lync Server Management Shell cmdlet EnablePrivacyMode parameter controls this option. When EnablePrivacyMode is set to True, the option to restrict presence information to contacts becomes available in the Lync 2010 Status options. When EnablePrivacyMode is set to False, users can choose either to always allow everyone to see their presence information or to adhere to any future changes the administrator makes to the privacy mode.

[pic]Important

Lync 2010 privacy settings are not honored by previous versions (Microsoft Office Communicator 2007 R2 or Microsoft Office Communicator 2007). If previous versions of Office Communicator are allowed to sign in, a Lync 2010 user’s status, contact information, or picture could be viewed by someone who has not been authorized to view it. Additionally, a Lync 2010 user’s privacy settings are reset if he or she later signs in with previous version of Communicator.

For these reasons, in a migration scenario, before you enable Lync 2010 enhanced presence privacy mode:

Ensure that every user has Lync 2010 installed.

Define a client version policy rule to prevent previous versions of Communicator from signing in.

[pic]To enable enhanced presence privacy mode

|1. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then |

|click Lync Server Management Shell. |

|2. Run the following command: |

|Get-CsPrivacyConfiguration | Set-CsPrivacyConfiguration -EnablePrivacyMode $True |

|This command enables privacy mode for all the privacy configuration settings currently in use in the organization. |

Customizing Lync 2010

This section describes how to use client policies and XML files to add the following custom features to Microsoft Lync 2010:

• Menu commands that pass contextual information to an external application

• Presence states specific to your organization

• Help menu modifications that link to your organization’s version of Lync 2010 Help

• A Help or troubleshooting link that appears at the end of every Lync 2010 error message

• Warnings or disclaimers that appear in the Conversation window at the start of an instant messaging (IM) session

[pic]Important

Lync 2010 does not support adding custom tabs to the Lync main window. Feedback from customers and developers indicated that using a custom command to pass contextual information to an external application was a more usable and more discoverable integration option for end users.

For details about adding custom commands to Lync 2010, see Adding Commands to Lync 2010 Menus and Integrating a Third-Party Collaboration Application with Lync 2010.

This section also describes how to initiate a Lync 2010 conversation from another application by using Lync 2010 command-line parameters.

For details about additional ways to customize Lync 2010, see the resources listed in the following table.

|To do this |Use this tool |Find out more |

|Add Lync 2010 functionality to a |Lync Controls |“Lync Controls” in the Microsoft Lync 2010 SDK at |

|custom application | | |

|Integrate a web application with |Lync Extensibility window |“Launching Applications in the Lync Extensibility Window” in |

|the Lync Conversation window | |the Lync SDK at |

|Automate the Lync 2010 user |Microsoft Lync 2010 API |“Extensibility API Concepts” in the Lync SDK at |

|interface from another |Automation class | |

|application | | |

|Modify Lync 2010 behavior, |Microsoft Lync Server 2010 |Lync Server Management Shell documentation |

|available features, and default |management tools | |

|settings | | |

In This Section

• Adding Commands to Lync 2010 Menus

• Integrating a Third-Party Collaboration Application with Lync 2010

• Configuring Custom Presence States

• Customizing the Lync 2010 Help Menu

• Adding a Custom Link to Lync 2010 Error Messages

• Adding Custom Text to Instant Messages

• Starting Lync 2010 from Another Application

Adding Commands to Lync 2010 Menus

You can add custom commands to Microsoft Lync 2010 menus and pass the SIP Uniform Resource Identifier (URI) of the current user and selected contacts to the application that the custom command starts.

The custom commands that you add can appear on one or more of the following menus:

• The Tools menu, on the menu bar in the Lync main window

• The shortcut menu for contacts in the Contacts list

• The Actions menu, on the menu bar, in the Conversation window

• The shortcut menu for people listed in the Conversation window participant list

• The options menu in a contact card

You can define custom commands for two types of applications—applications that do either of the following:

• Apply only to the current user and are started on the local computer.

• Involve additional users, such as an online collaboration program, and must be started on each user's computer.

The custom command can be invoked in the following ways:

• Select one or more users, and then choose the custom command.

• Start a two-party or multiparty conversation, and then choose the custom command.

To add a custom command

Use the registry settings in the following table to add a command to the Lync 2010 menus. These entries are placed in the registry at the following locations:

• For 64-bit operating systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Communicator\SessionManager\Apps

• For 32-bit operating systems:

HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps

Custom Command Registry Entries

|Name |Type |Data |

|Name |REG_SZ |Name of the application as it appears on the menu. |

|ApplicationType |DWORD |0 = Executable (default) |

| | |[pic]Note: |

| | |Requires ApplicationInstallPath. |

| | |1 = Protocol |

|ApplicationInstallPath |REG_SZ |Full path of the executable. |

| | |[pic]Note: |

| | |Must be specified if ApplicationType is 0 |

| | |(Executable). |

|Path |REG_SZ |Full path to be started along with any parameters, |

| | |including the default parameters %user-id% and |

| | |%contact-id%. |

|SessionType |DWORD |0 = Local session. The application is started on the|

| | |local computer. |

| | |1 = Two-party session (default). Lync 2010 starts |

| | |the application locally and then sends a desktop |

| | |notification to the other user. The other user |

| | |clicks the notification to start the application on |

| | |their computer. |

| | |2 = Multiparty session. Lync 2010 starts the |

| | |application locally and then sends desktop |

| | |notifications to the other users. The other user |

| | |clicks the notification to start the specified |

| | |application on his or her computer. |

|ExtensibleMenu |REG_SZ |A list of the menus where this command will appear, |

| | |separated by semi-colons. Possible values are: |

| | |MainWindowActions |

| | |MainWindowRightClick |

| | |ConversationWindowActions |

| | |ConversationWindowRightClick |

| | |ContactCardMenu |

| | |If ExtensibleMenu is not defined, the default values|

| | |of MainWindowRightClick and |

| | |ConversationWindowActions are used. |

For example, the following Registry Editor (.REG) file shows the results of adding a Contoso Sales Contact Manager menu item to Actions menu in the Conversation window:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps\{1F9F07C6-7E0B-462B-AAD7-98C6DBEA8F69}]

"Name"="Contoso Sales Contact Manager"

"HelpMessage"="The Contoso Sales Contact Manager is not installed. Contact the Help Desk for more information."

"ApplicationType"=dword:00000000

"ApplicationInstallPath"="C:\\cscm.exe"

"Path"="C:\\cscm.exe %user-id% %contact-id%"

"SessionType"=dword:00000001

"ExtensibleMenu"="ConversationWindowActions;MainWindowRightClick"

To access a custom command

To access a custom command after it is added, do one of the following, depending on the ExtensibleMenu values you define:

• MainWindowActions   In the Lync main window, press the Alt key to show the menu bar, click Tools, and then click your custom command.

• MainWindowRightClick   In the Lync main window, right-click a contact, and then click your custom command.

• ConversationWindowActions   In the Conversation window, press the Alt key to show the menu bar, click Actions, and then click your custom command.

• ConversationWindowRightClick   In the Conversation window, right-click a contact name, and then click your custom command.

• ContactCardMenu   In a person’s contact card, click the options menu [pic], and then click your custom command.

Integrating a Third-Party Collaboration Application with Lync 2010

You can integrate Microsoft Lync 2010 with any third-party online collaboration application by adding the same registry settings as those used by Microsoft Office Live Meeting 2007.

The integration process described in this topic is the one used for Office Live Meeting 2007. Therefore, some steps might not apply to other online collaboration applications.

You can use Lync 2010 to start data conferencing sessions hosted on an in-house server, an Internet-based service, or both. The collaboration or data conferencing session can be started from the Contacts list or from an existing instant messaging, voice, or video session. Lync 2010 acts only as the vehicle for starting the application. Any existing Lync 2010 conversations remain active after the online collaboration session has begun.

The following sections describe how Lync 2010 is integrated with Internet-based and server-based collaboration applications.

Integrating an Internet-Based Collaboration Application with Lync 2010

Generally, the steps involved in integrating a third-party collaboration application are as follows:

1. Information about the application is added to the registry.

2. The organizer signs in to Lync 2010 and selects contacts for data sharing and collaboration. Or, the organizer may already be in a conversation and decide to add data conferencing.

3. Lync 2010 reads the registry, starts the collaboration application, and then sends a custom SIP message—an appINVITE—to the selected participants.

4. Participants accept the invitation, and the collaboration application is started on each person’s computer. Lync 2010 uses the registry to determine which collaboration application to use, and then starts that application by using the parameters included in the appINVITE message.

The following table describes the registry entries required to integrate an Internet-based collaboration application with Lync 2010. These entries are placed in the registry in the following locations:

• For 64-bit operating systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Communicator\SessionManager\Apps

• For 32-bit operating systems:

HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps

Registry Entries for an Internet-based Collaboration Application

|Name |Type |Data |

|Name |REG_SZ |The application name for Lync 2010 menus. |

|SmallIcon |REG_SZ |Path to 16-pixel x 16-pixel icon, BMP or PNG. |

|LargeIcon |REG_SZ |Path to 28-pixel x 28-pixel icon, BMP or PNG. |

|Path |REG_SZ |Participant path for starting the online collaboration application. |

|OriginatorPath |REG_SZ |Organizer path for starting the online collaboration application. This path can contain one or |

| | |more custom parameters as defined in the Parameters subkey. For example, |

| | | |

|SessionType |DWORD |0 = Local session. The application is started on the local computer. |

| | |1 = Two-party session (default). Lync 2010 starts the application locally, and then sends a system|

| | |notification to the other user. The other user clicks the notification and starts the specified |

| | |application on their computer. |

| | |2 = Multiparty session. Lync 2010 starts the application locally, and then sends system |

| | |notifications to the other users, prompting them to start the specified application on their own |

| | |computer. |

|LiveServerIntegratio|DWORD |0 or not present = The application has its own conferencing mechanisms and does not require |

|n | |Microsoft Office Communications Server 2007 R2 (default). |

| | |1 = Integrates with an in-house server. |

|ApplicationType |DWORD |1 = Sets the application type to protocol. The other possible values do not apply in this case. If|

| | |not present, ApplicationType is set to 0 (executable). |

|ExensibleMenu |REG_SZ |A list of the menus where this command will appear, separated by semi-colons. Possible values are:|

| | | |

| | |MainWindowActions |

| | |MainWindowRightClick |

| | |ConversationWindowActions |

| | |ConversationWindowRightClick |

| | |ContactCardMenu |

| | |If ExtensibleMenu is not defined, the default values of MainWindowRightClick and |

| | |ConversationWindowActions are used. |

|ButtonPriority |DWORD |0 = Application is displayed on the button (default). |

The following table describes the registry entries for parameters. These entries are place at HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\Parameters.

Registry Entries for an Internet-based Collaboration Application

|Name |Type |Data |

|Param1 |REG_SZ |Used in tokenized format (%Parm1%) to add |

| | |user-specific values to the OriginatorPath |

| | |registry key. |

|Param2 |REG_SZ |See Param1. |

|Param3 |REG_SZ |See Param1. |

The following example registry settings integrate ADatum Collaboration Client with Lync 2010:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps\{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}]

"Path"=""

"OriginatorPath"=""

"SessionType"=dword:00000002

"ApplicationType"=dword:00000001

"LiveServerIntegration"=dword:00000000

"Name"="ADatum Online Collaboration Service"

"Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWindowActions;ConversationWindowRightClick"

[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager]

[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps]

[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\Parameters]

[HKEY_CURRENT_USER\Software\Microsoft\Communicator\SessionManager\Apps\Parameters\{C3F6E17A-855F-44a0-B90D-C0B92D38E5F1}]

"Param1"="meetserv"

"Param2"="admin"

"Param3"="abcdefg123"

Integrating a Server-Based Collaboration Application with Lync 2010

The settings to add commands for starting a server-based collaboration application from within Lync 2010 are similar to those described in the previous section, Integrating an Internet-Based Collaboration Application with Lync 2010. However, the OriginatorPath is not required, and some values are changed. Registry entries are placed in the following locations:

• For 64-bit operating systems:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Communicator\SessionManager\Apps

• For 32-bit operating systems:

HKEY_LOCAL_MACHINE\Software\Microsoft\Communicator\SessionManager\Apps

Registry Entries for a Server-based Collaboration Application

|Name |Type |Data |

|Name |REG_SZ |Name of the application as it appears on the menu. |

|ApplicationType |DWORD |Value = 1. Sets the application type to protocol. |

| | |The other possible values do not apply in this case.|

| | |If not present, ApplicationType is set to 0 |

| | |(executable). |

|Path |REG_SZ |Protocol used to start the collaboration |

| | |application. For Live Meeting 2007 the value of Path|

| | |is set to meet:%conf-uri%. |

|SessionType |DWORD |0 = Local session. The application is started on the|

| | |local computer. |

| | |1 = Two-party session (default). Lync 2010 starts |

| | |the application locally, and then sends a system |

| | |notification to the other user. The other user |

| | |clicks the notification and starts the specified |

| | |application on their computer. |

| | |2 = Multiparty session. Lync 2010 starts the |

| | |application locally, and then sends system |

| | |notifications to the other users, prompting them to |

| | |start the specified application on their computer. |

|LiveServerIntegration |DWORD |1 = Hosted on the in-house server. |

|MCUType |REG_SZ |DATA = The type of server. |

|ExtensibleMenu |REG_SZ |A list of the menus where this command will appear, |

| | |separated by semi-colons. Possible values are: |

| | |MainWindowActions |

| | |MainWindowRightClick |

| | |ConversationWindowActions |

| | |ConversationWindowRightClick |

| | |ContactCardMenu |

| | |If ExtensibleMenu is not defined, the default values|

| | |of MainWindowRightClick and |

| | |ConversationWindowActions are used. |

The following example adds commands to start ADatum Collaboration Client from within Lync 2010:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Communicator\SessionManager\Apps\{27877e66-615c-4582-ab88-0cb2ca05d951}]

"Path"="meet:%conf-uri%"

"SessionType"=dword:00000002

"LiveServerIntegration"=dword:00000001

"ApplicationType"=dword:00000001

"Name"="ADatum Collaboration Client"

"MCUType"="Data"

"Extensiblemenu"="MainWindowActions;MainWindowRightClick;ConversationWindowActions;ConversationWindowRightClick"

Configuring Custom Presence States

To define custom presence states in Microsoft Lync 2010, create an XML custom presence configuration file, and then specify its location by using the Lync Server Management Shell cmdlets New-CSClientPolicy or Set-CSClientPolicy with the parameter CustomStateURL.

Configuration files have the following properties:

• Custom presence states can be configured with the Available, Busy, and Do Not Disturb presence indicators.

• The availability attribute determines which presence indicator is associated with the status text of the custom state. In the example later in this topic, the status text Working from Home is displayed to the right of the green (Available) presence indicator.

• The maximum length of the status text is 64 characters.

• A maximum of four custom presence states can be added.

• Valid address types for the CustomStateURL parameter are FILE:, HTTP:, and HTTPS:.

Examples of valid addresses are as follows:







file://\\lspool.corp.\LSFileShare\ClientConfigFolder\Presence.xml

Localize your custom presence state by specifying one or more locale ID (LCID) schema in the XML configuration file. The example later in this topic shows localization into English - United States (1033), Norwegian - Bokmål (1044), French - France (1036), and Turkish (1055). For a list of LCIDs, see Locale IDs Assigned by Microsoft at .

To add custom presence states to Lync 2010

1. Create an XML configuration file that uses the format of the following example:

, description=Relative Path to the Lync Server Certificate Provisioning service

Using DHCPUtil.exe to obtain DHCP Option 120 and 43 values

To use DHCPUtil.exe to obtain the value for various sub-options for option 43, do the following:

1. Install Microsoft Visual C++ 2008 Redistributable Package (x86) to run DHCPUtil.exe for DHCP options.

2. At a command prompt, run:

DHCPUtil.exe -SipServer -WebServer -RunConfigScript

The Lync Server internal web FQDN is the FQDN of the web components that run on the Lync Server Front End pool. This is typically specified by using Topology Builder as part of the pool properties. If you do not use Domain Name System (DNS) load balancing for the pool, the Lync Server internal web FQDN is the same as the Lync Server pool FQDN.

Use the values generated by DHCPUtil.exe to configure your DHCP server. For example:

Sip Server FQDN: ocspool1.

Certificate Provisioning Service URL:

DHCP Option 120 Value:

00076578616D706C6503636F6D00

DHCP Option 43 Value:

Vendor Class Identifier: MS-UC-Client

Option 43 (for vendor=MS-UC-Client):

sub-option 1 : 4D532D55432D436C69656E74

sub-option 2 : 6874747073

sub-option 3 : 6F6373706F6F6C312E636F6E746F736F2E636F6D

sub-option 4 : 343433

sub-option 5 : 2F4365727450726F762F4365727450726F766973696F6E696E67536572766963652E73763

See Also

Configuring DHCP Options to Enable Sign-in for IP Phones

Deploying Lync Web App

Microsoft Lync Web App is an Internet Information Services (IIS) web client that installs with Microsoft Lync Server 2010 and is enabled by default. No additional steps are necessary to either enable Lync Web App on the server or deploy the web client to users. When users click a meeting URL, they are presented with the meeting join page, which provides the option to join the meeting by using Lync Web App.

Your main consideration during client deployment is whether to install the following software prerequisites for Lync Web App in advance or to allow users to install them as needed:

• The Microsoft Silverlight 4.0 browser plug-in is required for Lync Web App. You can deploy Silverlight 4.0 to client computers, or you can allow users to be prompted for installation when they first start Lync Web App.

• The sharing feature in Lync Web App requires a Microsoft ActiveX control. The first time users initiate a sharing session, they will be prompted to download the required ActiveX control.

See Also

Lync Web App Supported Platforms

Configure the Meeting Join Page

Deploying Mobile Clients

The topics in this section describe how to deploy mobile access clients for Lync Server 2010 in your organization.

In This Section

• Deploying Lync for Windows Phone

• Deploying Lync for Android

• Deploying Lync for iPhone and iPad

• Deploying Lync for Nokia

Deploying Lync for Windows Phone

This section describes how to deploy Microsoft Lync 2010 for Windows Phone for your mobile users.

In This Section

• Installing Lync for Windows Phone

• Removing Lync for Windows Phone

Installing Lync for Windows Phone

Microsoft Lync 2010 for Windows Phone is a user-installable application that is available in the Windows Phone Marketplace.

Installing Lync for Windows Mobile

You can instruct your users to install Lync 2010 for Windows Phone on their devices by directing them to the Windows Phone Marketplace at .

Verifying Mobile Client Installation

After you configure the client and sign in successfully, use the following tests to verify that your installation of Lync 2010 is working correctly on your mobile device.

[pic]Search for a contact in the corporate directory

|1. In the Contacts list, tap Search at the bottom. |

|2. Search for a contact that exists only in the global address list. |

|3. Verify that the contact name appears in the search results. |

[pic]Test IM and presence

|1. In the Contacts list, tap a contact. |

|2. In the contact card, tap the IM icon. |

|3. Verify that an IM window appears and you can type and send an IM. |

[pic]Test dial-out conferencing

|1. In Outlook, schedule a Lync meeting. |

|2. On the mobile device, open the meeting invitation. |

|3. Click the link in the meeting to join. |

|4. Answer the call from the conference service and verify that you are connected to meeting audio. |

[pic]Test push notifications

|1. On user A’s mobile device, sign in to Lync with user A’s account. |

|2. Open another application on the mobile device. |

|3. On a different client, sign in to Lync with user B’s account. |

|4. Send an IM from user B to user A. |

|5. Verify that the IM notification appears on user A’s mobile device. |

Removing Lync for Windows Phone

To remove the Microsoft Lync 2010 for Windows Phone application from the mobile device, perform the following steps:

1. On the mobile device, from the start screen, swipe to see the application list.

2. Tap and hold the Lync application, and then select Uninstall.

Deploying Lync for Android

This section describes how to deploy Microsoft Lync 2010 for Android for your mobile users.

In This Section

• Installing Lync for Android

• Removing Lync for Android

Installing Lync for Android

Microsoft Lync 2010 for Android is a user-installable application that is available in the Android Market.

Installing Lync for Android

You can instruct your users to install Lync 2010 for Android by directing them to the Market application from their phone. The Android Market is also available online at . .

Verifying Mobile Client Installation

After you configure the client and sign in successfully, use the following tests to verify that your installation of Lync 2010 is working correctly on your mobile device.

[pic]Search for a contact in the corporate directory

|1. In the Contacts list, tap Menu, and then tap Search. |

|2. Search for a contact that exists only in the global address list (GAL). |

|3. Tap Search the company directory. |

|4. Verify that the contact name appears in the search results. |

[pic]Test IM and presence

|1. In the Contacts list, tap a contact. |

|2. In the contact card, tap the IM icon. |

|3. Verify that an IM window appears and you can type and send an IM. |

[pic]Test dial-out conferencing

|1. In Outlook, schedule a Lync meeting. |

|2. On the mobile device, open the meeting invitation. |

|3. Click the link in the meeting to join. |

|4. Answer the call from the conference service and verify that you are connected to the meeting audio. |

Removing Lync for Android

To remove the Microsoft Lync 2010 for Android application from the mobile device, perform the following steps:

1. On the mobile device, open the tool for managing applications

2. Select the Lync application, and then select Uninstall.

Deploying Lync for iPhone and iPad

This section describes how to deploy Microsoft Lync 2010 for iPhone and Microsoft Lync 2010 for iPad for your mobile users.

In This Section

• Installing Lync for iPhone and iPad

• Removing Lync for iPhone and iPad

Installing Lync for iPhone and iPad

Microsoft Lync 2010 for iPhone and Microsoft Lync 2010 for iPad are user-installable applications that are available in the Apple App Store.

Installing Lync for iPhone and Lync for iPad

You can instruct your users to install Lync 2010 for iPhone and Lync 2010 for iPad by directing them to the App Store from their devices. The App Store for each device is also available online.

• Lync for iPhone is available in the App Store at < >

• Lync for iPad is available in the App Store at < >

Verifying Mobile Client Installation

After you configure the client and sign in successfully, use the following tests to verify that your Lync installation is working correctly on your mobile device.

[pic]Search for a contact in the corporate directory

|1. In the Contacts list, tap inside the search bar at the top, and begin typing the name of a contact that exists only in |

|the global address list (GAL). |

|2. Verify that the contact name appears in the search results. |

[pic]Test IM and presence

|1. In the Contacts list, tap a contact. |

|2. In the contact card, tap the IM icon. |

|3. Verify that an IM window appears and you can type and send an IM. |

[pic]Test dial-out conferencing

|1. In Outlook, schedule a Lync meeting. |

|2. On the mobile device, open the meeting invitation. |

|3. Click the link in the meeting to join. |

|4. Answer the call from the conference service and verify that you are connected to the meeting audio. |

[pic]Test push notifications.

|1. On user A’s mobile device, sign in to Lync with user A’s account. |

|2. Open another application on the mobile device. |

|3. On a different client, sign in to Lync with user B’s account. |

|4. Send an IM from user B to user A. |

|5. Verify that the IM notification appears on user A’s mobile device. |

Removing Lync for iPhone and iPad

To remove Microsoft Lync 2010 for iPhone or Microsoft Lync 2010 for iPad from the device, perform the following steps:

1. On the mobile device home screen, tap and hold the Lync icon.

2. When the tiles begin to shake and the X appears, tap the X to delete the application.

Deploying Lync for Nokia

This section provides information about how to deploy Microsoft Lync 2010 for Nokia to enable mobile phones to function as unified communications (UC) endpoints. Deployment of Lync 2010 for Nokia requires first deploying mobile access for Lync Server 2010, and then installing and configuring Lync 2010 for Nokia.

In This Section

• Installing Lync for Nokia

• Removing Lync for Nokia

Installing Lync for Nokia

Microsoft Lync 2010 for Nokia is distributed bundled with other Microsoft Office mobile applications. It is pre-installed on most Nokia smartphones. If it is not pre-installed, Microsoft Office mobile applications are also available in the Nokia Store. Users can download and install the Lync application on their phones. You can instruct your users to install Lync for Nokia on their devices by directing them to the Nokia store at .

Installing Lync for Nokia

Instruct your users to install Lync for Nokia on their devices from the Nokia store at .

[pic]To install directly to the phone

|1. From your phone, press the Menu key, and then click Nokia Store. |

|2. Locate Microsoft Office Apps, and then click Download to install the application on your phone. |

[pic]To install from the computer

|1. From your computer, go to , and sign in to your account. If you do not have an account, create |

|one first. |

|2. At the Nokia Store, search for “Lync.” In the search results, locate the Microsoft Apps bundle, which contains the Lync|

|for Nokia application. Click Send to mobile. |

|3. From your phone, open the link that was sent from the Nokia Store, and follow the instructions to install the |

|application. |

Verifying Mobile Client Installation

After you configure the client and sign in successfully, use the following tests to verify that your installation of Lync is working correctly on your mobile device.

[pic]Search for a contact in the corporate directory

|1. In the Contacts tab, tap the Search button in bottom toolbar. |

|2. Search for a contact that exists only in the global address list (GAL). |

|3. Verify that the contact name appears in the search results. |

[pic]Test IM and presence

|1. In the Contacts tab, expand a contact group, and select a contact. |

|2. In the contact card Send IM section, select the Lync ID of the contact. |

|3. Verify that an IM window appears and you can type and send an IM. |

[pic]Test dial-out conferencing

|1. In Outlook, schedule a Lync meeting. |

|2. On the mobile device, open the meeting invitation in the phone calendar. |

|3. Click the link in the meeting to join. |

|4. Answer the call from the conference service and verify that you are connected to the meeting audio. |

Removing Lync for Nokia

To remove Microsoft Lync 2010 for Nokia from the device, perform the following steps:

1. On the mobile device, press the Menu key to open the Applications Menu.

2. Select and hold the Lync application. In the pop-up menu, select Remove.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download