- Getting started
- Understanding UiPath Robot
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Redirecting robots through a proxy server
- Implementing authentication with credential providers
- 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
Robot admin guide
Updating UiPath Robot
The update process ensures that both Studio and Robot are upgraded to the latest available version.
Before updating your Robot version, check the compatibility matrix.
When planning for an update, keep the following recommendations in mind:
-
Preserve the Robot operational mode: Service Mode or User Mode.
-
Match Robot and Studio versions. Refer to the compatibility matrix for guidance.
-
UiPathRobot.msicannot update an olderUiPathStudio.msiinstallation.
When you have Orchestrator installed on the same machine as the Robot, we recommend updating your Orchestrator version first, followed by the Robot version. To apply the new settings, reconnect the Robot to Orchestrator.
Manual update is done via Command Line.
This option is available exclusively for Enterprise LTS versions of Robot. Community versions are automatically updated to the latest release.
For instance, you can manually update your 2024.10.5 LTS version to the latest 2024.10.9 LTS version. Community installations, however, are always updated to the most recent version, and selecting a specific version is not possible
UiPathStudio.msi or UiPathRobot.msi with default settings. This replaces old files without altering your settings.
C:\Program Files\UiPath\Studio\Packages folder.
UiPathStudio.msi, write:
UiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterServiceUiPathStudio.msi ADDLOCAL=DesktopFeature,Robot,RegisterServiceUiPathStudio.msi or UiPathRobot.msi with default settings. This replaces old files without altering your settings.
UiPathStudio.msi, write:
UiPathStudio.msi ADDLOCAL=DesktopFeature,RobotUiPathStudio.msi ADDLOCAL=DesktopFeature,Robot.xaml files from the original NuGet Packages folder.
Updating the configuration variables requires a Robot restart to take effect, but several changes in Orchestrator settings do not need a restart. These include:
-
RunDisconnectedHours- the number of hours the robot can run offline (disconnected from Orchestrator). -
SignalR settings - parameters related to the SignalR technology used for real-time communication between Robots and Orchestrator.
-
HeartbeatPeriodSeconds- the frequency, in seconds, at which the Robot sends a heartbeat signal to Orchestrator to show it is online. -
NuGet feeds - references to package sources for activities.
RegisterService parameter is added to the ADDLOCAL command.
RegisterService parameter is removed from the ADDLOCAL command.
Administrators can set up policies for automatically updating Studio, StudioX, Robot, and Assistant from Orchestrator. When a policy triggers the automatic update process, the UiPath Update Agent shows an Update Available notification, prompting you to start the update.
In unattended scenarios, the update service verifies that Robot, Studio, or Assistant are not executing any jobs or processes. Once this is confirmed, the update acknowledgment is sent back to the update server, triggering the update process.
Refer to the Update Service for more details.
