we found the below content from the UI Path Licensing training and trying to understand the implications of the same, can some one please help
Extract from UI Path Academy
Named User and Concurrent User licenses cannot coexist within a single Orchestrator tenant. As a result, the most suitable licensing model needs to be selected out of the two.
Does that mean that if we procure a node locked/named license now for studio we can not have that license managed through orchestrator at a later point along with other concurrent user licenses we intend to use based on the orchestrator?
Extract from UI Path Academy
As stated earlier, all the acquired UiPath Platform licenses can be managed through Orchestrator. For that reason, all the platform licenses must have the same anniversary date.
We are not completely clear about the implications of this? Does that mean that all the licenses managed through orchestrator (Orchestrator license, Robot license, Studio License) needs to have the same start date?
Named User and Concurrent User licenses cannot coexist within a single Orchestrator tenant. As a result, the most suitable licensing model needs to be selected out of the two.
Q: Does that mean that if we procure a node locked/named license now for studio we can not have that license managed through orchestrator at a later point along with other concurrent user licenses we intend to use based on the orchestrator?
A: On the same Orchestrator tenant you can have either Named User or Concurrent licenses.
If you have concurrent studio licenses in Orchestrator and as well Node-locked stand alone licenses, you can request to add those on the Orchestrator license. Same thing if you have Named User licenses in Orchestrator and Named User stand-alone licenses. Now, if the license model for stand alone is not consistent with the license model in Orchestrator you can:
-convert all licenses to the same model by contacting the sales rep
-divide the licenses in 2 orchestrator tenants: one with Named User licenses and one with Concurrent licenses.
But at this point I would ask what is the use case of having different license models for studio in the same company/ department? (usually Node-locked and Concurrent licenses are designated for employees working in shifts)
2.As stated earlier, all the acquired UiPath Platform licenses can be managed through Orchestrator. For that reason, all the platform licenses must have the same anniversary date.
Q:We are not completely clear about the implications of this? Does that mean that all the licenses managed through orchestrator (Orchestrator license, Robot license, Studio License) needs to have the same start date?
A:No, just the end date needs to match. If you acquire an Orchestrator license in January and in March you want to purchase additional robots to be added on the Orchestrator, you would pay for the additional licenses just a fraction of the one year subscription (corresponding to the time frame between March and next January). This is done by pro-rating the second order. Or you can decide to extend the initial licenses till March. Either way, the end date of all products belonging to a centralized license should have matching expiry dates.
If we have Unattended Robot Node-Locked and Studio - Named User licenses, now we would like to purchase Orchestrator to schedule the bots. so what kind of licenses do we have to purchase now to use the Orchestrator? (is any license required for tenant) @ovi