- Getting Started
- Installation and Upgrade
- About Backward and Forward Compatibility
- Hardware and Software Requirements
- Deployment guidelines
- Mass-deploying Studio and Robot to Multiple Machines
- AWS Deployment
- Azure Marketplace Deployment
- Deploying unattended automations
- Updating the Robot
- Setting Up Windows Server for High-Density Robots
- Services the Robot Connects to
- Configuration files
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Specific Scenarios
- Governance
- Troubleshooting
- Robot Service troubleshooting
- Execution troubleshooting
- Recording and Remote Control troubleshooting
- Networking troubleshooting
- Connection troubleshooting
- Licensing troubleshooting
- Package troubleshooting
- .NET troubleshooting
- Logging troubleshooting
- Session troubleshooting
- CrowdStrike integration troubleshooting
Mass-deploying Studio and Robot to Multiple Machines
Mass deployment options for installing Studio, Robot, and Assistant on multiple machines, with the requirements those machines must meet and the conditions for deploying through SCCM.
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.