Configuring Lync Server 2010 to 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.

Microsoft Corporation 2
Table of Contents
1. Introduction.........................................................................................................................................5
2. Download the Communicator Mobile component and prerequisites.................................................5
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...........................6
Install the prerequisites on the domain controller..............................................................................6
Run the schema prep command..........................................................................................................6
Ensure backward compatibility............................................................................................................7
Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology...............7
Install the prerequisites on the server where the Communicator Mobile component will run...........7
Install the server msi files....................................................................................................................7
Install the updates for Communications Server 2007 R2.....................................................................7
Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology...............8
On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows
PowerShell commands........................................................................................................................8
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...................................................8
Install the prerequisites on the domain controller..............................................................................9
Run the schema prep command........................................................................................................10
Run the schema prep.........................................................................................................................10
Ensure backward compatibility..........................................................................................................10
Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology.............10
Install the prerequisites on the server where the Communicator Mobile component will run.........11
Install the server msi files..................................................................................................................11
Install the updates for Communications Server 2007 R2...................................................................11
Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology.............11
On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows
PowerShell commands......................................................................................................................11
5. (Option C) Install the Communicator Mobile component on a topology that has been upgraded
from Communications Server 2007 R2 to Lync Server 2010......................................................................12
Ensure backward compatibility..........................................................................................................12
Install prerequisites on the computer where the Communicator Mobile component will run.........12

Microsoft Corporation 3
 Install the server msi files..................................................................................................................12
Install the updates for Communications Server 2007 R2...................................................................13
Merge the Communications Server 2007 R2 topology with the Lync Server 2010 topology.............13
On the Lync Server 2010 Front End Servers, stop and start the Windows service by using Windows
PowerShell commands......................................................................................................................13
6. Stop the Communicator Web Access apppool...................................................................................13
If you’re running Windows Server 2008 SP2 with IIS 7..........................................................................13
If you’re running Windows Server 2003 with IIS 6.................................................................................13
7. Update the next-hop FQDN or certificates on the computer running Communicator Web Access...14
8. Uninstall the server running the Communicator Mobile component................................................14

Microsoft Corporation 4
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 http://go.microsoft.com/fwlink/?LinkId=207171. This copies the OCSCore.msi and
corresponding prerequisites onto your computer.

Microsoft Corporation 5
 - Download the Unified Communications Managed API (UCMA) 2.0, Core Runtime (64-bit)
from http://go.microsoft.com/fwlink/?LinkID=163815.
- Download the Communicator Mobile Component for Communications Server 2007 R2
and Lync Server 2010 package from http://go.microsoft.com/fwlink/?LinkId=207167.
This copies the 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 environment that 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 (AD DS). Once you install this, you have access to lcscmd.exe,
which is used for the schema prep. Make sure you have AD DS 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
a. Microsoft® Visual C++® redistributable -vcredist_x64.exe
b. Microsoft® .NET Framework 3.5 SP1 - dotnetfx35.exe
c. Microsoft® SQL Server Native Client - sqlncli_x64.msi
d. Microsoft® Office Communications Server Core Components from Communications
Server 2007 R2 -Ocscore.msi

2. Copy the schema.ldf file from the folder where you deployed the Communications
Server 2007 R2 Core Components Runtime package to the “D:\Program Files\Common
Files\Microsoft Office Communications Server 2007 R2” folder.

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

4. Deploy Lync Server 2010. (For details, see the Lync Server TechCenter at
http://go.microsoft.com/fwlink/?LinkId=201187.)

5. For ensuring backward compatibility with the legacy server components, install
Ocswmibc.msi on the computer used to set up the Lync Server 2010 topology. You can

Microsoft Corporation 6
 find this file at the following location on the Lync Server 2010 installation disc:
Dev\Server\OcsBootStrapper\Setup.
Ensure backward compatibility
a. Install OCSWMIBC.MSI (Present at {Lync Server 2010
CD}Dev\Server\OcsBootStrapper\Setup)

6. Merge the Lync Server 2010 topology with the legacy topology
Merge the Communications Server 2007 R2 topology with the Lync Server 2010
topology
a. Open Topology Builder.
b. Click Merge 2007 or 2007 R2 topology.
c. Click Publish Topology.

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

8. 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
a. Visual C++ redistributable -vcredist_x64.exe
b. .NET Framework 3.5 SP1 - dotnetfx35.exe
c. SQL Server Native Client - sqlncli_x64.msi
d. Communications Server Core Components from Communications Server 2007 R2
-Ocscore.msi
e. UCMA (Core Runtime) -UcmaRuntimeSetup.exe

9. Deploy the Communicator Mobile component by using the Communicator Web Access
installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at
http://go.microsoft.com/fwlink/?linkid=161884.)
Install the server msi files
a. CwaMain.msi
b. CwaActivateServer.msi
c. CwaCreateVirtualServer.msi

10. Install the updates for Communications Server 2007 R2 on the computer running the
Communicator Mobile component.
Install the updates for Communications Server 2007 R2
a. Download the updates for Communications Server 2007 R2 from
http://go.microsoft.com/fwlink/?LinkID=202639.

Microsoft Corporation 7
 b. 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 http://go.microsoft.com/fwlink/?linkid=187535.)

11. Merge the Lync Server 2010 topology with the legacy topology.
Merge the Communications Server 2007 R2 topology with the Lync Server 2010
topology
a. Open Topology Builder.
b. Click Merge 2007 or 2007 R2 topology.
c. Click Publish Topology.

12. 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.”

Microsoft Corporation 8
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 controller by 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 http://go.microsoft.com/fwlink/?LinkID=207822&clcid=0x409.

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

Install the prerequisites on the domain controller

a. Visual C++ redistributable -vcredist_x64.exe
b. .NET Framework 3.5 SP1 - dotnetfx35.exe
c. SQL Server Native Client - sqlncli_x64.msi
d. Communications Server Core Components from Communications Server 2007 R2
-Ocscore.msi

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

Microsoft Corporation 9
 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

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

Run the schema prep

a. Go to the computer running the Deployment Wizard, run Setup again, and redo the
schema prep for Lync Server 2010.

5. For ensuring backward compatibility with the legacy server components, install
Ocswmibc.msi on the computer used to set up 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

a. Install OCSWMIBC.MSI (Present at {Lync Server 2010
CD}Dev\Server\OcsBootStrapper\Setup)

6. Merge the Lync Server 2010 topology with the legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010
topology
a. Open Topology Builder.
b. Click Merge 2007 or 2007 R2 topology.
c. Click Publish Topology. (You should see the backward compatibility site.)

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

8. 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
a. Visual C++ redistributable -vcredist_x64.exe
b. .NET Framework 3.5 SP1 - dotnetfx35.exe
c. SQL Server Native Client - sqlncli_x64.msi

Microsoft Corporation 10
 d. Communications Server Core Components from Communications Server 2007 R2
-Ocscore.msi
e. UCMA (Core Runtime) -UcmaRuntimeSetup.exe

9. Deploy the Communicator Mobile component by using the Communicator Web Access
installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at
http://go.microsoft.com/fwlink/?linkid=161884.)

Install the server msi files

a. CwaMain.msi
b. CwaActivateServer.msi
c. CwaCreateVirtualServer.msi

10. Install the updates for Communications Server 2007 R2 on the computer running the
Communicator Mobile component.

Install the updates for Communications Server 2007 R2

a. Download the updates for Communications Server 2007 R2 from
http://go.microsoft.com/fwlink/?LinkID=202639.
b. 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 http://go.microsoft.com/fwlink/?linkid=187535.)

11. Merge the Lync Server 2010 topology with the legacy topology.

Merge the Communications Server 2007 R2 topology with the Lync Server 2010
topology
a. Open Topology Builder.
b. Click Merge 2007 or 2007 R2 topology.
c. Click Publish Topology.

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

Microsoft Corporation 11
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 set up
the Lync Server 2010 topology.

Ensure backward compatibility

a. Install OCSWMIBC.MSI (Present at {Lync Server 2010
CD}Dev\Server\OcsBootStrapper\Setup).

2. 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
a. Visual C++ redistributable -vcredist_x64.exe
b. .NET Framework 3.5 SP1 - dotnetfx35.exe
c. SQL Server Native Client - sqlncli_x64.msi
d. Communications Server Core Components from Communications Server 2007 R2
-Ocscore.msi
e. UCMA (Core Runtime) -UcmaRuntimeSetup.exe

3. Deploy the Communicator Mobile component by using the Communicator Web Access
installer. (For details, see “Deploying Communicator Web Access (2007 R2 Release)” at
http://go.microsoft.com/fwlink/?linkid=161884.)

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 the server msi files
a. CwaMain.msi
b. CwaActivateServer.msi
c. CwaCreateVirtualServer.msi

4. Install the updates for Communications Server 2007 R2 on the server running the
Communicator Mobile component.
Install the updates for Communications Server 2007 R2
a. Download the updates for Communications Server 2007 R2 from
http://go.microsoft.com/fwlink/?LinkID=202639.

Microsoft Corporation 12
 b. 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 http://go.microsoft.com/fwlink/?linkid=187535.)

5. Merge the Lync Server 2010 topology with the existing legacy topology.
Merge the Communications Server 2007 R2 topology with the Lync Server 2010
topology
a. Open Topology Builder.
b. Click on Merge 2007 or 2007 R2 topology.
c. Click Publish Topology.

6. 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 2003 with 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]

Microsoft Corporation 13
 > 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
To change the next-hop fully qualified domain name (FQDN) server or the certificates on the
computer running Communicator Web Access, uninstall Communicator Web Access from the
Control Panel, redeploy Communicator Web Access, and reinstall updates on the computer
running Communicator Web Access with the latest certificates or next hop FQDN, as required.

8. Uninstall the server running the Communicator Mobile component

1. Get the topology file by using the following Windows PowerShell™ cmdlet:
(Get-CsTopology -asxml).tostring() > topology.xml

2. Remove Communicator Mobile component-related data from the topology.xml file:

<Cluster RequiresReplication="false" RequiresSetup="false" Fqdn="AC13-LCT.child.orgcn13.com">

<ClusterId SiteId="BackCompatSite" Number="4" />
<Machine OrdinalInCluster="1" Fqdn="AC13-LCT.child.orgcn13.com">
<NetInterface InterfaceSide="Primary" InterfaceNumber="1" IPAddress="0.0.0.0" />
</Machine>
</Cluster>

<Service RoleVersion="1" Type="Microsoft.Rtc.Management.Deploy.Internal.ServiceRoles.ExternalApplicationService"

ServiceVersion="4">
<ServiceId SiteId="BackCompatSite" RoleName="ExternalServer" Instance="1" />
<DependsOn />
<InstalledOn>
<ClusterId SiteId="BackCompatSite" Number="4" />
</InstalledOn>
<Ports xmlns="urn:schema:Microsoft.Rtc.Management.Deploy.ServiceRoles.2008">
<Port Owner="urn:application:cwa1" Usage="SipServer" InterfaceSide="Primary" InterfaceNumber="1"
Port="443" Protocol="Mtls" UrlPath="/" AuthorizesRequests="true" GruuType="CWA">
<TSEGuidOverrides>
<TSEGuidOverride Fqdn="AC13-LCT.child.orgcn13.com" Guid="A4171438-96E1-447C-9BC5-0FA2E9D1CE41" />
</TSEGuidOverrides>
</Port>
<Port Owner="urn:application:cwa2" Usage="SipServer" InterfaceSide="Primary" InterfaceNumber="1"
Port="5565" Protocol="Mtls" UrlPath="/" AuthorizesRequests="true" GruuType="CWA">
<TSEGuidOverrides>
<TSEGuidOverride Fqdn="AC13-LCT.child.orgcn13.com" Guid="4E8D7F33-FAEF-4271-86AA-99714E3F8632" />
</TSEGuidOverrides>
</Port>
<Port Owner="urn:application:cwa3" Usage="SipServer" InterfaceSide="Primary" InterfaceNumber="1"
Port="5566" Protocol="Mtls" UrlPath="/" AuthorizesRequests="true" GruuType="CWA">
<TSEGuidOverrides>
<TSEGuidOverride Fqdn="AC13-LCT.child.orgcn13.com" Guid="042B5556-4249-4C3B-8E48-5A84B14A7FA5" />
</TSEGuidOverrides>
</Port>
</Ports>

Microsoft Corporation 14
 <ExternalApplicationService xmlns="urn:schema:Microsoft.Rtc.Management.Deploy.ServiceRoles.2008" />
</Service>

3. Publish the topology by using the following Windows PowerShell cmdlet:

Publish-CsTopology .\ topology.xml –verbose

4. Verify that the settings have been replicated by using the following the Windows PowerShell
cmdlet:
Get-CsManagementStoreReplicationStatus

5. Uninstall the following components by using Control Panel:

a. 2007 R2 release of Microsoft® Office Communicator Web Access
b. Communications Server 2007 R2 UCMA
c. Communications Server 2007 R2 Admin Tools
d. Communications Server 2007 R2 Core Components
e. Visual C++ redistributable

Microsoft Corporation 15