Requirements for robot VM

VM(s) access 
 

• Access to HQ server (20.224.22.20) tenantname.headquarters.robotiq.ai through the following ports (VM and Host (if exists) firewall): 
  • 443 - HTTPS traffic 
  • Execute command prompt command: ping api.robotiq.ai – to verify VM is set up properly and traffic is passing through (ping can be accessed through port 80).
• The restriction on accessing api.robotiq.ai via the WebSocket protocol must be removed to ensure proper communication between the system and the API
•  Localhost TCP communication must be unhindered on ports: 
  • 32788 (Credential provider)
  • 0-65535 (Handler chooses any AVAILABLE port in range)
• AD account for the Robot with the following characteristics: 
  • The password should not expire and should not contain the special character ";"
  • Robot username at VM without white spaces in the name (e.g. “robot1” or “RobotCompanyName1”)
  • The robot user must be able to log in via an RDP session. A prerequisite for using an unattended robot is that the robot user has interactive login enabled.

Virtual machine (VM) characteristics

Minimal requirements

▪ Intel® Core™ i7-3770 or better
▪ 8 GB RAM or more
▪ 100 GB hard disk or more
▪ VM resolution – 1920 x 1080 – this should be adjusted as default on VM 

Fixed requirements

▪ Windows 10 PRO or Enterprise or Windows Server 2022 (or older, supported by Microsoft)
▪ Microsoft Office
▪ Chrome web browser (the HQ web application is optimized for Chrome)
▪ Installed .NET framework 4.7.1 or higher
▪ .NET6 runtime is not necessary to install because it is shipped in installation (self-contained 
mode)

Local admin permissions on the VM(s) 

REQUIRED

• Local admin account needs to install software on the VM. Software itself does NOT require Admin account (some software utility capabilities will be hindered)
• Secure Sign-In (the user must press Ctrl + Alt + Delete on the lock screen before 
  the Sign-in process begins) must be disabled at Robot VM

OPTIONAL: If Robotiq.ai software (Digital worker) has access to Admin credentials, 
then several features are available, which include:

• Robot update on demand 
• Installation log streaming
• Additional features in the future 
• If Digital Worker (Robot) is instructed to execute an admin action as a part of a business process (advised to check with process owner if it is necessary to have admin rights to execute the process), admin access is required since this is a constraint set by Windows OS. 
• Development Robot is part of Unattended Robot installation. It is not permitted to install Development Robot on a VM where Unattended Robot is already installed, and vice versa.

To confirm whether the Robot's VM meets all the necessary requirements, please refer to this document for instructions.