Migrate Users Overview
This section describes how to migrate users between IM and Presence Service clusters.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This section describes how to migrate users between IM and Presence Service clusters.
Run full backups of both the current and destination cluster. For details, see Backup the System.
Ensure that the users to be migrated are licensed for the IM and Presence Service or Cisco Jabber on their current home cluster only. If these users are licensed on any cluster other than the premigration cluster, they must be fully unlicensed before proceeding with the migration tasks.
Complete these tasks to migrate IM and Presence users to a new cluster.
Command or Action | Purpose | |
---|---|---|
Step 1 |
Before migrating users, remove all stale rosters, group entries and non-presence contract records. |
|
Step 2 |
Before migrating, confirm the following services are running:
|
|
Step 3 |
Run the System Troubleshooter and confirm that there are no intercluster sync issues. |
|
Step 4 |
Before migrating users, configure these standard Presence settings. |
|
Step 5 |
Complete this procedure to export the contact lists of the migrating users from their current cluster. |
|
Step 6 |
Complete one of these mini-task flows to move users to the new cluster: |
|
Step 7 |
After you have migrated users to the new cluster, import the contact lists to restore contact data for the migrated users. |
|
Step 8 |
You may not want to remove users from the old cluster until after you confirm that everything is working fine in the new cluster. Use this procedure to use Bulk Administration's Update Users feature to remove IM and Presence functionality from the old cluster. |
Before migrating users, remove stale rosters, group entries and non-presence contact records. This is to be done on the publisher IM&P node from which the users had presence disabled.
Note |
Repeat these steps as necessary in batches of 2000. If it is too time consuming to remove a large amount of stale entries via CLI, open a TAC case to leverage the stale roster script at the end of this section that requires root access. |
Step 1 |
Start the CLI session. For details on how to start a CLI session, refer to the "Start CLI session" section of the Command Line Interface Reference Guide for Cisco Unified Communications Solutions. |
Step 2 |
Check and remove stale roster entries. To do this, run the following queries: |
Step 3 |
Check and remove stale group records. To do this, run the following queries: |
Step 4 |
Check and remove stale non-contact records (in order). To do this, run the following queries: |
Before migrating users, configure these Presence settings.
Step 1 |
From Cisco Unified CM IM and Presence Administration, choose . |
Step 2 |
Check the Allow users to view the availability of other users without being prompted for approval check box. |
Step 3 |
For the Maximum Contact List Size (per user) setting, check the No Limit check box. |
Step 4 |
For the Maximum Watchers (per user) setting, check the No Limit check box |
Step 5 |
Click Save. |
Before migrating, confirm that there are no intercluster sync errors.
Step 1 |
From Cisco Unified CM IM and Presence Administration, choose . |
Step 2 |
Confirm that there are no intercluster sync errors. If there are errors, fix them before proceeding. |
In Cisco Unified IM and Presence Serviceability, confirm that the following essential services for the migration are running:
Cisco AXL Web Service
Cisco Sync Agent
Cisco Intercluster Sync Agent
Step 1 |
From Cisco Unified IM and Presence Serviceability, choose |
Step 2 |
From the Server drop-down select your IM and Presence node and click Go. |
Step 3 |
Under Database and Admin Services, confirm that the Cisco AXL Web Service is Started. If the service is not running (the default setting is not running), select the service and click Start. |
Step 4 |
Choose . |
Step 5 |
From the Server drop-down select your IM and Presence node and click Go. |
Step 6 |
Under IM and Presence Services, confirm that both the Cisco Sync Agent and Cisco Intercluster Sync Agent services are running. If they are not running, Start them. |
Complete this procedure to export the contact lists of the migrating users from their current cluster.
Step 1 |
Export the contact lists of the migrating users from the current home cluster.
|
Step 2 |
Monitor the status of the contact list export job.
|
Step 3 |
Download the contact list export file and store it for use later when the user migration is complete.
|
Go to one of the following task flows to assign users in the new cluster:
Complete these tasks if your users are synced with an LDAP Directory and you want to migrate to a new cluster.
Note |
You must add your LDAP Directory configuration into the new cluster. This includes any service profiles, user profiles, and feature group templates. Make sure that your feature group template configuration has the Enable Users for Unified CM IM and Presence check box checked. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
You may need to update your external LDAP directory if your deployment uses a separate LDAP structure for each cluster and where users are synchronized only to their home cluster. |
|
Step 2 |
If LDAP is enabled on Cisco Unified Communications Manager, import users to your new cluster by synchronizing your new cluster with the updated LDAP directory. |
You may need to update your external LDAP directory if your deployment uses a separate LDAP structure for each cluster and where users are synchronized only to their home cluster.
Note |
You do not need to move the users if the deployment uses a flat LDAP structure, that is, all users are synchronized to all Cisco Unified Communications Manager and IM and Presence Service clusters where users are licensed to only one cluster. |
Note |
Depending on how you have your LDAP Directory sync configured in the old and new cluster, moving your users within the external LDAP Directory may automatically migrate those users to the new IM and Presence Service cluster when the next sync occurs. |
Step 1 |
Update users in your external LDAP directory. |
Step 2 |
After you move the users, delete the LDAP entries from the old LDAP cluster. |
Provision the LDAP directory in your new cluster. If your LDAP directory sync includes universal line and device templates, and feature group templates, you must configure these templates in your new cluster. Make sure that your feature group template has the following options checked:
Home Cluster
Enable Users for Unified CM IM and Presence
For details on how to configure an LDAP directory sync, refer to the "Configure End Users" section of the System Configuration Guide for Cisco Unified Communications Manager.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Click Find and select the LDAP Directory that you've configured |
Step 3 |
Click Perform Full Sync Now. |
Complete these tasks to move a user to the new cluster manually.
Note |
If you have a large number of users, you may want to use the Bulk Administration Tool in Cisco Unified Communications Manager to update a large number of users via a csv file. For details, see the Bulk Administration Guide for Cisco Unified Communications Manager. |
Command or Action | Purpose | |
---|---|---|
Step 1 |
Disable a migrating user for IM and Presence Service and Cisco Jabber on their current home cluster. |
|
Step 2 |
If LDAP synchronization is not configured in the new cluster, provision users manually to your new Cisco Unified Communications Manager cluster. |
|
Step 3 |
When the users have been synchronized, or manually provisioned, on the new home cluster, you must enable the users for IM and Presence Service and Cisco Jabber. |
The following procedure describes how to disable a migrating user for IM and Presence Service and Cisco Jabber on their current home cluster.
Note |
If you are migrating a large number of users at once, you may want to use the Bulk Administration Tool in Cisco Unified Communications Manager. For details, see the Bulk Administration Guide for Cisco Unified Communications Manager. |
Step 1 |
In Cisco Unified CM Administration, choose . |
Step 2 |
Use the filters to find the user that you want to disable for IM and Presence Service. |
Step 3 |
In the End User Configuration screen, uncheck Enable User for Unified CM IM and Presence. |
Step 4 |
Click Save. |
If LDAP synchronization is not configured in the new cluster, import users manually to your new Cisco Unified Communications Manager cluster.
For details, see Configure User Settings.
When the users have been synchronized, or manually provisioned, on the new home cluster, you must enable the users for IM and Presence Service and Cisco Jabber.
Step 1 |
In Cisco Unified CM Administration, choose . |
Step 2 |
Use the filters to find the user that you want to enable for IM and Presence Service. |
Step 3 |
In the End User Configuration screen, check Enable User for Unified CM IM and Presence. |
Step 4 |
Click Save. |
Step 5 |
Provision the users on Cisco Unified Communications Manager for Phone and CSF. See the Administration Guide for Cisco Unified Communications Manager for more information. |
Move the users to a new cluster via the Bulk Administration Tool (for example, migrating from cluster 1 to cluster 2).
The Cisco Bulk Provisioning Service must be running in both clusters.
Note |
If the number of users to be moved from source to destination in IM and Presence cluster are less than 100 then, do not start or stop Cisco Intercluster Sync Agent service. If you are moving 100 to 1,000 users from any source / destination cluster perform the below steps by stopping Intercluster Sync Agent service on both source and destination clusters. If the number of users to be moved are more than 1000, For example, if we have to move 16K users then first move 8K users by following below steps and stop the Intercluster Sync Agent service while moving users in chunks of 1K users. Later move the next 8K in a balanced and serial sequence in chunks of 1K users. |
On the IM and Presence cluster where the users are being moved from source:
Step 1 On the associated subscriber node of the IM and Presence publisher's Presence Redundancy Group (PRG) pair stop Intercluster Sync Agent service.
Step 2 On the publisher node of the publisher IM and Presence Presence Redundancy Group pair stop Intercluster Sync Agent service.
On the IM and Presence cluster where the users are being moved from destination:
Step 3 On the secondary node of the publisher Presence Redundancy Group pair stop Intercluster Sync Agent service.
Step 4 On the publisher node of the publisher Presence Redundancy Group pair stop Intercluster Sync Agent service.
Note |
No other cluster nodes require Intercluster Sync Agent service to be stopped. |
Step 5 Peform the steps mentioned in Migrate Users via Bulk Administration.
Step 6 Start the Intercluster Sync Agent service on the IM and Presence publisher and subscriber nodes on both destination and source clusters.
Step 7 It can take up to 30 minutes for all other clusters to complete their sync with the destination cluster.
Command or Action | Purpose | |
---|---|---|
Step 1 |
In the original cluster (cluster 1) export the migrating users to a CSV file. |
|
Step 2 |
Download the CSV export file. |
|
Step 3 |
Upload the CSV file to the destination cluster (cluster 2). |
|
Step 4 |
In the destination cluster, configure a User Template with the user settings. |
|
Step 5 |
Use the Insert Users menu in Bulk Administration to import users from the CSV file. |
|
Step 6 |
Verify the user migration via bulk administration. |
In the original cluster, use the Bulk Administration Tool to export the users whom you want to migrate to a CSV file.
Note: After the job runs, you can go to the Job Scheduler to check the status of the job and confirm that the file was created. If you selected Run Later, you can use the Job Scheduler to set the time for the job to run.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Use the Filter tools to search for and select the users whom you want to migrate and click Find. |
Step 3 |
Click Next. |
Step 4 |
Enter a File Name for the file. |
Step 5 |
From the File Format drop-down, select the format of the export file. |
Step 6 |
To run the job right away, select Run Immediately and click Submit. |
After the job runs, you can go to the Job Scheduler to check the status of the job and confirm that the file was created. If you selected Run Later, you can use the Job Scheduler to set the time for the job to run.
Once you have confirmed that the file was created, Download CSV Export File.
Once you have confirmed that the export file was created, download the file.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Click Find. |
Step 3 |
Select the file that was created and click Download Selected. |
Step 4 |
Download the file. |
In the destination cluster (cluster 2), upload the csv file that you exported from cluster 1.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Click Add New. |
Step 3 |
Click Choose File. Browse and select the export file from the other system. |
Step 4 |
From the Target drop-down, select the Bulk Administration menu that you want to use to import the file contents. For example, Users or Phones and Users. |
Step 5 |
From the Transaction Type drop-down, select the submenu that you want to use to import the file contents. For example, Insert Users or Insert Phones/Users. |
Step 6 |
Click Save |
In the destination cluster, configure a user template with the settings that you want to apply to imported users.
Step 1 |
From Cisco Unified CM Administration choose . |
Step 2 |
Do either of the following:
|
Step 3 |
Configure the user settings that you want to apply to your imported users. For example, make sure that the following fields are checked
|
Step 4 |
If you want users to be enabled for calendar integration with Microsoft Outlook, check the Include meeting information in Presence check box. |
Step 5 |
Configure any remaining fields. |
Step 6 |
Click Save. |
Use Bulk Administration's Insert Users menu to import the exported users into the new Cluster.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
From File Name, select the file that was exported from the other system. |
Step 3 |
From the User Template Name, select the user template that you just created. |
Step 4 |
Check the File created with Export Users check box. |
Step 5 |
Check Run Immediately and click Submit. |
After migrating users via Bulk Administration and starting Cisco Intercluster Sync Agent Services on the source and destination clusters, it is necessary to verify that other clusters than source and destination clusters received notifications that user move has been occurred.
It can take up to 30 minutes for all other clusters to complete their sync with the destination cluster. While you wait, you can open a terminal session to sample (5) IMP publishers in parallel that are not part of the change (source or destination) to monitor the CiscoSyslogs.
Step 1 |
Run the below command to observe if the sample IMP publisher node has already completed its sync after migrating users via Bulk Administration and starting Cisco Intercluster Sync Agent Services on the source and destination clusters. Notify the timestamp for this moment. In the following example syntax, the destination cluster name is dst-name. Replace this with your destination cluster name.
|
Step 2 |
If the time stamp in the ICSA status is not more recent than the timestamp recorded, then use the following command for up to 30 minutes for a successful sync:
If you see an ICSA failed sync status alarm on the selected sample cluster/node, wait for 5-10 minutes for a successful sync status alarm. ICSA will retry every 5 minutes. If you do not have a successful sync alarm or have consistent sync failures, please open a TAC case. At this point you have verified the 5 remote sample clusters if the current time is 30 minutes later than timestamp recorded after migrating users via Bulk Administration and starting Cisco Intercluster Sync Agent Services on source and destination clusters. You can now proceed to the next move process or if there no other moves, you are finished. |
After you have migrated users to the new cluster, import the contact lists to restore contact data for the migrated users.
Step 1 |
Upload the previously exported contact list CSV file.
|
Step 2 |
Run the import contact list job.
|
Step 3 |
Monitor the contact list import status |
You may not want to remove users from the old cluster until after you confirm that everything is working fine in the new cluster. Use this procedure to use Bulk Administration's Update Users feature to remove IM and Presence functionality from the old cluster.
Step 1 |
From Cisco Unified CM Administration, choose . |
Step 2 |
Use the Filter tools to search for the migrating users. For example, you can search for all users whom meet this condition: Has IM and Presence Enabled. |
Step 3 |
Click Next |
Step 4 |
For each of the following two fields, check the far left box and leave the adjacent box on the right unchecked. The left box indicates that you want to update the field and the right box indicates the new setting: unchecked.
|
Step 5 |
Under Job Information, select Run Immediately. |
Step 6 |
Click Submit. |
Once you are confident that the migration worked, and that all users are configured properly in the new cluster, you can delete migrated users in the old cluster.