robot
2021.10
false
- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Windows Sessions
- Login Using Thales Luna Credential System
- Login Using NShield Key Storage Provider
- Redirecting Robots Through a Proxy Server
- Executing Tasks in a Minimized RDP Window
- Using Mapped Network Drives
- Stopping a Process
- Disable Stop Button
- Custom Package Folders and Network Paths
- CrowdStrike Integration
- Troubleshooting
- Unresponsive Robot Over RDP
- Duplicate Execution Logs
- Frequently Encountered Robot Errors
- Increased Process Execution Duration
- Enforced Package Signature Verification
- Message Too Large to Process
- Errors When Running as Administrator
- NuGet Packages Not Accessible After Migration
- User Access Control Prompt and UI Automation Activities
- .NET6 Projects Fail to Run
OUT OF SUPPORT
Robot User Guide
Last updated Nov 11, 2024
Using Mapped Network Drives
To make your work easier with shared network folders, you can map network drives for quick access on your user account. However, if the processes you publish from Studio are located on that drive, the situation described below occurs.
The issue occurs when you use a mapped network drive for your packages. The location of the packages you publish to Orchestrator
can be seen in the
UiPath.settings file on the Robot machine, under the NuGetServerUrl parameter. The mapped network drive is available to the user that created it, while the Robot Service runs system-wide.
You can convert the Robot from Service-Mode to User-Mode by running the
.MSI installer and choosing the User-Mode during update.
Check out the Updating the Robot guide for more details.
- Download the Sysinternals Suite. It contains the
PsExec.exetool, which is required for this operation. - Open an elevated Command Prompt instance.
- Use the
cdcommand to navigate to the location where you downloaded the Sysinternals Suite (such ascd C:\Downloads\SysinternalsSuite). - Use the
PsExec -i -s cmd.execommand. A confirmation dialog appears. - Click the Accept button to install the
PsExec.exeservice. This makes it possible to map a network drive for the Local System. - Use the
net use z: \\ServerName\SharedFolder /persistent:yescommand to map the drive, where ServerName is your server and SharedFolder is the location of the drive you want to map.
If you want to remove the mapped network drive, you need to repeat the steps above, but using the
net use z: /delete command instead. You can find out more on this page.
