Share Unattended Robot license

Hello everybody

We have 1 unattended robot license on one specific robot server. We’ve got new process requests that cannot run on the current robot server because of security requirements. Applications which shall be automated are in a different subnet, which cannot be accessed from outside. So, we need a new robot server within this subnet to fullfill the requirements.

Actually, we don’t have many automation processes for both robot servers and no argument to buy a further license. The idea comes up to share the robot license between both servers depending on the process.

Does anybody of you know a concept of realising that?

We actually have only 2 weak ideas to do so. First one is to shut down the unused server, e. g. per day. That doesn’t sound like a good idea.
The second one is to “switch” the active server within the orchestrator. But this would need human interaction…

Thanks for your help

Hello @Enrico_S!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly