we are working on developing a hosting solution for customers. Our goal is to have one ORCH to run different tenants and their robots. Every tenant logs in as their own administrator and can thus manager their own licenses for un/attended/Free robots. We just provide the infrastructure and the ORCH.
We figured that we will need an ORCH license and let the customers to buy and manage their own licenses through the Settings at their own leisure. This works great.
After upgrading to 2017.1 SP1 (in-place install, old version 2017.1) we find that the ORCH license does not pass through to the tenants anymore. Each tenant shows that the license is expired and thus no robots can be scheduled to run. We updated the license for what we believed to be our top site (not the default host as it turns out), but the rest of the customers are still expired.
Does the new version of ORCH require a license for each tenant? Or have we missed something during the installation?
By the way, we have disabled Multitenancy in web-config. We expose the websites directly to our customers and don’t want them to click “become a tenant” - that’s our job to create it for them. I hope this is not related to our issue.