Orchestrator is typically licensed through either a host license or an organization-level license, by a system administrator.
However, there are certain functions in Orchestrator that require that administrators or users of Orchestrator understand and work with other types of licenses, which allow the use of various features. These are called service licenses and, of these, of particular interest is the runtime.
This page covers strictly the licensing aspects of interest to Orchestrator administrators and users for using Orchestrator.

Licensing concepts

---

To learn more about the various types of licenses, see:

• Plattformlizenzierung
• Benutzerlizenzierung
• Service licensing.

Licensing permissions

---

Several permissions are available to allow a user to perform the various license-related actions described on this page:

• License - Edit or License - Create - enables you to activate or update licenses
• License - View - enables the See More buttons on the License page, which allow you to see details about the licensed Robots in their corresponding page. The View Robots button is also available on these pages if you also have the Robots - View permission.
• License - Delete - enables you to remove licenses.

Licensing steps

---

A licensing process most commonly starts with activating your Orchestrator license, as explained here. If you want to manage your licenses at host level, activate your Orchestrator license and allocate them as explained here.

Afterward, all you need to do to activate a Robot license is to connect the Robot to Orchestrator.

Bei Studio gibt es zwei Möglichkeiten:

• You can activate its license directly from Orchestrator. This is the recommended method.
• You can activate it locally and then connect Studio to Orchestrator through its Robot. Remember to select the Stand-alone license checkbox when creating your Robot, to prevent Orchestrator from allocating Studio a license from its pool of licenses.

Lizenznutzung

---

There are several ways to monitor license usage from Orchestrator:

• If you want to assess whether there's room for maximizing licensing efficiency, you have the possibility to monitor historical licensing data on the Tenant > Monitoring page, by selecting License from the Section list.

• In the License page, the total number of runtimes available on all online machines is displayed. Remember that a machine consumes the licenses as soon as the Robot Service starts.
  To instantly release a license, disable the machine from the corresponding License page. Please note that you cannot use Studio or the Robot on a disabled machine.
  Eine deaktivierte Maschine wird auf der Seite Roboter durchgestrichen angezeigt:

 

How many runtimes to allocate

---

Although license management is typically performed from the administration interfaces, in Orchestrator you do work with a particular type of license: the runtime, which is a service license for robot use.

Runtimes are the licenses you need to run unattended automations. You allocate runtimes when you create a machine object in Orchestrator. There are two aspects to know when allocating runtimes:

• Number of runtimes: You can assign a custom number of runtimes to a machine object (standard machine, or machine template), which determine the number of processes that can run at the same time on a machine.
  The number required runtimes is given by the number of jobs you want to allow to be executed at the same time on this machine; it is not impacted by the number of robots on the machine.
  Let's say you have a machine template with 10 Production (Unattended) runtimes allocated to it. For each workstation that is connected using the machine key of that template, 10 Production (Unattended) runtimes are reserved from the available licenses at the tenant level, allowing for executing 10 jobs at the same time. From these reserved runtimes, a runtime is only in use during job execution. So if you connect 4 machines to Orchestrator using that template, you need and reserve 40 runtimes at the tenant level. With, for example, 25 jobs running, 25 out of the 40 reserved runtimes are in use, leaving 15 runtimes that are reserved, but unused.
• Types of runtimes: The types of runtimes that are assigned to a machine object determine the types of processes that can run on that machine.

Runtimes for classic folders

Because for classic folders you can have several Robot entities on the same machine, it is important to understand that more Robots does not mean more execution capacity. For that you need more runtimes.

Wenn Sie zum Beispiel auf einem Computer mit 5 Robotern nur 3 Laufzeiten definieren, bedeutet das, dass nur 3 Lizenzen in Anspruch genommen werden. Wenn Sie 5 Jobs ausführen oder die Ausführung aller Roboter auf diesem Computer zeitlich planen, passiert Folgendes:

1. 3 Jobs werden auf den ersten 3 lizenzierten Robotern ausgeführt;
2. die restlichen 2 unlizenzierten Roboter werden in einen ausstehenden Status versetzt;
3. die ersten 3 Roboter geben ihre Lizenzen frei;
4. the remaining 2 Robots are licensed and they execute the assigned jobs, leaving one license reserved, but not in use.

Wenn Sie auf einer Maschine nur einen einzigen Unattended- oder NonProduction-Roboter haben und der Maschine 30 Laufzeiten zuweisen, dann werden 30 Lizenzen verbraucht, wenn diese Maschine online ist.

If a Windows 7 machine has 10 users (Robots), you can only execute one process at a time, and you have to leave the number of runtimes to its default value, 1. If you assign more than 1 runtime to a Windows workstation machine and try to execute multiple jobs at the same time, errors are thrown.

If the UiPath Robot service is running on a given machine, it is displayed as licensed. If there are no more licenses available, the machine is not licensed.

Alle Maschinen, die als unbeaufsichtigt definierte Roboter haben, werden auf der Seite Unbeaufsichtigt (Unattended) oder KeineProduktion aufgelistet, zusammen mit der Anzahl der zugeordneten Laufzeitumgebungen, der Anzahl der definierten und ausgeführten Robotern und dem Lizenzstatus der Maschine. Zusätzlich können Sie die Anzahl der einer Maschine zugeordneten Laufzeitumgebungen bearbeiten und eine Liste der auf dieser Maschine definierten Roboter anzeigen.

📘

Wichtig!

Wenn eine Maschine online, aber nicht lizenziert ist, versucht sie eine Laufzeit mit jedem Heartbeat zu erwerben.

Lizenzablauf

---

Ablaufwarnungen

By default, you are notified 180, 90, 30, 14, 7, and 1 day before the license expiry date. You can configure these values using theSystemJobs.LicenseExpirationAlert.DaysBefore app setting.

At host level, for single licenses distributed across multiple tenants, only the system administrator receives these email alerts. At tenant level, all the active users with License - View permission receive them. The emails are localized per user.

Übergangszeitraum

Nach Ablauf Ihrer Lizenz wird Ihnen ein Übergangszeitraum gewährt, in dem Sie Ihre Lizenz ohne Betriebsunterbrechung erneuern können. Bei der Anmeldung wird eine Benachrichtigung angezeigt, die Sie über Ihre abgelaufene Lizenz und die Dauer des Übergangszeitraums informiert:

Sie können die Benachrichtigung schließen, indem Sie auf OK klicken und die Arbeit wie gewohnt fortsetzen. Nach Ablauf des vorgeschriebenen Übergangszeitraums verliert Ihr Orchestrator die Lizenz und funktioniert nicht mehr.