- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- Control Flow
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- Logging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-NMG-017 - Class name matches default namespace
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DPB-010 - Multiple instances of [Workflow] or [Test Case]
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-021 - Hardcoded Timeout
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-017 - Invalid parameter modifier
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- Coded automations
- Introduction
- Registering custom services
- Before and After contexts
- Generating code
- Generating coded test case from manual test cases
- Trigger-based Attended Automation
- Recording
- UI Elements
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- VMware Horizon Automation
- Salesforce Automation
- SAP Automation
- macOS UI Automation
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Extensions
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for Safari
- Extension for VMware Horizon
- Extension for Amazon WorkSpaces
- SAP Solution Manager plugin
- Excel Add-in
- Test Suite - Studio
- Troubleshooting
- About troubleshooting
- Assembly compilation errors
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Validation of large Windows-legacy projects takes longer than expected
Studio User Guide
Extension for Microsoft Remote Desktop and Apps
By installing the UiPath Extension for Microsoft Remote Desktop and Apps you are capable of natively generating selectors over RDP connections. It can be installed per-user (from Studio or the Command Prompt) or per-system (from the Command Prompt and Studio Installer).
- Open UiPath Studio.
- Navigate to Home > Tools > UiPath Extensions.
- Select Microsoft Remote Desktop and Apps > Install. A confirmation dialog box is displayed.
- Restart your active RDP connection for the changes to take effect.
- The UiPath Extension for
Windows Remote Desktop is now installed and is located at
C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\
.
- Select the Windows
Start button and type
cmd
in the search field. - Right click on Command Prompt and run it as administrator.
- Change the directory to the
UiPath installation folder (
cd C:\Program Files (x86)\UiPath\Studio\UiPath
). - Use the
SetupExtensions /RdpClient
command to install the extension per user, or theSetupExtensions /RdpClientGlobal
command to install the extension per system. A confirmation dialog box is displayed. - Restart your active RDP connection for the changes to take effect.
- The UiPath Extension for Windows Remote Desktop is now installed.
To generate native selectors over RDP connections, you also need to deploy the UiPath Remote Runtime component on the Remote Desktop machine, as explained on this page.
UiPathRemoteRuntime.msi
installer can be downloaded from:
- Product Downloads in the UiPath Customer Portal
- Resource Center in the UiPath Automation Cloud. To access Resource Center, log in to your Automation Cloud Organization and click the Help button on the navigation bar.
For instructions on additional operations you might need to perform while installing or configuring the UiPath Extension for Microsoft Remote Desktop and Apps, see the following:
The Workspot Unified Digital Workplace Platform can be configured to use the same Remote Desktop Protocol (RDP) plugins usually used by the UiPath Remote Desktop client. This documentation page explains the step-by-step process to get the Workspot Client working with the existing UiPath Extension for Microsoft Remote Desktop and Apps.
Prerequisites
- Install the UiPath Extension for Microsoft Remote Desktop and Apps on the client.
- Install the UiPath Remote Runtime on your Virtual Desktop Infrastructure (VDI).
Locate and copy the RDP Registry keys
You need to navigate to your Registry Editor to find and copy the RDP Registry keys.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\UiPathPluginRdp]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp_x64.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\UiPathPluginRdp32]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\UiPathPluginRdp]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp_x64.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\UiPathPluginRdp32]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp.dll"
regedit
into the Run command
(Windows Key + R) to open the Registry Editor. Navigate to the RDP Registry keys
using the paths above, and copy these keys.
24.10.92.62643
, may differ in your case. Make
sure to copy the exact value you find in the Registry Editor.
Paste the keys into the Workspot Registry
UiPathPluginRdp
, UiPathPluginRdp32
) you have
copied. The paths where you need to copy these values for Workspot are:
[HKEY_LOCAL_MACHINE\SOFTWARE\Workspot\Client\PersistentSettings\VDIPlugins\UiPathPluginRdp]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp_x64.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Workspot\Client\PersistentSettings\VDIPlugins\UiPathPluginRdp32]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Workspot\Client\PersistentSettings\VDIPlugins\UiPathPluginRdp]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp_x64.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Workspot\Client\PersistentSettings\VDIPlugins\UiPathPluginRdp32]
"Name"="C:\Program Files (x86)\Common Files\UiPath\UiPath.Common\24.10.92.62643\UiPathPluginRdp.dll"
By pasting these registry keys, you are essentially directing Workspot to the location of the RDP extensions allowing it to use them.