Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager, Release 9.0(1)
Integration Overview
Downloads: This chapterpdf (PDF - 2.02MB) The complete bookPDF (PDF - 4.15MB) | The complete bookePub (ePub - 767.0KB) | Feedback

Integration Overview

Contents

Integration Overview

Partitioned Intradomain Federation

More and more enterprises are choosing Cisco Unified Communications Manager IM and Presence Service as their IM and availability platform. These enterprises already have Microsoft Lync, Microsoft Office Communications Server (OCS) or Microsoft Live Communications Server (LCS) deployed and want to move their users over to an IM and Presence Service supported client.

During this transition, it is important that these users who migrate to an IM and Presence Service supported client can continue to share availability and instant messages with those users who are still using the Microsoft servers. For more information about supported IM and Presence Service clients, see the "Software Requirements" section.

Partitioned Intradomain Federation enables IM and Presence Service client users and Microsoft Lync or Microsoft Office Communicator users within the same enterprise domain to exchange presence Availability and IM.

This integration supports users within an enterprise domain who are either configured on the IM and Presence Service and use an IM and Presence Service supported client as their desktop client, or are enabled on OCS or LCS and use Microsoft Lync or Microsoft Office Communicator as their desktop client or are enabled on Lync, OCS or LCS and use Microsoft Lync or Microsoft Office Communicator as their desktop client.


Note


Partitioned Intradomain Federation requires that a user is enabled on one system only. This integration does not support a user that is enabled on both the IM and Presence Service and the Microsoft server at the same time.


The IM and Presence Service uses the standard Session Initiation Protocol (SIP RFC 3261) to provide Partitioned Intradomain Federation support for the following Microsoft server platforms:

  • Microsoft Lync Server 2010, Standard Edition and Enterprise Edition

  • Microsoft Office Communications Server 2007 R2 Standard Edition and Enterprise Edition

  • Microsoft Live Communications Server 2005 Standard Edition and Enterprise Edition


Note


The term Microsoft server is used in this document to refer to all supported Lync, OCS and LCS platform types. Any information that is specific to a certain platform is identified.


Related References

Partitioned Federation Deployment Overview

The following figure shows a high-level sample deployment of the IM and Presence Service and Microsoft OCS within the same domain. This example shows an OCS deployment, but it also applies to the other supported Microsoft servers.

For Partitioned Intradomain Federation, you must configure the identical domain on the IM and Presence Service nodes and on the Microsoft servers.

Figure 1. Integration Overview



Single Domain Example

In this example, users within the domain called synergy.com on both the IM and Presence Service node and the Microsoft Lync server are able to exchange Availability and IM using intradomain federation because that domain is configured on both systems. The common active directory enables contact searches and display name resolution for all users on both systems.

Figure 2. Single Domain Intradomain Federation Example




Note


Domains must be identical. For example, user1@abc.synergy.com cannot share IM and Availability with any of the federated users configured for Intradomain Federation on synergy.com. Add user1 to the synergy.com domain to enable user1 to participate in Intradomain Federation in this example.


Partitioned Intradomain Federation Configuration

You configure the following key components to enable Partitioned Intradomain Federation between the IM and Presence Service and your Microsoft Lync/OCS/LCS server:
  1. IM and Presence Service node

  2. Microsoft server

  3. User migration


Tip


See the detailed configuration workflows for the start-to-finish steps needed to enable Partitioned Intradomain Federation and for links to the procedures that are performed at each step of the process.


Cisco recommends that you back up the Microsoft server user contact list information before proceeding to configure Partitioned Intradomain Federation between the IM and Presence Service and your Microsoft server.

Table 1 Partitioned Intradomain Federation High Level Configuration Tasks for the IM and Presence Service Node

Task

O = Optional

M = Mandatory

Ensure that the common domain to be used for Partitioned Intradomain Federation is configured on the IM and Presence Service node and verify that matching domains are configured on the Microsoft servers

M

Enable Partitioned Intradomain Federation

M

Set up static routes to the Microsoft server

M

Set up access control lists

M

Set up TLS for the Lync server (required if you are using a Lync server)

M

Set up TLS for OCS and LCS servers

O

Deactivate non-essential services on the dedicated routing server (if applicable)

M

Table 2 Partitioned Intradomain Federation High Level Configuration Tasks for the Lync Server

Task

O = Optional

M = Mandatory

Ensure that the common domain used for Partitioned Intradomain Federation is configured on the Lync server and verify that it matches the domain that is configured on the IM and Presence Service nodes.

M

Set up static routes to the IM and Presence Service node

M

Set up host authorization

M

Publish the topology

M

Set up TLS

M

The following table lists the high-level Partitioned Intradomain Federation configuration tasks for the OCS and LCS servers

Table 3 Partitioned Intradomain Federation High Level Configuration Tasks for the OCS and LCS Servers

Task

O = Optional

M = Mandatory

Ensure that the common domain used for Partitioned Intradomain Federation is configured on the Lync server and verify that it matches the domain that is configured on the IM and Presence Service nodes.

M

Enable SIP port

M

Set up static routes to the IM and Presence Service node

M

Set up host authorization

M

Set up TLS

O

Table 4 Partitioned Intradomain Federation User Migration Tasks

Task

O = Optional

M = Mandatory

Download tools

M

Disable Lync subscriber notification pop-ups

M

Set unlimited contact list sizes and watcher sizes

M

Enable auto authorization of subscriber requests

M

Provision Microsoft server users on Cisco Unified Communications Manager

M

Back up user Microsoft server contact list information

M

Export contact lists for users

M

Disable users on Microsoft server

M

Verify that user accounts are disabled

M

Delete user data from database for migrating users

Note   

Depending on your Microsoft server deployment, you may have to perform this procedure on multiple databases.

M

Import contact lists for migrating users in to the IM and Presence Service

M

Reset maximum contact list and watcher size

M

Re-enable Lync subscriber notification pop-ups

M

Availability

This section describes Availability functionality.

Availability Subscriptions and Policy

This section describes call flows for the IM and Presence Service and Microsoft Lync or Microsoft Office Communicator.

Subscription to an IM and Presence Service User

When a Microsoft Lync or Microsoft Office Communicator user wishes to view the availability of an IM and Presence Service client user, a SIP SUBSCRIBE request is routed from Lync/OCS/LCS to IM and Presence Service. IM and Presence Service accepts the incoming subscription and places it in a pending state. Private policy is then applied to this incoming subscription request.


Note


Privacy policy applied to subscriptions from Microsoft server users in a Partitioned Intradomain Federation deployment is identical to the privacy policy applied to subscriptions from IM and Presence Service client users.


The IM and Presence Service checks whether auto-authorization is enabled or whether the IM and Presence Service client user has previously blocked or allowed presence subscriptions from the Microsoft server user. If either case is true, IM and Presence Service auto-handles policy decision for the subscription request. Otherwise, the IM and Presence Service client user receives an alert regarding the new subscription.

If the subscription is denied, polite blocking is implemented. This means that the presence state of the user appears as offline to the Microsoft server user. If the subscription is authorized, the IM and Presence Service sends availability updates to the Microsoft server user and the IM and Presence Service client user also has the option to add the Microsoft server user to their roster.

Subscription to Microsoft Lync or Microsoft Office Communicator User

When an IM and Presence Service client user wishes to view the availability of a Microsoft Lync or Microsoft Office Communicator user, a SIP SUBSCRIBE request is routed from IM and Presence Service to Lync/OCS/LCS. The Microsoft server accepts the incoming subscription. Policy is then applied to this incoming subscription request.

If the Microsoft server user has previously accepted a subscription from this IM and Presence Server user, the subscription is auto-accepted and availability is returned to the IM and Presence Service client user in line with the policy level applied by the Microsoft server user. If not, the Microsoft server user receives an alert regarding the new subscription. The Microsoft server user can then accept or block the IM and Presence Service client user.


Note


The Microsoft server performs a refresh subscribe approximately every 1 hour and 45 minutes. Therefore, if an IM and Presence Service node restarts, the maximum duration a Microsoft Lync or Microsoft Office Communicator user is without the availability status of the IM and Presence Service contacts is approximately two hours.

If the Microsoft server restarts, the maximum duration an IM and Presence Service client is without available status of Microsoft Lync or Microsoft Office Communicator contacts is approximately 2 hours.


Availability Mapping States

The following table shows the availability mapping states from Microsoft Lync or Microsoft Office Communicator to the following IM and Presence Service supported clients:

  • Cisco Jabber for Windows

  • Cisco Jabber for Mac

  • Cisco Jabber for iPad

  • Cisco Jabber IM for Mobile (iPhone, Android, Blackberry)

  • Cisco Unified Personal Communicator Release 8.x

  • Third-party XMPP Clients

Table 5 Availability Mapping States from Microsoft Lync or Microsoft Office Communicator

Microsoft Lync or Microsoft Office Communicator

Setting

Cisco Jabber1

Setting

Cisco Unified Personal Communicator

8.x Setting

Third-Party XMPP Clients

Setting

Available

Available

Available

Available

Away

Away

Away

Away

Be Right Back

Away

Away

Away

Busy

Busy

Busy

Busy

Do Not Disturb

Busy

Busy

Busy

Appear Offline

Offline

Offline

Offline

Offline

Offline

Offline

Offline

1 Applies to all supported Cisco Jabber clients.

The following table shows the availability mapping states from all supported Cisco Jabber clients to Microsoft Lync or Microsoft Office Communicator.

Table 6 Availability Mapping States from Cisco Unified Personal Communicator Release 8.x to Microsoft Lync or Microsoft Office Communicator

Cisco Unified Personal Communicator

Release 8.x Setting

Microsoft Lync or Microsoft Office Communicator

Setting

Available

Available

Busy

Busy

On the Phone

Busy

Meeting

Busy

Away

Away

Do Not Disturb

Busy

Offline

Offline

Offline—On the Phone

Offline

Offline—Meeting

Offline

Offline—Out of Office

Offline

The following table shows the availability mapping states from Cisco Jabber to Microsoft Lync or Microsoft Office Communicator.

Table 7 Availability Mapping States from Cisco Jabber to Microsoft Lync or Microsoft Office Communicator

Cisco Jabber2

Setting

Microsoft Lync or Microsoft Office Communicator

Setting

Available

Available

Away

Away

Do Not Disturb

Busy

Out of Office

Offline

Offline

Offline

2 Applies to all supported Cisco Jabber clients.

The following table shows the availability mapping states from third-party XMPP clients to Microsoft Lync or Microsoft Office Communicator.

Table 8 Availability Mapping States from Third-Party XMPP Clients to Microsoft Lync or Microsoft Office Communicator

Third-Party XMPP

Setting

Microsoft Lync or Microsoft Office Communicator

Setting

Available

Available

Away

Away

Extended Away

Away

Do Not Disturb

Busy

Offline

Offline

Instant Messaging

Partitioned Intradomain Federation supports point-to-point IM between the IM and Presence Service client users and Microsoft Lync or Microsoft Office Communicator users. This includes support for the following IM features:

  • Plain text IM format

  • Typing indication

  • Basic emoticons

SIP Session Mode IM is used to transfer messages and typing indications between the IM and Presence Service and the Microsoft server.

When an IM and Presence Service client user sends an IM to a Microsoft server user, if no existing IM session is established between these two users the IM and Presence Service sends a SIP INVITE message to the Microsoft server to establish a new session. This session is used for any subsequent SIP MESSAGE or SIP INFO (typing indication) traffic from either of these two users.


Note


The IM and Presence Service client users and third-party XMPP client users can begin an IM conversation with a Microsoft server user even if they do not have availability.


When a Microsoft user sends an IM to an IM and Presence Service client user, if no existing IM session is established between these two users, the Microsoft server sends a SIP INVITE message to the IM and Presence Service. This session is used for any subsequent SIP MESSAGE or SIP INFO (typing indication) traffic from either of these two users.


Note


Due to the proprietary nature of Microsoft server group chat functionality, Partitioned Intradomain Federation does not support group chat between the IM and Presence Service client users and Microsoft Lync or Microsoft Office Communicator users.


Request Routing

This section describes request routing for the IM and Presence Service to Lync/OCS/LCS and for Lync/OCS/LCS to the IM and Presence Service.

IM and Presence to Microsoft Server Request Routing

To enable basic connectivity from IM and Presence Service to Lync/OCS/LCS, you must configure SIP static routes on the IM and Presence Service for the IM and Presence Service domain. These static routes point to an IP address of a Microsoft server or front-end load balancer (Enterprise Edition Microsoft servers only) and allow the IM and Presence Service to route same-domain requests to the Microsoft server when the recipient is not an IM and Presence Service user. Transport Layer Security (TLS) encryption can be enabled on these static routes. To support basic connectivity from the IM and Presence Service to the Microsoft server, you must also configure entries in the Incoming Access Control List (ACL) to ensure that the Microsoft servers can access the IM and Presence Service node without authentication.

Overlaying this basic connectivity, Partitioned Intradomain Federation provides two modes of request routing from the IM and Presence Service to the Microsoft server: Basic Routing and Advanced Routing.

Basic Routing Mode for Partitioned Intradomain Federation

Basic Routing is the default routing mode for Partitioned Intradomain Federation. When Basic Routing is enabled, the IM and Presence Service routes a request to Lync/OCS/LCS if the request recipient is within the IM and Presence Service domain but is not a licensed IM and Presence Service user.

The following figure shows the sequence of the routing request from the IM and Presence Service to the Microsoft server when Basic Routing is configured. This figure shows an example of an OCS deployment, but it also applies to the other supported Microsoft servers.

Figure 3. IM and Presence Service to Microsoft Server Request Routing



1

Ann, a Cisco Jabber 8.x user, sends a request to Bob, who is a Microsoft Office Communicator user.

2

Because Bob is within the local domain but is not a licensed IM and Presence Service client user, the IM and Presence Service translates the request and routes it to OCS.

3

The OCS server forwards the request to Bob’s Microsoft Office Communicator client.


Note


  • For recipients who are not provisioned on either the IM and Presence Service or a Microsoft server, any such request that is forwarded to the Microsoft server is in turn returned by the Microsoft server to the IM and Presence Service.
  • The IM and Presence Service has built-in loop detection to reject any requests that loop back from the Microsoft server in this manner.


Advanced Routing Mode for Partitioned Intradomain Federation

Advanced Routing ensures less traffic between the IM and Presence Service and Lync/OCS/LCS in deployments in which there are a large number of unprovisioned or unknown contacts in the IM and Presence Service database. However, Advanced Routing does add an additional storage overhead on each IM and Presence Service cluster because each cluster must store all Microsoft Lync or Microsoft Office Communicator users so that the Advance Routing logic can be applied.

Configure Advanced Routing for Partitioned Intradomain Federation only when you have a single-cluster IM and Presence Service deployment and Cisco Unified Communications Manager synchronizes its users from the same Active Directory that the Microsoft server uses. When more than one IM and Presence Service cluster is deployed, you must use the default basic routing method.

For Advanced Routing, the list of users synchronized from Active Directory must include all Microsoft Lync or Microsoft Office Communicator users.

When Advanced Routing is enabled, the IM and Presence Service routes the request to the Microsoft server when both of the following conditions are met:

  • The request recipient is within the IM and Presence Service domain but is not a licensed IM and Presence Service user

    and

  • The request recipient has a valid Microsoft Lync or Microsoft Office Communicator SIP address stored in the IM and Presence Service database.

Microsoft Server to IM and Presence Service Request Routing

To enable basic connectivity from Lync/OCS/LCS to the IM and Presence Service, you must configure SIP static routes on the Microsoft server for the IM and Presence Service domain. These static routes point to the IP address and port of an IM and Presence Service node, which is designated as the routing IM and Presence Service node. They allow the Microsoft server to route same-domain requests to the IM and Presence Service when the recipient is not a Microsoft server user. TLS encryption can be enabled on these static routes.

To ensure that the Microsoft server is not prompted for authorization to accept SIP Requests from the IM and Presence Service, you must also configure Host Authorization entries on the Microsoft server for each IM and Presence Service node.

As mentioned, overlaying the static route configuration, the Microsoft server has just a single routing mode in a Partitioned Intradomain Federation deployment. The Microsoft server routes requests to the IM and Presence Service if the request recipient is within one of the Microsoft server managed IM and availability domains but is not a Microsoft Lync or Microsoft Office Communicator user.

The following figure shows the sequence of the routing request from a Microsoft server to the IM and Presence Service. This figure shows an example of an OCS deployment, but it also applies to the other Microsoft server deployments.

Figure 4. Microsoft Server to IM and Presence Service Request Routing



1

Bob, a Microsoft Office Communicator user, sends a request to Ann, who is a Cisco Jabber user.

3

The IM and Presence Service accepts the request and forwards it to Ann’s home IM and Presence Service node.

2

Because Ann is within the local domain but is not a Microsoft Office Communicator user, the Microsoft server routes the request to the IM and Presence Service.

4

The IM and Presence Service translates the request and forwards it to Ann’s Cisco Jabber client.


Note


For recipients who are not provisioned on either the IM and Presence Service or the Microsoft server, any such requests that are forwarded by the Microsoft server to the IM and Presence Service are rejected by the IM and Presence Service.


Intercluster and Multinode Deployments

In an intercluster and multinode cluster IM and Presence Service deployment, when establishing an Availability subscription or IM conversation, Lync/OCS/LCS servers route all SIP messages to an IM and Presence Service node that is designated for routing purposes. If the IM and Presence Service routing node does not host the recipient user, it routes the message to the appropriate IM and Presence Service node within the deployment. The system routes all responses that are associated with this request back through the routing IM and Presence Service node.

Any IM and Presence Service node, when establishing an Availability subscription or IM conversation, can send a SIP message directly to a Microsoft server. When the Microsoft server replies to these messages, the replies are sent directly back to the IM and Presence Service node that began the message.

Interdomain Federation

The IM and Presence Service supports Interdomain Federation. This feature is also available when the IM and Presence Service is configured for Partitioned Intradomain Federation. However, any Interdomain Federation that is configured on the IM and Presence Service is available only to IM and Presence Service client users.

If the Lync/OCS/LCS deployment is already configured for SIP Interdomain Federation through an Access Edge/Access Proxy server, Microsoft Lync or Microsoft Office Communicator users can continue to use this federation capability. It is also possible to configure the IM and Presence Service and the Microsoft server so that IM and Presence Service client users can take advantage of such existing federation capability.


Note


  • It is not supported to configure both the IM and Presence Service and the Microsoft server to federate directly with the same remote domain.

  • See the document Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager for more information about Interdomain Federation.


High Availability for Intradomain Federation

Partitioned Intradomain Federation supports high availability for request routing between the IM and Presence Service and Lync/OCS/LCS.

High Availability for IM and Presence Service to Microsoft Server Request Routing

As mentioned earlier, SIP static routes must be configured on the IM and Presence Service to enable basic Intradomain Federation connectivity between the IM and Presence Service and Lync/OCS/LCS.

To provide high availability for integration with Microsoft servers, you can configure multiple SIP static routes for each address pattern on the IM and Presence Service.

You can assign priority values to these static routes as required to define primary and backup static routes. Highest Priority routes are attempted first. If those routes are not available, the request is re-sent using the backup route as shown in the following figure. This figure shows an example of an OCS deployment, but it also applies to the other supported Microsoft servers.

Figure 5. High Availability for IM and Presence Service to Microsoft Server Request Routing



1

When routing to a Microsoft server, the IM and Presence Service finds the highest-priority static route and attempts to send the request to the next hop address that is configured for that route.

2

If that next hop is not available, the IM and Presence Service falls back to the next-highest priority static route and attempts to send the request to the associated next hop address.

In the case of Enterprise Edition Microsoft servers, you can deploy a front-end load balancer. In such cases, you can configure SIP static routes on the IM and Presence Service to point to the IP address of the Microsoft server's front-end load balancer. The front-end load balancer provides high availability within its associated Microsoft server pool as shown in the following figure. This figure shows an example of an OCS deployment, but it also applies to other Microsoft servers.

Figure 6. High Availability with Load Balancer for IM and Presence to Microsoft Server Request Routing



1

When routing to a Microsoft server, the IM and Presence Service finds a static route that points to the OCS front-end load balancer.

2

The Microsoft server's front-end load balancer then routes onward to one of the active front-end servers within the pool.

See the following URL for a list of approved load balancers: http:/​/​technet.microsoft.com/​en-us/​office/​ocs/​cc843611. It is your responsibility to ensure that those load balancers are deployed and managed correctly.


Note


Cisco does not support the configuration of static routes to point to load balancers. Cisco recommends that you configure static routes to bypass the front-end load balancer.


High Availability for Microsoft Server to IM and Presence Service Request Routing

SIP static routes must be configured on Lync/OCS/LCS to enable basic Intradomain Federation connectivity between Microsoft server and the IM and Presence Service.

However, Microsoft servers support configuration of only a single SIP static route for each domain, which means that the static route can point to just a single IM and Presence Service node.

Therefore, to achieve high availability when the IM and Presence Service is integrated with a Microsoft server, you must incorporate a load balancer between the IM and Presence Service node and Microsoft server as shown in the following figure. This figure shows an example of an OCS deployment, but it also applies to the other Microsoft servers.

Figure 7. High Availability for Microsoft Server to IM and Presence Service Request Routing



1

The load balancer works in Active/Backup mode. It routes requests to the primary IM and Presence Service node while that server is running and uses heartbeat signaling to check if the IM and Presence Service node is alive.

2

If the IM and Presence Service fails, the load balancer ensures that all subsequent requests are routed to the backup IM and Presence Service node.

Contact Search

Partitioned Intradomain Federation allows for full search capabilities on both IM and Presence Service supported clients and Microsoft Lync or Microsoft Office Communicator.

Active Directory (AD) searches by the IM and Presence Service supported clients return users regardless of where they are provisioned. Microsoft server Address Book searches continue to return all Microsoft server users and also any IM and Presence Service client users who have migrated to the IM and Presence Service.

Contact Card information is available on both clients for all contacts.


Note


If an IM and Presence Service client user was never provisioned on the Microsoft server, you must perform an Active Directory update to the msRTCSIP-PrimaryUserAddress field for such users to ensure that the user is available for the Microsoft server searches.


User Migration

At a high level, the administrative flow for user migration is as follows:

  1. License and assign migrating Microsoft server users to the IM and Presence Service.

  2. Back up Microsoft server data for migrating Microsoft server users.

  3. Export Microsoft server contact lists for each of the migrating Microsoft server users.

  4. Disable Microsoft server user accounts for migrating Microsoft server users.

  5. Delete Microsoft server user data for migrating Microsoft server users.

  6. Import Microsoft server contact lists into the IM and Presence Service database for the migrated users.

  7. Deploy an IM and Presence Service supported client on migrated users’ desktops.

To further aid the migration process for administrators, a number of tools are available with this feature.

One of the primary advantages of a Partitioned Intradomain Federation deployment is that it allows a seamless transition from a Microsoft server to the IM and Presence Service within an enterprise. Partitioned Intradomain Federation offers the following benefits:
  • IM and Presence Service client users and Microsoft Lync or Microsoft Office Communicator users share the same presence domain.

  • Users can exchange Availability and Instant Messaging within that shared domain.

  • Users can search for and add contacts regardless of where the user or contact is provisioned.

User Migration Tools

The IM and Presence Service provides tools for the following Lync/OCS/LCS user migration steps:

  • Export Microsoft server contact lists for each of the migrating Microsoft server users.

  • Disable Microsoft server user accounts for migrating Microsoft server users.

  • Delete Microsoft server user data for migrating Microsoft server users.

  • Import Microsoft server contact lists into the IM and Presence Service database for the migrated users.


Note


  • While attempting to run any of the user migration tools you may receive the following error: "Application failed to initialize properly". The reason for this error is that you are attempting to run the user migration tools without the .NET 1.1 Framework installed. Each of the user migration tools that Cisco provides requires that at least version 1.1 of the .NET Framework is installed on the server where you are running the tool.

  • The Export, Disable and Delete tools are provided in a zip file on cisco.com. The Import tool is accessible through the Cisco Unified CM IM and Presence Administration user interface.


Export Microsoft Server Contact Lists for Each of the Migrating Microsoft Server Users

This IM and Presence Service tool allows for bulk export of contact lists from the Microsoft server. The exported contact lists are written to a comma-separated values (CSV) file that is acceptable to the IM and Presence Service Contact List Import Bulk Administration Tool (BAT). The combination of these tools allows for end-to-end administrative bulk contact list migration.

Disable Microsoft Server User Accounts for Migrating Microsoft Server Users

The IM and Presence Service contains a tool to disable the Microsoft server user accounts in bulk. This tool disables Microsoft server accounts by connecting to Active Directory and modifying the user’s Microsoft server-specific attributes as required.

Delete Microsoft Server user Data for Migrating OCS Users

Microsoft server users must be deleted from the Microsoft servers to allow Partitioned Intradomain Federation routing from the Microsoft server to the IM and Presence Service. However, when users are deleted from the Microsoft servers, they are removed from the contact list of any Microsoft Lync or Microsoft Office Communicator users also. This IM and Presence Service tool deletes Microsoft server user data in bulk, while ensuring that the users are not removed from the contact list of Microsoft Lync or Microsoft Office Communicator users.

Import Microsoft Server Contact Lists into the IM and Presence Service Database for the Migrated Users

The IM and Presence Service BAT supports bulk contact list import. It takes a CSV file as input for this bulk import. When used in conjunction with the Microsoft server Export Contact List tool, it allows for contact list migration from a Microsoft server to IM and Presence Service.


Note


Running the user migration tools has no affect on the capabilities of other Microsoft server users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run the user migration tools during a scheduled maintenance window to reduce the load on the Microsoft server and Active Directory system.