- 入门指南
- 了解 UiPath Robot
- UiPath Assistant
- 安装要求
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- 为高密度机器人设置 Windows Server
- 通过代理服务器重定向机器人
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- 设置 Linux 机器人
- 配置包签名验证
- 设置包文件夹和网络路径
- 配置活动订阅源
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- 集成
- 故障排除
Robot admin guide
Setting up non-persistent VDIs - follow up with Sai
The Robot can operate in both persistent and non-persistent Virtual Desktop Infrastructure (VDI) environments. Each of these setups has special characteristics.
-
In a persistent VDI setup, each user has their own desktop that keeps their data and settings after they log out. In this type of setup, the virtual machine used by the Robot keeps the same settings, configurations, and variables, so they do not change between different login sessions.
-
In a non-persistent VDI setup, users start with a new, clean desktop every time they log in. Since the virtual machine does not save changes, the Robot has to finish its tasks in one session. Alternatively, you can set it up to adjust necessary settings or variables at the start of each session.
The following procedure explain how to set up a non-persistent VDI using the Citrix solution.
To deploy your robots to a non-persistent VDI, you need the following software:
-
VMware vSphere 5.5 or newer, or any L1 hypervisor
-
Citrix XenDesktop, VDA and PVS 6.5 or newer
-
Windows 7 or newer
-
Windows Server 2008R2 or newer - for Orchestrator and other infrastructure machines
-
SQL Server 2012 or newer
-
UiPath Orchestrator
To install a non-persistent VDI, and you need to provide the connection string of the tenant in Orchestrator. All robots that use the same connection string connect to the same tenant in Orchestrator. To obtain the connection string, you need to enable Windows Integrated Authentication in Orchestrator.