I would like to install the Robot on another machine. So I found that Setup.
So I wanted to run:
Silently install the Robot as a Windows service and connect it to Orchestrator: UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterService CONNECTIONSTRING=https://platform.uipath.com/api/robotsservice/GetConnectionData?tenantId=1 /Q
But what is my connectionstring and the tenantId? I was looking for info in my account. But there is no URL neither an ID. How to get them now?
I have a Tenant under Services. Is this now the new “Tenant” area?
So what is on manage Tenants results for me in this connectionstring: CONNECTIONSTRING=https://platform.uipath.com?tenantId=SERVICENAME /Q.
With that command the Robot and Studio is installed silently. But there is no connection active when I start UIRobot. I think the connectingstring is wrong or does not exist anymore? What I’m doing wrong?
If you have just one tenant ID will probably be just 1. This is part of your connection string and you will be able to see it once you do these changes:
To use the connection string to deploy Robots to Orchestrator, the following are required:
•the WindowsAuth.Enabled parameter from the web.config file has to be set to true
•the WindowsAuth.Domain parameter has to be set to a valid domain
•the Robot machines you want to deploy have to be in the Active Directory domain which was specified in the WindowsAuth.Domain parameter
Thanks but what is there connectionstring good for then? I mean if I create that connection, which advantages I have with that? I still have to set the machinekey, don’t I?
So why should some install with connectionstring over the robot.exe auth with the machinekey. I still didn’t get the point of those both machanics. Could you describe and differenciate them please?
Not sure if this is the right answer for all, but in our case, where we have a larger pool of machines in Citrix it helps as with the connection string we can run just one script to connect all of them to Orchestrator.
You will still need to provision the robots beforehand in Orchestrator, but the machine key is not required anymore for the connection.
Sounds interesting but how does it work with authentication? Wouldn’t be anyone be allowed to use it with that connectionstring? Could you make a step-by-step on what you have done. Maybe also a way without Citrix because I won’t be using it.
I don’t understand your concern. What do you mean anyone could use it? This would involve that anyone has access to your robot.
Steps below, after installing all components:
Provision your machine and robot to Orchestrator
Connect your robot to Orchestrator as instructed here: Connecting Robots to Orchestrator . Due to internal reasoning we have created a script with this command which is executed when machines are started.
But everyone can run UiRobot.exe --connect -connectionString https://platform.uipath.com/api/robotsservice/GetConnectionData?tenantId=1? There is nothing secret, not the url, not the id that always seems to be 1.
Sorry but I’m totally confused now Cristina. And the machine/robot is provisioned in Orchestrator.
Ohh and what does the followings mean. Are these simple parameters in UiStudio?
the WindowsAuth.Enabled parameter from the web.config file has to be set to true ;
the WindowsAuth.Domain parameter has to be set to a valid domain;
Orchestrator and the Robots need to be part of the same Active Directory domain
I’m using latest Studio. Having the Community edition.
What is the web.config file of Orchestrator? That sounds like a very specific thing of your environment? Ok so the identification is located in that web.config file, that makes sense.
Ok, I understand the confusion now.
If you are using the Community edition you will not have access to configure Orchestrator, as this is controlled by UiPath. I am not even sure they provide a connection string, considering the number of tenants they host.
With Enterprise you have full control of all the components.
No matter the version, in regards to secuirty, all configurations are encrypted and safely stored in a database sitting behind Orchestrator.
Thank you that makes sense. If so the UiPath documention is totally incomplete and should be clearified. Ok so we will get Orch licence soon and then I will have another look at the installation process. Very confusing stuff here with all these licencing stuff and old docs.