Virtual Machine
- Home
- Virtual Machine
On-Premises Setup
Setting up your Virtual Machine
If the process we are automating for you (the customer) uses a software or application that can only be accessed locally from your network, a virtual machine will be required. This VM will not only be used to access your systems, but will also host the workforce agent that needs to be installed on your machine.
Security Concerns
For any Security Concerns
The following page provides all documentation and links regarding the security of the Robocorp workforce agent: Robocorp Security Page.
Additional Info
Security is built directly into our development lifecycle, by performing both automated security scans and red team style penetration tests on every build and deployment. For more information on our security, check out our Trust and Security page.
Scenarios Where We Cannot Automate via the VM
Virtual Machine (VM) within a VM
Example: You use a VPN and Remote Desktop to access another client’s systems, and we’re expected to connect through 2 VPNs (both yours and your client’s) in order to connect. We do not build in the use of a VPN into our automations. A VPN should only be used when our developers are doing development on the machines.
Attended (Supervised) VMs
Unattended access to the VM for development purposes is needed for the automation. We’re needing you, the customer, to allow us the freedom to access the VM without supervision.
“Black Box”
An outbound connection is needed for the Robocloud Workforce Agent to function. The customer will need to whitelist the connection in accordance with the Robocorp Firewall and Network Proxy Requirements mentioned above.
Citrix/Remote Desktop
The module cannot use remote desktop or Citrix to log into multiple locations from one central location. If the access is controlled and distributed via Citrix or a Remote Desktop, we cannot automate it.
