- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Deploying the Robot to multiple machines
You can deploy Studio, Robot, and Assistant to multiple virtual or physical machines using various mass deployment tools. The steps to follow differ depending on the infrastructure and deployment tools used in your organization. There are a few general principles to consider before deploying, such as making sure that the target computers:
-
Meet the hardware and software requirements.
-
Run on the same operating system.
-
Are part of the same network group.
-
Have access to the resource from which the installation will be pushed.
Options available for mass deployment include:
-
Redistribute the installer through high-availability network storage.
-
Deploy through System Center Configuration Manager (SCCM).
When using SCCM, take into account that:
-
The version that is installed must match the version that is advertised.
-
The installation must be performed from the command line in silent mode.
-
-
Deploy through Group Policy.
-
Deploy through Remote Desktop Services.
-
Deploy though third-party solutions such as PDQ Deploy.
-
Deploy through Citrix DaaS.
