Skip to main content
Question

Automation Anywhere On-Prem – License Expiry, Renewal, and Vendor Control

  • January 7, 2026
  • 0 replies
  • 12 views

Forum|alt.badge.img+1

Hello everyone,

I would like to get some standard information and learn from your experience regarding license lifecycle management in Automation Anywhere On-Prem environments.

We are using Automation Anywhere On-Prem, and I was not involved in the initial system setup. Because of this, I would like to better understand how license-related scenarios are handled in practice.

Specifically, I would like to clarify the following points:

  • What happens when licenses expire in an On-Prem setup?

  • How does the license renewal process work technically (license files, activation steps, possible downtime, etc.)?

  • If certain licenses are stopped, removed, or frozen, how is this reflected in the Control Room?

  • What is the impact on existing users, bot runners, and running automations?

Additionally, since this is an On-Prem deployment, I would like to understand the vendor-side involvement:

  • Even in an On-Prem environment, can Automation Anywhere remotely deactivate or restrict licenses?

  • Is there any permanent or periodic connection between our Control Room and Automation Anywhere for license validation or enforcement?

  • Or is license control fully managed on our side unless we explicitly apply changes (e.g., new license files)?

In the Cloud version, these flows are more transparent. However, due to the On-Prem nature of our setup and my limited visibility into the initial configuration, these questions have become important while managing the environment.

If you have experience with license renewals, expirations, audits, or vendor interactions in an On-Prem Automation Anywhere setup, I would really appreciate it if you could share your insights and best practices.

Thank you in advance.