ConfiguringLync Server 2010to Support Communicator Mobile for Java and Communicator Mobile for Nokia

Date: 12/16/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.

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 © 2010 Microsoft Corporation. All rights reserved.

Microsoft, .NET, Active Directory, Lync, Office Communications Server, Office Communicator, SQL Server, Visual C++, Windows, Windows PowerShell, and Windows Server are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Table of Contents

1.Introduction

2.Download the Communicator Mobile component and prerequisites

3.(Option A) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environment that has been prepped with the Communications Server 2007 R2 schema

Install the prerequisites on the domain controller

Run the schema prep command

Ensure backward compatibility

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

Install the prerequisites on the server where the Communicator Mobile component will run

Install the server msi files

Install the updates for Communications Server 2007 R2

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

4.(Option B) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environment that has been prepped with the Lync Server 2010 schema

Install the prerequisites on the domain controller

Run the schema prep command

Run the schema prep

Ensure backward compatibility

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

Install the prerequisites on the server where the Communicator Mobile component will run

Install the server msi files

Install the updates for Communications Server 2007 R2

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

5.(Option C) Install the Communicator Mobile component on a topology that has been upgraded from Communications Server 2007 R2 to Lync Server 2010

Ensure backward compatibility

Install prerequisites on the computer where the Communicator Mobile component will run

Install the server msi files

Install the updates for Communications Server 2007 R2

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

6.Stop the Communicator Web Access apppool

If you’re running Windows Server 2008 SP2 with IIS 7

If you’re running Windows Server 2003 with IIS 6

7.Update the next-hop FQDN or certificates on the computer running Communicator Web Access

8.Uninstall the server running the Communicator Mobile component

1.Introduction

Microsoft® Office Communicator Mobile 2007 R2 for Java and Microsoft® Office Communicator Mobile for Nokia 1.0 depend on the Communicator Mobile component (the Back End Server component)for Microsoft® Office Communications Server 2007 R2. Microsoft® Lync™ Server 2010 communications software does not automatically install the necessary Back End Server components (for instance, the 2007 R2 release of Microsoft® Office Communicator Web Access or the associated Communicator Mobile component). Therefore, users of the previously mentioned mobile clients will experience disruption and won’t be able to use their mobile client when they are upgraded to Lync Server 2010.

This document provides the necessary steps for installing the Communicator Mobile component alongside Lync Server 2010 so that Office Communicator Mobile 2007 R2 for Java and Office Communicator Mobile for Nokia 1.0 can connect to the Communicator Mobile component as usual, and the Communicator Mobile component can connect to Lync Server 2010.

Many of the steps you need to follow depend on your deployment scenario. If you are a new customer of Lync Server 2010, chose the section that describes your deployment scenario:

-Section 3: (Option A) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environment that has been prepped with the Office Communications Server 2007 R2 schema

-Section 4: (Option B) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environment that has been prepped with the Lync Server 2010 schema

If you are upgrading from Communications Server 2007 R2, see “Section 5:

(Option C) Install the Communicator Mobile component on a topology that has been upgraded from Communications Server 2007 R2 to Lync Server 2010.”

IMPORTANT Regardless of your deployment scenario, complete the steps in Sections 2, 6, 7, and 8.

2.Download the Communicator Mobile component and prerequisites

-Download the Communications Server 2007 R2 Core Components Runtime package from This copies the OCSCore.msi and corresponding prerequisites onto your computer.

-Download the Unified Communications Managed API (UCMA) 2.0, Core Runtime (64-bit) from

-Download the Communicator Mobile Component for Communications Server 2007 R2 and Lync Server 2010 package from This copiesthe 2007 R2 release of Office Communicator Web Access or the associated Communicator Mobile component installer package onto your computer.

3.(Option A) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environmentthat has been prepped with the Communications Server 2007 R2 schema

  1. Before you prep the Lync Server 2010 schema, prep the schema for Communications Server 2007 R2 by installing Ocscore.msi on the domain controller running Active Directory Domain Services (ADDS). Once you install this, you have access to lcscmd.exe, which is used for the schema prep. Make sure you have ADDS running if the server is running the Windows Server® 2008 operating system. Install the necessary prerequisites, as follows.

Install the prerequisites on the domain controller

  1. Microsoft® Visual C++® redistributable-vcredist_x64.exe
  2. Microsoft® .NET Framework 3.5 SP1- dotnetfx35.exe
  3. Microsoft® SQL Server Native Client- sqlncli_x64.msi
  4. Microsoft® Office Communications Server Core Components from Communications Server 2007 R2 -Ocscore.msi
  1. Copy the schema.ldf file from the folder where you deployed the Communications Server 2007 R2 Core Components Runtimepackage to the “D:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2” folder.
  1. Prepare the AD DS schema and forest for Communications Server 2007 R2. After installing the OCSCore.msi, you will see lcscmd.exe in the D:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 folder. Run the following command to prep the schema:

Run the schema prep command

LcsCmd.exe /forest:”<Full domain FQDN>” /action:schemaprep

LcsCmd.exe /forest /action:forestprep

LcsCmd.exe /domain /action:domainprep

  1. Deploy Lync Server 2010. (For details, see the Lync Server TechCenter at
  1. For ensuring backward compatibility with the legacy server components, install Ocswmibc.msi on the computer used to setup the Lync Server 2010 topology. You can find this file at the following location on the Lync Server 2010 installation disc:
    Dev\Server\OcsBootStrapper\Setup.

Ensure backward compatibility

  1. Install OCSWMIBC.MSI (Present at {Lync Server 2010 CD}Dev\Server\OcsBootStrapper\Setup)
  1. Merge the Lync Server 2010 topology with the legacy topology

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

  1. Open Topology Builder.
  2. Click Merge 2007 or 2007 R2 topology.
  3. Click Publish Topology.
  1. Before installing the prerequisites on the computer where you will run the Communicator Mobile component, ensure that you’ve uninstalled Microsoft .NET Framework 4.0 from this computer. Otherwise, the subsequent steps to install UCMA API and CwaMain.msi will fail.
  1. Install the remaining prerequisites on the computer where you will run the Communicator Mobile component:

Install the prerequisites on the server where the Communicator Mobile component will run

  1. Visual C++ redistributable-vcredist_x64.exe
  2. .NET Framework 3.5 SP1- dotnetfx35.exe
  3. SQL Server Native Client- sqlncli_x64.msi
  4. Communications Server Core Components from Communications Server 2007 R2-Ocscore.msi
  5. UCMA (Core Runtime)-UcmaRuntimeSetup.exe
  1. Deploy the Communicator Mobile component by using theCommunicator Web Access installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at

Install the server msi files

  1. CwaMain.msi
  2. CwaActivateServer.msi
  3. CwaCreateVirtualServer.msi
  1. Install the updates for Communications Server 2007 R2 on the computer running the Communicator Mobile component.

Install the updates for Communications Server 2007 R2

  1. Download the updates for Communications Server 2007 R2 from
  2. Run the updates on the computer running Communicator Web Access. (For details, see Microsoft Knowledge Base article 968802, “Updates for Communications Server 2007 R2,” at
  1. Merge the Lync Server 2010 topology with the legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

  1. Open Topology Builder.
  2. Click Merge 2007 or 2007 R2 topology.
  3. Click Publish Topology.
  1. Stop and start services on Lync Server 2010.

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

Stop-CSWindowsService –Verbose

Start-CSWindowsService –Verbose

4.(Option B) Install the Communicator Mobile component on a “clean green field” Lync Server 2010 environment that has been prepped with the Lync Server 2010 schema

If you already have a clean green field Lync Server 2010 environment that was not prepped with Communications Server 2007 R2 schema during installation, as described in the previous section, then you might see the following error if you try to run the schema prep commands described in the previous section:

“ERROR (0xC3EC794A): Current forest schema is of higher version. Please use deployment tools of that version to execute this action.”

In order to deploy Communicator Mobile components in this environment,complete the following steps:

  1. Prep the Communications Server 2007 R2 schema on the domain controllerby using the Schema.ldf file (downloaded as part of the Communications Server 2007 R2 Core Components Runtime package) and the following command:

ldifde –i –v –k –s <DCName> -f schema.ldf –c DC=X <defaultNamingContext> -b <administrator account> <login domain> <password>

For example:

ldifde –i –v –k –s DC1 –f schema.ldf –c DC=X “DC=contoso,DC=com” –b Administrator contoso password

For details, see

  1. Install the OCSCore.msi and its prerequisites on the domain controller.

Install the prerequisites on the domain controller

  1. Visual C++ redistributable-vcredist_x64.exe
  2. .NET Framework 3.5 SP1- dotnetfx35.exe
  3. SQL Server Native Client- sqlncli_x64.msi
  4. Communications Server Core Components from Communications Server 2007 R2 -Ocscore.msi
  1. Prepare the forest and domain for Communications Server 2007 R2 by using lcscmd.exe. After installing the OCSCore.msi, you will see lcscmd.exe in the D:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 folder. Run the following command:

Run the schema prep command

LcsCmd.exe /forest /action:forestprep

LcsCmd.exe /domain /action:domainprep

  1. Re-run the Lync Server 2010 schema prep by using theLync Server 2010 Deployment Wizard.

Run the schema prep

  1. Go to the computer running the Deployment Wizard, run Setup again, and redo the schema prep for Lync Server 2010.
  1. For ensuring backward compatibility with the legacy server components, install Ocswmibc.msi on the computer used to setup the Lync Server 2010 topology. You can find this file at the following location on the Lync Server 2010 installation disc:
    Dev\Server\OcsBootStrapper\Setup.

Ensure backward compatibility

  1. Install OCSWMIBC.MSI (Present at {Lync Server 2010 CD}Dev\Server\OcsBootStrapper\Setup)
  1. Merge the Lync Server 2010 topology with the legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

  1. Open Topology Builder.
  2. Click Merge 2007 or 2007 R2 topology.
  3. Click Publish Topology. (You should see the backward compatibility site.)
  1. Before installing the prerequisites on the computer where you will run the Communicator Mobile component, ensure that you’ve uninstalled .NET Framework 4.0 from this computer. Otherwise, the subsequent steps to install UCMA API and CwaMain.msi will fail.
  1. Install the remaining prerequisites on the computer where you will run the Communicator Mobile component.

Install the prerequisites on the server where the Communicator Mobile component will run

  1. Visual C++ redistributable-vcredist_x64.exe
  2. .NET Framework 3.5 SP1- dotnetfx35.exe
  3. SQL Server Native Client- sqlncli_x64.msi
  4. Communications Server Core Components from Communications Server 2007 R2 -Ocscore.msi
  5. UCMA (Core Runtime)-UcmaRuntimeSetup.exe
  1. Deploy the Communicator Mobile component by using the Communicator Web Access installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at

Install the server msi files

  1. CwaMain.msi
  2. CwaActivateServer.msi
  3. CwaCreateVirtualServer.msi
  1. Install the updates for Communications Server 2007 R2 on the computer running the Communicator Mobile component.

Install the updates for Communications Server 2007 R2

  1. Download the updates for Communications Server 2007 R2 from
  2. Run the updates on the computer running Communicator Web Access. (For details, see Microsoft Knowledge Base article 968802, “Updates for Communications Server 2007 R2,” at
  1. Merge the Lync Server 2010 topology with the legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

  1. Open Topology Builder.
  2. Click Merge 2007 or 2007 R2 topology.
  3. Click Publish Topology.
  1. Stop and start services on Lync Server 2010.

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

Stop-CSWindowsService –Verbose

Start-CSWindowsService –Verbose

5.(Option C) Install the Communicator Mobile component on a topology that has been upgraded from Communications Server 2007 R2 to Lync Server 2010

In this scenario,there is already a topology with servers running Communications Server 2007 R2, and the schema has been prepped for Communications Server 2007 R2. We are assuming that the administrator will first install Lync Server 2010 on a different computer after prepping the schema for Lync Server 2010.

  1. For ensuring backward compatibility, do the following on the computer used to setup the Lync Server 2010 topology.

Ensure backward compatibility

  1. Install OCSWMIBC.MSI (Present at {Lync Server 2010 CD}Dev\Server\OcsBootStrapper\Setup).
  1. Before installing the prerequisites on the computer where you will run the Communicator Mobile component, ensure that you’ve uninstalled .NET Framework 4.0 from this computer. Otherwise, the subsequent steps to install UCMA API and CwaMain.msi will fail.

NOTE: If you already have an installation of the Communicator Mobile component as part of the Communications Server 2007 R2 installation, you can skip this step.

Install prerequisites on the computer where the Communicator Mobile component will run

  1. Visual C++ redistributable-vcredist_x64.exe
  2. .NET Framework 3.5 SP1- dotnetfx35.exe
  3. SQL Server Native Client- sqlncli_x64.msi
  4. Communications Server Core Components from Communications Server 2007 R2 -Ocscore.msi
  5. UCMA (Core Runtime)-UcmaRuntimeSetup.exe
  1. Deploy the Communicator Mobile component by using the Communicator Web Access installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at

NOTE: If you already have an installation of the Communicator Mobile component as part of the Communications Server 2007 R2 installation, you can skip this step.

Installthe server msi files

  1. CwaMain.msi
  2. CwaActivateServer.msi
  3. CwaCreateVirtualServer.msi
  1. Install the updates for Communications Server 2007 R2 on the server running the Communicator Mobile component.

Install the updates for Communications Server 2007 R2

  1. Download the updates for Communications Server 2007 R2 from
  2. Run the updates on the computer running Communicator Web Access. (For details, see the Microsoft Knowledge Base article 968802, “Updates for Communications Server 2007 R2,” at
  1. Merge the Lync Server 2010 topology with the existing legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology

  1. Open Topology Builder.
  2. Click on Merge 2007 or 2007 R2 topology.
  3. Click Publish Topology.
  1. Stop and start services on Lync Server 2010.

On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows PowerShell commands

Stop-CSWindowsService –Verbose

Start-CSWindowsService –Verbose

6.Stop the Communicator Web Access apppool

Communicator Web Access is not a supported component with Lync Server 2010.Therefore, you need to disable the apppool for Communicator Web Access by running the following commands.

If you’re running Windows Server 2008 SP2 with IIS 7

Cd %systemroot%\system32\inetsrv\
>appcmd list apppool
APPPOOL "DefaultAppPool" (MgdVersion:v2.0,MgdMode:Integrated,state:Started)
APPPOOL "Classic .NET AppPool" (MgdVersion:v2.0,MgdMode:Classic,state:Started)
APPPOOL "Communicator Web Access Template Application Pool" (MgdVersion:v2.0,MgdMode:Classic,state:Started)
APPPOOL "W3SVC175074823 - Communicator Web Access" (MgdVersion:v2.0,MgdMode:Integrated,state:Started)
APPPOOL "W3SVC175074823 - Communicator Mobile Component" (MgdVersion:v2.0,MgdMode:Integrated,state:Started)
>appcmd stop apppool "W3SVC175074823 - Communicator Web Access"
>appcmd set apppool "W3SVC175074823 - Communicator Web Access" -autoStart:false

If you’re running Windows Server 2003with IIS 6

cd /d \Inetpub\AdminScripts
> adsutil.vbs enum /p w3svc/apppools
[/w3svc/apppools/Communicator Web Access Template Application Pool]
[/w3svc/apppools/DefaultAppPool]
[/w3svc/apppools/LSGroupExpAppPool]
[/w3svc/apppools/W3SVC175074822 - Communicator Mobile Component]
[/w3svc/apppools/W3SVC175074822 - Communicator Web Access]
> adsutil.vbs STOP_SERVER "/w3svc/apppools/W3SVC175074822- Communicator Web Access"
Server w3svc/apppools/W3SVC175074822 - Communicator Web Access Successfully STOPPED

7.Update the next-hop FQDN or certificates on the computer running Communicator Web Access