Read and Review Automation Anywhere Documentation

Automation Anywhere Version 11.3

Close Contents

Contents

Open Contents

Migration: FAQs

  • Updated: 5/07/2020
    • 11.3.x
    • Explore
    • Enterprise

Migration: FAQs

Find answers to questions on specific scenarios related to migration.

  1. Are the schedules created by a user existing in the destination Control Room or deleted from source Control Room migrated?

    No, these schedules are not migrated.

    • If an Active Directory user who created a schedule in the source, exists in the destination, then the first run of the migration shows the status for Schedules as Failed because of the following reason:
      Unable to continue as the user with same name already exists
    • If a non-Active Directory user who created a schedule in the source does not exist or is deleted in the destination, then the first run of the migration shows the status for Schedules as Failed because of the following reason:

      User <username> for this schedule does not exist

    For more information on migrating users, see Select users to migrate.

  2. IQ Bots and My Lists are deprecated from 11.2. What happens to the bots that have IQ Bots as dependent files or the files that are present in My Lists?

    IQ Bot dependency and My Lists are filtered out because they are deprecated in 11.2. These are not listed in the preview.

    For more information on migrating bots, see Select bots to migrate.

  3. I am currently on Control Room LTS and I want to migrate to Control Room 11.2. What happens to the Repository Path field value?

    The Repository Path remains the same and this field is disabled after migrating to 11.2.

    For more information on providing the source Repository Path details, see Connect to source Control Room database.

  4. I have migrated from Automation Anywhere 11.2 or earlier 11.x version to Automation Anywhere 11.3. What are the precautionary steps to recover schedules, which had disappeared in version 11.2 or earlier 11.x versions?

    Once you upgrade to version 11.3, for schedules that already exist and are visible in the Schedules page, we recommend that you first deactivate and then reactivate those schedules so that they do not go missing in the first week from the Schedules page.

    Important: (This note applies to the 11.x version before Version 11.3.2). You can deactivate and then activate only those schedules that were initiated on different weekdays than the present day. For example if a weekly schedule is set to run on Monday and the initial execution of the schedule is also Monday at 13:00 hrs, then first deactivate/activate it on any day other than Monday. You can deactivate/activate on Monday only after it runs at 13:00 hrs. See table for reference:
    Schedule name Schedule date, day, and time Action
    Schedule-1 01/07/19, Monday, 13:00 hrs Do not deactivate and reactivate. Perform this action only after the schedule runs.
    Schedule-2 01/08/19, Tuesday, 13:00 hrs Deactivate and then reactivate
    Schedule-3 01/09/19, Wednesday, 13:00 hrs Deactivate and then reactivate

    For details on how to recover the schedules, see topic Recover schedules post upgrade after upgrading to Automation Anywhere Enterprise 11.3.

    Customers upgrading from Automation Anywhere 11.2.1 need not perform the recovery steps given in the topic as the issue was fixed in that version.
  5. What are the specific considerations for migrating from 10.x to Version 11.3.x.x?

    Control Room provides a built-in migration tool that allows existing customers to migrate their data from earlier versions of Automation Anywhere viz. 10 SP2, 10 LTS to Version 11.3.x.x. For versions before 10 LTS (10.3), customers will have to undergo a two-step migration process – first upgrading to 10 LTS and then to Version 11.3.1.

    Attention: Data can be migrated only from one SQL database instance to another SQL database instance for Control Room DB and from PostgreSQL instance to another PostgreSQL instance for Bot Insight DB.

    Migration from Microsoft SQL Server to Oracle Server for Control Room DB and PostgreSQL Server to Microsoft SQL Server for Bot Insight DB is not supported in the current version.

  6. Version 11.3.3 What are the specific considerations for migrating the Historical Activity from version 10.x to version 11.x?
    • You must migrate the corresponding Users and Bots from version 10.x. See Select bots to migrate.
    • You must log in with the same migrated user, using the same Device or Client with the same Fully Qualified Domain Name (FQDN) as that of 10.x.

      For example: If John was logged in MY-DEVICE-NAME.COM device in 10.x, the same user in 11.x, John must be logged in to the same MY-DEVICE-NAME.COM device.

  7. Version 11.3.3Is it possible to migrate the Historical Activity using API?

    Yes, migration of historical activity is supported by API and UI both.

  8. Version 11.3.3My machine is affected by virus and is destroyed. Will I be able to migrate the Historical Activity?
    No, you cannot migrate the Historical Activity. You require the same machine to migrate the Historical Activity. The migration process can also fail if the same device is unavailable due to the following reasons:
    • If the virtual machine is destroyed.
    • If the same machine is used but the host name is changed.
Send Feedback