Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager Release 9.1(1)
User migration
Download this chapter
User migrationUser migration
Download the complete book
Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager Release 9.1(1)Partitioned Intradomain Federation for IM and Presence Service on Cisco Unified Communications Manager Release 9.1(1) (PDF - 4 MB)
 Feedback

Contents

User migration

Cisco user migration tools

Cisco provides the following tools to aid the user migration process from Lync/OCS/LCS to IM and Presence:

  • Export Contact List tool—allows you to export contact lists in bulk from Lync/OCS/LCS for migrating users
  • Disable Account tool—allows you to disable the Lync/OCS/LCS account of migrating users
  • Delete Account tool—allows you to delete migrating users from Lync/OCS/LCS so that presence requests for these users are later routed to IM and Presence

These user migration tools can be collectively downloaded as a zip file from the IM and Presence Download Software page on cisco.com at http:/​/​software.cisco.com/​download/​navigator.html?mdfid=280448682&flowid=37582.

The zip file contains the three tools and a text file called version.txt. The text file contains the current version number of the tools and must be saved in the same folder as the tools. If the tools are stored in different folders, you must store a copy of the text file in each location. If the text file is not in the same folder when you run a tool, you will receive an error and the tool will not run.

Recommendations before migration

Cisco recommends that you perform the following tasks before you begin to migrate users from Lync/OCS/LCS to IM and Presence:

  • Set unlimited contact lists and watchers
  • Enable automatic authorization of subscription requests
  • Disable new subscriber notification popups on Microsoft Lync

Set unlimited contact lists and watchers

Before you migrate users from Lync/OCS/LCS to IM and Presence, Cisco recommends that you set the Maximum Contact List Size and Maximum Watchers settings on IM and Presence to unlimited. This ensures that each migrated user contact list is fully imported to IM and Presence.

After all users have been migrated to IM and Presence, reset the Maximum Contact List Size and Maximum Watchers settings on IM and Presence to the desired values. The system default value is 200 for Maximum Contact List Size and 200 for Maximum Watchers size.

The following procedure describes how to set unlimited values for the Maximum Contact List Size and Maximum Watchers settings.


Note

If you have a multicluster deployment, you must perform this procedure on each cluster. When you change Presence settings, they are applied to all nodes in the cluster; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

Procedure
    Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Settings.
    Step 2   For Maximum Contact List Size (per user), check the No Limit option.
    Step 3   For Maximum Watchers (per user), check the No Limit option.
    Step 4   Select Save.
    Step 5   Restart the Cisco XCP Router on all IM and Presence nodes in the cluster. To restart the Cisco XCP Router, select Cisco Unified IM and Presence Serviceability > Tools > Control Center – Network Services.

    Enable automatic authorization of subscription requests

    To improve user experience during migration, Cisco recommends that you allow automatic authorization of subscription requests before you begin the migration process. Otherwise, each IM and Presence user will be forced to manually authorize subscription requests each time they are imported as a contact into IM and Presence. This setting should only be disabled, if desired, after all migrations are complete.

    The following procedure describes how to enable automatic authorization of subscription requests.


    Note

    This setting is enabled by default on IM and Presence.


    Note

    If you have a multicluster deployment, you must perform this procedure on each cluster. When you change Presence settings, they are applied to all nodes in the cluster; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

    Procedure
      Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Settings.
      Step 2   Check Allow users to view the availability of other users without being prompted for approval.
      Step 3   Select Save.
      Step 4   Restart the Cisco XCP Router on all IM and Presence nodes in the cluster. To restart the Cisco XCP Router, select Cisco Unified IM and Presence Serviceability > Tools > Control Center – Network Services.

      Subscriber Notification Popups

      When you migrate users from Microsoft Lync to IM and Presence, users that remain on Lync may receive subscription notification popups from some of those migrated users. Such a notification will only occur when:

      • the migrated user has the Microsoft Lync user in their contact list and
      • the Microsoft Lync user does not have that same migrated user in their contact list

      If the Microsoft Lync user has the migrated contact in their contact list also, then no popup will be observed. When an individual notification popup has been handled by the Microsoft Lync user, it will not re-appear.

      If you do not want Lync users to receive new subscriber notification popups you can disable Lync popups. You have two options when disabling these notification popups:

      • you can disable popups for the entire duration of user migration
      • you can disable popups only during the migration of a batch of users

      If you disable popups, then all popups for all Lync users will be disabled until you re-enable them.


      Note

      Disabling and enabling Microsoft Lync popups requires a restart of the Lync front-end services.

      Disable Microsoft Lync Popups

      If you want to disable all popups for all Microsoft Lync users, complete the following procedure before you begin the user migration or the migration of a batch of users.

      Procedure
        Step 1   On the Lync front-end server select Start > All Programs > Microsoft Lync Server 2010 > Lync Server Management Shell.
        Step 2   Enter the following powershell command:

        Set-CSClientpolicy -EnableNotificationForNewSubscriber $False

        Step 3   Select Start > Programs > Administrative Tools > Services.
        Step 4   Right-click the service Lync front end server and select Restart.

        Restore Microsoft Lync Popup Behavior

        To restore the previous client behavior for notification popups for Microsoft Lync users complete the following procedure after user migration is complete or after the migration of a batch of users is complete.

        Procedure
          Step 1   Enter the following command to restore client popup behavior on Lync:

          Set-CSClientpolicy -EnableNotificationForNewSubscribers $Null

          Step 2   Select Start > Programs > Administrative Tools > Services.
          Step 3   Right-click the service Lync front end server and select Restart.

          Provision of Lync/OCS/LCS users on Cisco Unified Communications Manager

          The first step in migrating users from Microsoft Lync, Microsoft Live Communications Server (LCS) or Microsoft Office Communications Server (OCS) to IM and Presence is to provision the Lync/OCS/LCS users on Cisco Unified Communications Manager and license them for IM and Presence and an IM and Presence supported client.

          See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for information about configuring new users in Cisco Unified Communications Manager and the license requirements for the IM and Presence Service and IM and Presence supported clients.

          What To Do Next

          Backups of user Lync/​OCS/​LCS contact list information

          Related Information

          Backups of user Lync/OCS/LCS contact list information

          Lync/OCS/LCS provides a tool called dbimpexp.exe. Cisco recommends that you use this tool to back up Lync/OCS/LCS user contact list information so that you can restore this information on Lync/OCS/LCS at a later date, if needed.

          For the purpose of migrating Lync/OCS/LCS users to an IM and Presence supported client, you can use this tool to back up the contact list for an individual Lync/OCS/LCS user or all users.

          Related Topic

          Usage of the dbimpexp.exe tool: http:/​/​www.ocspedia.com/​Misc/​Explore_​Dbimpexp.aspx?ArticleID=41

          What To Do Next

          Export of contact lists for migrating users

          Export of contact lists for migrating users

          Cisco provides an Export Contact List tool (ExportContacts.exe) to allow an administrator to export contact lists in bulk from Lync/OCS/LCS for migrating users. The tool uses Lync/OCS/LCS application programming interfaces (APIs) to export contact lists and output to a comma-separated values (CSV) file. This file can then be used by the IM and Presence Bulk Administration Tool (BAT) to import these same contact lists into IM and Presence at a later point in the migration.


          Note
          • You can run this tool against all supported Lync/OCS/LCS platforms.
          • You can run the tool on any Standard Edition server or Enterprise Edition front-end server.
          • To export contact lists for Lync users, the Export Contact List tool requires read access to the Lync RTC database and also read access to LDAP. You must also ensure that dbo execution account privileges are granted to the RTC database.
          • Running this tool has no affect on the capabilities of other Lync/OCS/LCS users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run this tool during a scheduled maintenance window to reduce the load on the Lync/OCS/LCS and Active Directory system.

          After you run the tool, a file that contains the exported contact lists is created in the same directory as the tool. The filename is ExportedContacts<Timestamp>.csv. A time stamp is appended to the filename when the file is created; therefore, each time you run the Export Contact List tool, it creates a unique output file.

          The Export Contact List tool also creates a second file that contains the Lync/OCS/LCS SIP URI of each user that you specify for the contact list export. The filename is UserList<Timestamp>.txt and it is also created in the same directory as the tool.


          Note

          You can use the UserList<Timestamp>.txt file as input to the Disable Account tool and the Delete Account tool.

          Log file

          The Export Contact List tool also creates a unique time-stamped log file in the same directory as the output file each time you run the tool. The filename for the log file is ExportContactsLog<Timestamp>.txt.

          It is good practice to check the log file each time you run the Export Contact List tool. You can then scan through the log file to fix any issues. At the bottom of each log file, the following information is summarized:

          • Number of users that were successfully processed
          • Number of users that were not found
          • Number of users that were not processed due to errors
          • Largest contact list size
          • Total number of contacts that were found
          • Average contact list size

          Run modes

          The Export Contact List tool has two run modes; NORMAL and STATSONLY. NORMAL is the standard way to run the tool. In this mode, three files are created: the CSV file that contains the exported contacts, the log file and the users’ Lync/OCS/LCS SIP URI file. In STATSONLY mode, the Export Contact List tool creates only the log file. This allows you to run the tool to discover any errors that you can fix before you create the exported contacts CSV file and the Lync/OCS/LCS SIP URI file.

          Input file formats

          The Export Contact List tool (ExportContacts.exe) allows you to specify an input file containing the list of migrating users. The tool then retrieves the contact lists for the users that are specified in that input file. Alternatively, you can specify a command line parameter to export contact lists for all users in the local Lync/OCS/LCS database.


          Note

          If you use choose to export all users with the Export Contact List tool, the resulting UserList<Timestamp>.txt file will contain the contact lists of all Lync/OCS/LCS enabled users in the domain, regardless of whether they are migrating to IM and Presence. If you later use the UserList<Timestamp>.txt file as input to the Disable Account tool and the Delete Account tool, be aware that all user accounts in the domain will be affected by the Disable Account and Delete Account tools.

          If you are using an input file, the following input file formats are supported:

          Input File Format 1: Lync/OCS/LCS SIP URIs

          Note the following:

          • Each line in the input file represents a contact list owner.
          • The contact list owner is represented by the owner’s Lync/OCS/LCS SIP URI, for example, sip:bobjones@foo.com.
          • The following is a sample input file:
            sip:ann@foo.com
sip:bob@foo.com
sip:joe@foo.com
sip:chuck@foo.com

          Input File Format 2: IM and Presence User IDs

          Note the following:

          • You can obtain a file in this format using the IM and Presence BAT Subcluster Export tool.
          • This format is a comma-separated values (CSV) format, in which each line in the input file represents IM and Presence subcluster assignment data on the contact list owner.
          • The contact list owner is represented by the owner’s IM and Presence user ID, for example, bobjones. The user ID (configured on Cisco Unified Communications Manager) must match the user portion of the SIP URI in the Lync/OCS/LCS domain; if the user ID does not match, you must use one of the other input file formats instead.
          • The following is a sample input file with user IDs in bold type:
            UserID,Subcluster Name,Node Name
ann,CUPSubcluster1,CUPServer1
bob,CUPSubcluster1,CUPServer1
joe,CUPSubcluster1,CUPServer1
chuck,CUPSubcluster1,CUPServer1
            The Export Contact List tool ignores the Subcluster Name and Node Name information and uses only the UserID value.
          • If you use this file format, you must provide the domain of the IM and Presence server when you run the tool. The tool uses the domain to format the user’s SIP URI as follows: sip:userID@domain.

          Input File Format 3: Users by Organizational Unit in Active Directory

          In this input file format, you can specify the Organizational Unit (OU) in Active Directory that contains the users that you want to migrate. The input file must have the following format:

          DN:OU=OrgUnit1,OU=OrgUnit2,DC=DomainComp1,DC=DomainComp2

          where OrgUnit1 is an OU in the OrgUnit2 OU and DomainComp1 and DomainComp2 are the domain components. Domains usually have two domain components in AD, for example cisco and com for the cisco.com domain.

          You can also specify multiple distinguished names (DNs) in a single input file to export contact lists for users from different OUs. The format of an input file with multiple DNs is as follows:

          DN:OU=firstOU,DC=DomainComp1,DC=DomainComp2
DN:OU=secondOU,DC=DomainComp1,DC=DomainComp2
DN:OU=thirdOU,DC=DomainComp1,DC=DomainComp2

          The following procedure describes how to export contact lists in bulk from Lync/OCS/LCS for migrating users.

          Procedure
            Step 1   Copy and extract the zip file containing the Cisco user migration tools to the Standard Edition server or Enterprise Edition front-end server.
            Note   

            After extraction, if you move any of the Cisco user migration tools to a different location on the Lync/OCS/LCS servers, you must also copy the version.txt file to the new location to ensure that the tool prints out its current version.

            Step 2   Open a command prompt and change directory to the location of the Export Contact List tool.
            Step 3   At the command prompt, run the tool as follows:

            If you want to...

            Enter this command

            Export the contact list for a list of users as specified in an Lync/OCS/LCS SIP URI input file

            or

            Export the contact list for a list of users in an Organizational Unit in AD, as specified in a Users by Organizational Unit in AD input file

            		 
            ExportContacts.exe -s/LDAPServer -f/input_file -l/logLevel -r/run_mode -i/database_instance

            where:

            • LDAPServer—The IP or FQDN of the AD server where Lync/OCS/LCS users are stored
            • input_file—A text file that contains a list of Lync/OCS/LCS SIP URIs, or, a text file that contains a list of distinguished names for AD Organizational Units that contain the users that you want to migrate
            • logLevel—The logging level, which must be one of the following:
              • error
              • info
              • debug (recommended)
            • run_mode—The run mode, which must be one of the following:
              • NORMAL
              • STATSONLY
            • database_instance—The Lync datastore instance name. This parameter is required only when you are exporting contacts for Lync users. You do not need to include this parameter when you are exporting contacts for OCS or LCS users. Sample entries are as follows:
              • Lync Standard Edition server: localhost\rtc
              • Lync Enterprise Edition server: LyncDatastoreFqdn\rtc

            Export the contact list for a list of users as specified in an IM and Presence User ID input file

            		 
            ExportContacts.exe -s/LDAPServer -f/input_file -l/logLevel -d/Domain -r/run_mode -i/database_instance

            where:

            • LDAPServer—The IP or FQDN of the AD server where Lync/OCS/LCS users are stored
            • input_file—A text file that contains a list of IM and Presence user IDs
            • logLevel—The logging level, which must be one of the following:
              • error
              • info
              • debug (recommended)
            • Domain—The domain in which the IM and Presence server resides.
            • run_mode—The run mode, which must be one of the following:
              • NORMAL
              • STATSONLY
            • database_instance—The Lync datastore instance name. This parameter is required only when you are exporting contacts for Lync users. You do not need to include this parameter when you are exporting contacts for OCS or LCS users. Sample entries are as follows:
              • Lync Standard Edition server: localhost\rtc
              • Lync Enterprise Edition server: LyncDatastoreFqdn\rtc

            Export the contact list for all Lync/OCS/LCS enabled users in the domain

            		 
            ExportContacts.exe -s/LDAPServer -f/ALL -l/logLevel -r/run_mode -i/database_instance

            where:

            • LDAPServer—The IP or FQDN of the AD server where Lync/OCS/LCS users are stored
            • logLevel—The logging level, which must be one of the following:
              • error
              • info
              • debug (recommended)
            • run_mode—The run mode, which must be one of the following:
              • NORMAL
              • STATSONLY
            • database_instance—The Lync datastore instance name. This parameter is required only when you are exporting contacts for Lync users. You do not need to include this parameter when you are exporting contacts for OCS or LCS users. Sample entries are as follows:
            Note   

            This command exports the contact lists for all Lync/OCS/LCS enabled users in the specified domain, regardless of whether they are migrating to IM and Presence. If you use the UserList<Timestamp>.txt file, which is created from this command, as input to the Disable Account tool and the Delete Account tool, be aware that all user accounts in the domain will be affected by the Disable Account and Delete Account tools.
            Note   

            To ensure correct contact list migration, the owners of the exported contact lists must be completely disabled on Lync/OCS/LCS before you import the contacts lists into IM and Presence.

            What to Do Next

            Disable users on Lync/​OCS/​LCS

            Related References

            Disable users on Lync/OCS/LCS

            This section describes procedures on how to disable a Lync/OCS/LCS account for migrating users and how to verify that Active Directory updates are synchronized to Lync/OCS/LCS.

            Disable Lync/OCS/LCS account for migrating users

            Cisco provides a tool to disable the Lync/OCS/LCS account of migrating users. This tool (DisableAccount.exe) connects to Active Directory (AD) and updates the users’ Lync/OCS/LCS attributes to disable their Lync/OCS/LCS account. Running the Disable Account tool is the first step in a two-step process that must take place to disable a migrating user on Lync/OCS/LCS:

            1. Disable Lync/OCS/LCS account for migrating user.
            2. Delete Lync/OCS/LCS user data for migrating user.

            After you disable the account for migrating user, wait until the Lync/OCS/LCS LDAP changes are synchronized before proceeding with the Delete utility. The LDAP synchronization can take up to 30 minutes.


            Note
            • You can run this tool on all supported Lync/OCS/LCS platforms.
            • You can run this tool on any Standard Edition server or Enterprise Edition front-end server.
            • Running this tool has no affect on the capabilities of other Lync/OCS/LCS users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run this tool during a scheduled maintenance window to reduce the load on the Lync/OCS/LCS and Active Directory system.

            The Disable Account tool accepts three inputs, as follows:

            • The IP or FQDN of the AD server on which the Lync/OCS/LCS users exist
            • An input file containing the list of Lync/OCS/LCS user accounts to disable
            • The logging level, which should be one of error, info, or debug (debug is the recommended setting)

            The Disable Account tool reads the list of users to disable from an input file. Each line in the input file represents a contact list owner. The contact list owner is represented by the owner’s Lync/OCS/LCS SIP URI, for example, sip:bobjones@cisco.com. The following is a sample input file:

            sip:ann@cisco.com
sip:bob@cisco.com
sip:joe@cisco.com
sip@chuck@cisco.com

            You can create your own input file based on the above format. however, Cisco recommends that you use the UserList<Timestamp>.txt file as the input file for the Disable Account tool. The UserList<Timestamp>.txt file will not contain any duplicate, disabled, or nonexistent users.

            After you run the Disable Account tool, the tool generates a unique, time-stamped log file called DisableAccountLog<Timestamp>.txt in the same directory as the tool. The log file contains details about any failures or errors that occurred.

            Before You Begin

            You must have read/write permission to AD to run this tool.

            Procedure
              Step 1   Copy and extract the zip file containing the Cisco user migration tools to the Standard Edition server or Enterprise Edition front-end server.
              Note   

              After extraction, if you move any of the Cisco user migration tools to a different location on the Lync/OCS/LCS servers, you must also copy the version.txt file to the new location to ensure that the tool prints out its current version.

              Step 2   Open a command prompt and change directory to the location of the Disable Account tool.
              Step 3   At the command prompt, enter the following command: 
              DisableAccount.exe -s/LDAPServer -f/input_file -l/logLevel

              where:

              • LDAPServer—The IP or FQDN of the AD server on which the users exist
              • input_file—The file containing the list of Lync/OCS/LCS user accounts to disable, UserList<Timestamp>.txt
              • logLevel—The logging level, which must be one of error, info or debug (debug is the recommended setting)
              Step 4   Check the DisableAccountLog<Timestamp>.txt log file after each execution of the Disable Account tool to ensure that all users were successfully disabled.
              What to Do Next

              Verify that Active Directory updates synchronized to Lync/​OCS/​LCS

              Verify that Active Directory updates synchronized to Lync/OCS/LCS

              After the Active Directory updates are made to disable the Lync/OCS/LCS accounts, the next step is to verify that those updates have synchronized to Lync/OCS/LCS. Verification takes place on the Standard Edition server or Enterprise Edition pool where the disabled Lync/OCS/LCS account was provisioned. You must wait until the Lync/OCS/LCS LDAP changes are synched before proceeding with the Delete utility.


              Note

              Depending on your Lync/OCS/LCS deployment, it may take up to 30 minutes for these changes to synchronize to Lync/OCS/LCS.

              Procedure
                Step 1   Depending on your deployment, do one of the following:
                • If you are using LCS 2005, select Start > Programs > Administrative Tools > Live Communications Server 2005.
                • If you are using OCS 2007 R2, select Start > Programs > Administrative Tools > Office Communications Server 2007 R2.
                • If you are using Lync Server 2010, select Start > All Programs > Microsoft Lync Server 2010 > Lync Server Control Panel.
                Step 2   Depending on your deployment, check the following:
                • For OCS/LCS, select Users and ensure that the disabled user no longer appears in the list of enabled OCS/LCS users.
                • For Lync, select Users and ensure that the disabled user no longer appears in the list of users.
                What to Do Next

                Delete user data from database for migrating users

                Related References

                Delete user data from database for migrating users


                Note

                To delete user data from the Lync/OCS/LCS database for migrating users, you must have read/write access to the Lync/OCS/LCS database.

                Lync/OCS/LCS provides an administrative way to delete a user from the Lync/OCS/LCS database. However, if you delete a user from the database in this way, the user is removed from other users’ contact lists. To prevent the user being removed from the contact lists of other Microsoft Lync or Microsoft Office Communicator users, Cisco provides an alternative means of deleting the user from the Lync/OCS/LCS database.

                This alternative tool (DeleteAccount.exe) allows you to delete migrating users so that presence requests for these users are later routed to IM and Presence. This tool also ensures that the deleted users are not removed from the contact list of any users that remain on Lync/OCS/LCS. Running the Delete Account tool is the second step in a two-step process to disable a migrating user on Lync/OCS/LCS. The two-step process is as follows:

                1. Disable Lync/OCS/LCS account for migrating user.
                2. Delete Lync/OCS/LCS user data for migrating user.

                After you disable the account for migrating user, wait until the Lync/OCS/LCS LDAP changes are synchronized before proceeding with the Delete utility. The LDAP synchronization can take up to 30 minutes.


                Note
                • You can run this tool on all supported Lync/OCS/LCS platforms.
                • You can run this tool on any Standard Edition server or Enterprise Edition pool.
                • Running this tool has no affect on the capabilities of other Lync/OCS/LCS users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run this tool during a scheduled maintenance window to reduce the load on the Lync/OCS/LCS and Active Directory system.

                The Delete Account tool reads the list of users to delete from an input file. Each line in the input file represents a contact list owner. The contact list owner is represented by the owner’s Lync/OCS/LCS SIP URI, for example, sip:bobjones@cisco.com. The following is a sample input file:

                sip:ann@cisco.com
sip:bob@cisco.com
sip:joe@cisco.com
sip@chuck@cisco.com

                You can create your own input file based on the above format. however, Cisco recommends that you use the UserList<Timestamp>.txt file as the input file for the Delete Account tool. The UserList<Timestamp>.txt file will not contain any duplicate, disabled, or nonexistent users.

                Running the Delete Account Tool on Standard Edition Deployments

                When deleting data for a list of users, you must run this tool once on each Standard Edition server. The database is coresident on the Standard Edition server.

                Running the Delete Account Tool on Enterprise Edition Deployments

                When deleting data for a list of users, you must run this tool once on each Enterprise Edition pool. The LCS SQL server name or Lync/OCS database instance name to which the Lync/OCS/LCS front-end connects must be specified when running the tool.


                Caution

                For Lync Enterprise Edition, you must run this tool first on the back-end database server and then on each front-end server. The Lync database instance name to which the Lync front-end connects must be specified in both options. The name of the database for the front-end servers is rtclocal. The default name of the database for the back-end server is rtc, but that can be changed during system installation. For LCS/OCS Enterprise Edition, the tool must be run on only the back-end database server.

                Procedure
                  Step 1   Ensure that you have read/write access to the Lync/OCS/LCS database before you run this tool.
                  Step 2   Copy and extract the zip file containing the Cisco user migration tools to the Standard Edition server or one of the Enterprise Edition pool servers (front-end or back-end).
                  Note   

                  After extraction, if you move any of the Cisco user migration tools to a different location on the Lync/OCS/LCS servers, you must also copy the version.txt file to the new location to ensure that the tool prints out its current version.

                  Step 3   Open a command prompt and change directory to the location of the Delete Account tool.
                  Step 4   At the command prompt, enter the command as follows: 
                  DeleteAccount.exe -s/database_instance -f/input_file -l/logLevel

                  where:

                  • database_instance—The database instance name of the Lync/OCS pool or the SQL server instance of the LCS pool
                  • input_file—The file containing the list of Lync/OCS/LCS user accounts to delete, UserList<Timestamp>.txt
                  • logLevel—The logging level, which must be one of error, info, or debug (debug is the recommended setting)
                  Note   

                  After the command executes, the Delete Account tool generates a unique, time-stamped log file called DeleteAccountLog<Timestamp>.txt in the same directory as the tool. The log file contains details about any failures or errors that have occurred.

                  Step 5   For each Standard Edition server or Enterprise Edition pool, repeat Steps 1 to 3.

                  For troubleshooting tips, see Delete Account tool

                  Step 6   If you are deleting user data from a Lync database you must also repeat Steps 2 to 4 on each front-end server. To access the front-end server database, the command in Step 4 must be run locally on the front-end server. In addition, you must use <front-end_server_hostname>\rtclocal as the value for the database instance parameter.
                  What to Do Next

                  Import contact lists for migrating users into IM and Presence

                  Import contact lists for migrating users into IM and Presence

                  You can use the IM and Presence Bulk Assignment Tool (BAT) to import Lync/OCS/LCS user contact lists into IM and Presence.

                  Complete the following steps to import Lync/OCS/LCS user contact lists into IM and Presence:

                  1. Upload the CSV File Using BAT.
                  2. Create a New Bulk Administration Job.
                  3. Check Results of Bulk Administration Job.

                  Note

                  The default contact list import rate is based on the server hardware type. You can change the contact list import rate by selecting Cisco Unified CM IM and Presence Administration > System > Service Parameters > Cisco Bulk Provisioning Service. However, if you increase the default import rate, this results in a higher CPU and Memory usage on IM and Presence.

                  Before You Begin

                  The procedure to import the Lync/OCS/LCS user contact lists is one of the final steps in the user migration process. Before you import the Lync/OCS/LCS user contact lists, you must complete the following procedures:

                  1. Provision the Lync/OCS/LCS users on Cisco Unified Communications Manager.
                  2. Ensure that the Lync/OCS/LCS users are licensed and assigned to IM and Presence.
                  3. Ensure that the IM and Presence Maximum Contact List Size and Maximum Watchers settings are set to unlimited to ensure all contact lists are fully imported. See Set unlimited contact lists and watchers.
                  4. Run the Export Contact List tool to produce the ExportedContacts<Timestamp>.csv file. See Export of contact lists for migrating users.
                  5. Ensure that the Lync/OCS/LCS users have been fully disabled on Lync/OCS/LCS. See Disable users on Lync/​OCS/​LCS.

                  CSV file upload using BAT

                  You must upload the ExportedContacts<Timestamp>.csv file to IM and Presence using BAT. See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for instructions on how to upload the CSV file.

                  Related Topic

                  Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager

                  What To Do Next

                  Creation of a new bulk administration job

                  Creation of a new bulk administration job

                  After you upload the CSV file, you must create a new bulk administration job in Cisco Unified CM IM and Presence Administration to update the user contact lists. See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for instructions on how to create a new bulk administration job.

                  Related Topic

                  Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager

                  What To Do Next

                  Results of bulk administration job

                  Results of bulk administration job

                  When the bulk administration job is complete, the IM and Presence BAT tool writes the results of the contact list import job to a log file. See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for instructions on how to check the results of the bulk administration job.

                  What To Do Next

                  Deploy an IM and Presence supported client on users desktop

                  Related Information

                  Deploy an IM and Presence supported client on users desktop

                  After you provision the Lync/OCS/LCS users on Cisco Unified Communications Manager and license them for IM and Presence and an IM and Presence supported client, you can install the client software on the users’ desktops. See the Deployment Guide for IM and Presence Service on Cisco Unified Communications Manager for information about deploying IM and Presence supported clients.

                  Related Information

                  Reset Maximum Contact List Size and Maximum Watcher Size

                  Prior to migrating users from Lync/OCS/LCS to IM and Presence, Cisco recommends that you set the Maximum Contact List Size and Maximum Watchers settings on IM and Presence to unlimited. This ensures that each migrated user contact list is fully imported to IM and Presence.

                  After all users have been migrated to IM and Presence, reset the Maximum Contact List Size and Maximum Watchers settings on IM and Presence to the desired values. The system default value is 200 for Maximum Contact List Size and 200 for Maximum Watchers size.


                  Note

                  If you are performing a phased migration of users from Lync/OCS/LCS to IM and Presence, do not reset the Maximum Contact List Size and Maximum Watchers values until all users have been migrated.

                  The following procedure describes how to set values for the Maximum Contact List Size and Maximum Watchers settings.


                  Note

                  If you have a multicluster deployment, you must perform this procedure on each cluster. When you change Presence settings, they are applied to all nodes in the cluster; therefore you need to set them only on the IM and Presence publisher node within any given cluster.

                  Procedure
                    Step 1   Select Cisco Unified CM IM and Presence Administration > Presence > Settings.
                    Step 2   For Maximum Contact List Size (per user), uncheck the No Limit option and enter the desired limit.
                    Step 3   For Maximum Watchers (per user), uncheck the No Limit option and enter the desired limit.
                    Step 4   Select Save.
                    Step 5   Restart the Cisco XCP Router on all IM and Presence nodes in the cluster. To restart the Cisco XCP Router, select Cisco Unified IM and Presence Serviceability > Tools > Control Center – Network Services.