Main Process
The main process of the agent is the one corresponding to the executable “Aranda.ARC.Workstation”. When launched from the agent it will look like this:
Windows
MacOS
This process is responsible for communicating with the main server, managing the agent’s internal database, as well as launching the processes of the ARC services that need to be executed.
User Interface Process
When you enter the agent UI, you will see a “Aranda.ARC.Workstation.UI” process for Windows within each logged in session. The process will belong to each user, like this:
In the case of MacOS the process that will be displayed is “Aranda Remote Control”
There will only be one process per user session. This process is in charge of launching windows, icons, questions with a graphical user interface.
ARC Service Processes
Remote control
The process in charge of allowing remote control in Windows is the one corresponding to the executable “Aranda.AVS.VNC.Application.exe”.
Two processes will be visualized as follows:
For MacOS, the processes that are executed correspond to “arcvnc” and will be displayed as follows:
Main Service (Windows only)
When the ARC agent has been installed, the following Windows service will be displayed for the agent:
This service points to the executable “Aranda.ARC.Workstation.exe”
As can be seen, this service must be started automatically to allow functionalities without depending on a session.
Additional Services for ARC Services (Windows Only)
Remote control
When the ARC agent has been installed, the following service must be available for remote control:
This service points to the executable “Aranda.AVS.VNC.Application.exe”
This service is launched by the “Aranda.ARC.Workstation.exe” executable service, so its boot must be manual.
Halting Processes
Regardless of the way the agent has been launched, if the agent is stopped correctly, it will in turn be responsible for stopping all the processes and services launched during its operation.
Internal communication between processes and services
For the aforementioned processes it is important to be able to send and receive messages. To do this, a GRPC communication is used in which each process listens on an internal port, without configuring firewall rules and without remote or external access to the computer; it is a local communication between processes.
The ports mentioned below are static. The agent will attempt to use those ports locally; however, in case they are busy, the agent will not work properly until the ports are available.
Main Process
The main process of the executable “Aranda.ARC.Workstation” tries to listen on TCP port 5050. On this port, it receives responses from the interaction with the graphical interfaces of the user processes “Aranda.ARC.Workstation.UI.exe” for Windows and the “Aranda Remote Control” process for MacOS, as well as notifications from remote control services and user confirmation requests (if enabled).
File transfer process (windows only)
The main process of the executable “Aranda.AVS.Transferfile.Service.Target.exe” tries to listen on TCP port 5029. On this port, responses are received from the interaction with the file transfer between the workstation and the specialist.
Remote Control Process
The remote control process “Aranda.AVS.VNC.Application” on Windows, “arcvnc” on MacOS attempts to listen on TCP port 9087 when running within a user’s session locally. There it receives requests to start a remote control session. In this case, the agent attempts to use port 3478 for communication; is the only port that must be allowed to egress to the Internet in order to communicate with the Turn Server.