Licensing of Bots should be per Orchestrator instead of per Tenant

i_completed
orchestrator
r_18_3

#1

In Orchestrator 2017.1 Enterprise edition, we have to specify in advance that how many tenants we will be using and Bots per tenant. This restrains us to add more tenants in future as it will be a license change. Also if there are bots available in one tenant but none in the other then it cant be used in the latter. Instead it would have been easier if licensing was limited to number of Bots in an Orchestrator instead of going till Tenant level.


#2

I think this is deliberate to prevent over-use of one Orchestrator license - e.g. across multiple companies. You can use Organisation Units to separate different business areas under the same license.

Appreciate your point though.


#3

It’s a long debate.

When we’ve implemented multi-tenacy we thought of it as infrastructure simplification only…It’s a feature that let’s IT admins to manage easily multiple Orchestrator installations (only one instance actually)… and tenants would not share any data. Now, we’re reconsidering if we should go with units or allow the possibility of moving licenses across tenants.


#4

From a functional perspective, I agree that you want tenants separate.
But there are reporting benefits to using tenants for business units within the enterprise.
And a true multi-tenant hosting site may find it easier to administer licenses across tenants.
So I think Robot licensing at the Orchestrator level (or at least the ability to move licenses across tenants) is needed.


#5

Completely agree. Managing licensing at Tenant is lot of pain from administration prospective, as you need to finalize in advance what is required at tenant level, ask for multiple licenses and manage multiple licenses (i.e. changes in licenses etc.). License at Orchestrator level provide flexibility.

On bit different note, I believe focus should be to provide more features (to increase scope for automation) in Product rather than bring license management related changes - which are forcing customer to waste more time in understanding / managing licensing.


#6

stay tuned for 18.3


#7

I thought releases were half yearly :stuck_out_tongue:


#8

we changed our mind :slight_smile: we want to move faster so expect 4 per year.


#9

I totally agree with you Badita. I find Units more useful and apt when i want to isolate data between business units. Plus it helps me in sharing the licenses between them at any point of time. But What I don’t understand is, why is it kept as an experimental feature ? This is stopping me from using this feature even-though I need it badly.


#10

Done in 18.3 (Host Licensing)