Skip to Content
Primo RPA OrchestratorInstallationInstalling and Configuring RDP2 Version 1.25.1.x on Astra Linux 1.7.x

Installing and Configuring RDP2 Version 1.25.1.x on Astra Linux 1.7.x

ℹ️

Information about new configuration options for RDP2 version 1.25.9.x can be found in the article here.

Installing RDP2 and the Service for Retaining RDP Sessions

Connect to the server via SSH as a user with root privileges.

Copy /srv/samba/shared/install/RDP2 to /opt/Primo/RDP2:

cp -R /srv/samba/shared/install/RDP2 /opt/Primo/RDP2

Create the service:

Navigate to the directory /opt/Primo/RDP2

cd /opt/Primo/RDP2

Copy the service file (comes with the package) to /etc/systemd/system:

cp Primo.Orchestrator.RDP2.service /etc/systemd/system/Primo.Orchestrator.RDP2.service systemctl daemon-reload

Place the service in the autostart list:

systemctl enable /etc/systemd/system/Primo.Orchestrator.RDP2.service

Grant execution permissions:

chmod -R 755 /opt/Primo/RDP2

Replace the Orchestrator section in the configuration file with the address of Orchestrator and the user account; use only the rdpservice system user:

alt

If the password for the rdpservice user has changed, change it. The password should be encrypted using a password encryption program.

If necessary, set the value of AddressFilter for filtering by Agent machine, or leave the field blank (all Agents will be used).

The value "RdpClientConnectionUpdateInterval" sets the step/interval of the service’s work in milliseconds, it is not recommended to change it.

The value "MaxSessionsLimit" sets the maximum number of new connections allowed per step/intervalof service operation. This helps smooth the load on the Agent when there are a large number of simultaneous connections. If it becomes necessary to connect N sessions at once (where N > MaxSessionsLimit), only MaxSessionsLimit sessions will be connected in the first step, then another MaxSessionsLimit sessions will be connected after the RdpClientConnectionUpdateInterval step/interval, and so on until all N sessions are connected.

Configure the path to the log file and the log file rotation period (default is one day).

Important: Before starting the service, run the following two commands on all workers (robot machines) where session retention is needed (if they were not executed previously during the worker setup):

alt

Start the service:

systemctl start Primo.Orchestrator.RDP2

Check the service status:

systemctl status Primo.Orchestrator.RDP2

Check the system journal logs:

journalctl --since "2 min ago"

Verify that the RDP session is established correctly.

Session parameters should be set to the following:

Authentication Level = Attempt Authentication
Negotiate Security Layer = True

Configuring the ufw Firewall Rule

Installation and configuration of the ufw firewall are described in the article: ufw Firewall.

To allow access to the RDP2 API, execute the following command:

ufw allow 5102/tcp

Updating the RDP2 Service

Stop the service:

systemctl stop Primo.Orchestrator.RDP2

Update the RDP2 files on the machine (the file RDP2-linux.zip should be located in the /srv/samba/shared/install directory):

unzip -o -u /srv/samba/shared/install/RDP2-linux.zip -d /opt/Primo/RDP2 -x appsettings.ProdLinux.json appsettings.json rdpclientexternalsettings.json chmod a+x /opt/Primo/RDP2/Primo.Orchestrator.RDP2

Start the service:

systemctl start Primo.Orchestrator.RDP2

View the service status:

systemctl status Primo.Orchestrator.RDP2
Last updated on