UCMA 3.0 Core Application Coexistence

If a mixed Microsoft Office Communications Server 2007–Microsoft Lync Server 2010 or mixed Microsoft Office Communications Server 2007 R2–Microsoft Lync Server 2010 topology has already been prepared, no additional steps are necessary for a Microsoft Unified Communications Managed API (UCMA) 3.0 application that has been deployed against Lync Server 2010 following the activation steps described in Activating a UCMA 3.0 Core Trusted Application. The trusted service entries and contact object entries created using the trusted application cmdlets are created in a backward-compatible fashion so that users homed on earlier Communications Server versions will be able to communicate with the application.

The following sections describe each of the Microsoft Unified Communications Managed API (UCMA) 3.0 application coexistence scenarios.

Coexistence of a UCMA 3.0 Core Application in an Office Communications Server 2007 R2—Microsoft Lync Server 2010 Topology

If a UCMA 3.0 application is deployed in a coexistence topology using trusted application cmdlets, no additional steps are necessary. In this scenario, Office Communications Server 2007 R2 users are able to communicate with the application.

For more information about activating a UCMA 3.0 application, see Activating a UCMA 3.0 Core Trusted Application.

Coexistence of a UCMA 3.0 Core Application in an Office Communications Server 2007—Microsoft Lync Server 2010 Topology

Before testing this scenario, make sure that all of the latest patches for UCMA 2.0 have been applied to the Office Communications Server 2007 pool of computers. The following knowledge base articles describe the patches and provided links to the update packages: KB949935, KB945053, KB942872, and KB956389.

Deploy the UCMA 3.0 application in the coexistence topology, using the trusted application cmdlets.

If a Office Communications Server 2007 user is unable make an IM or audio call to a UCMA 3.0 trusted application’s contact object, the following command might be helpful. This command forces a user replication, which replicates the application contact object information to OCS. osql.exe -S (local)\rtc -d rtc -E -Q "exec UrRegenerate"

For more information about activating a UCMA 3.0 application, see Activating a UCMA 3.0 Core Trusted Application.

Direct Deployment of a UCMA 3.0 Core Application in a Pure Office Communications Server 2007 R2 Topology

There is only limited support for UCMA 3.0 applications deployed in a pure Office Communications Server 2007 R2 topology. Specifically, only endpoints of type UserEndpoint are supported; applications that use endpoints of type ApplicationEndpoint are not supported. Only person-to-person IM and IM conferencing are supported; audio is not supported. IM Conference Scheduling is supported, escalating a two-party IM call to an IM conference is supported, and IM conference joining are supported.

In general, a user object or contact object for a UCMA 3.0 application that is not homed on Lync Server 2010 or later, is not supported.

UCMA 3.0 features that depend on Lync Server 2010 are not supported if the application is deployed against Office Communications Server 2007 R2.

Because the UCMA 3.0 application is deployed against Office Communications Server 2007 R2, it should be deployed as if it were a UCMA 2.0 application. For more information, see Deploying a UCMA 2.0 Core Application.