Robot tray orchestrator settings - Administration rights

[andan]

Scenario: I Work in a large organization and intend to deploy (using Orchestrator) attended scripts to multiple users. We have packaged UiPath Robot (robot tray) for automatic distribution and set up so that a normal user may apply for access and then have the Robot installed.

However it seems that when a user gets the Robot installed, admin rights are required to update Orchestrator settings with URL and Machine Key. A normal user will not be granted admin rights. I would like to avoid the task of a priviledged user remotely taking over a normal user’s screen and updating Orchestrator settings after each installation. Is there a solution to this? E.g. a setting that removes the admin rights requirement or to “pre-populate” the values during distribution/installation?

Thanks!

[Pablito (Pawel Wozniak)]

Hi @andan,
Welcome to the Community!
If you have administrative privileges you can try to remotely setup robot on user side using power shell (remote scripting needs to be enabled through GPO). List of command you have here:

Arguments Description

[andan]

Hi Pablito,
thank you for your answer. I’ve tried to connect manually from cmd with the command --connect -url [orch url] -key [machinekey] but get an error message ‘A task was canceled’. That’s the same error message I get when attempting to enter the values manually through the robot tray - orchestrator settings interface. Do you have any idea what the problem is?
Thanks in advance
/Anders

[Pablito (Pawel Wozniak)]

Maybe you are typing wrong URL? Please look at the forum banner or here:

New requirements for Robot to Orchestrator connection!

New requirements for Robot to Orchestrator connection! Since latest update of Community Orchestrator please be careful when connecting Robot to Orchestrator. Now you need to provide full address like: https://platform.uipath.com/[AccountName]/[ServiceName] Before you needed to add just: https://platform.uipath.com/ You may find the full address in the address bar when you are on Orchestrator Tenant page. Without providing the full address in this form you will get this error: [imag…

[andan]

The orchestrator we connect to is v2018.4.6 so I don’t think that’s it. I suspect a firewall issue; do you know which ports are used when connecting to orch?

[Pablito (Pawel Wozniak)]

I think you should create ticket for this case here:

Contact Technical Support

[andan]

It works now, we had to open traffic through the firewall on port 443 to the orchestrator host. Thanks for your help anyway.