Customize device settings
Customize the settings for user devices at the device level such as device lifespan, auto-login, screen resolution, deployment, and other advanced options.
These configurations are available for editing only if the settings are enabled by the Control Room administrator.
- Navigate to .
Select the setting tab for configuration at the device level:
Update the Nickname and
Description parameters, and select either
Temporary in the General
Device lifespan can be Persistent or Temporary. Temporary devices are created to support non-persistent virtual desktop infrastructure (VDI) and are automatically deleted after a specified time when the device is disconnected from the Control Room. You can specify the time to automatically delete temporary devices in the Control Room devices settings.
Persistent devices are created to support persistent virtual desktop infrastructure (VDI) and are not deleted after the device is disconnected from the Control Room.
To update the settings for Auto Login to run bots on user sessions at the device level, select
Use custom settings.
Either create new user sessions or use existing user sessions after a bot finishes running.You can customize the auto login settings at the device level only if the allow a user to change these settings individually for each device in devices page option is enabled by the Control Room administrator.
Update the Screen resolution settings for
existing device sessions.
The screen resolution settings are used to begin user sessions at the resolution specified in this setting. You can customize the screen resolution settings at the device level only if the allows users to override the resolution option is enabled by the Control Room administrator.Note that the screen resolution settings are applicable only when you use RDP-based deployments. For regular deployments, a Windows session is created using the existing resolution settings of the device. In this case, the screen resolution set in the Control Room is ignored.Recommendation: When resolution-dependent packages are used to build bots, any difference in screen resolution between the Bot Creator and Bot Runner devices will affect the bots at runtime. Therefore, ensure that the resolution settings on devices match when you create and run bots.
Update the Deployment settings for single or
multiple user devices and use the Use custom
settings option to set the threshold settings for CPU
and memory utilization at the device level.
For single users installed at the system level, the default deployment type is regular; you can change this to RDP. For multiple users installed at system level, the default deployment is RDP. For single users installed at the user level and multiple users at the system level, you cannot updated the deployment type.Note: If the Windows setting Restrict Remote Desktop Services users to a single Remote Desktop Services session is enabled for RDP in the local group policy, a user is connected to an existing session instead of creating a new session when the user uses RDP to verify bot deployments.For multiple user devices, additionally configure the Concurrent sessions supported. The minimum concurrent session value is 2.You can customize the threshold settings only if the enable threshold settings option is enabled by the Control Room administrator.
Update Log collection configuration to configure
log collection level, log file size, number of archived logs, and
synchronize log collection settings.
Collect logs for three levels: information to collect messages that highlight the progress of the application, debugging information that is useful to debug an application, and tracing logs to capture application behavior in detail.Define the maximum log file size for a single log file. A new log file is created after the file is archived.Define the number of archived logs files that can be generated. The archived log file is retained for a day. For example, Node_Manager-2022-Mar-30-1.log.zip.Set values and synchronize log collection configuration across devices from the Control Room to capture logs with more information or debug any observed behavior.
Update the Advanced Options at the device level
such as auto-login timeout, bot launcher JVM options,
console readiness wait time, bot response wait time, RDP
command options and log collection by selecting the Use
Note that you can customize these advanced options only if the allow changes in the edit device page option is enabled by the Control Room administrator.
- Auto-login timeout enables you to set a wait time for a bot to deploy. After this wait time, an error is shown.
- Bot launcher JVM options enable you to send dynamic properties supported for Java. For example, you can use this option to increase the memory of the bot launcher.
- Maximum simultaneous downloads enable you to set the number of simultaneous downloads. For example, 5 downloads including dependent files.
- Console readiness wait time enables you to set a wait time for the console to be displayed when you run a bot. After this wait time, an error is shown.
- Bot response wait time enables you to set a wait time for an active bot session. After this wait time, an error is shown.
- RDP command options enable you to provide different RDP-based commands, for example, ports-related commands.
- When the log collector option is selected by the Control Room admin, the device can send logs to the Control Room.
- Update the Nickname and Description parameters, and select either Persistent or Temporary in the General Settings.
Click Save changes.
If the user device is offline, these changes take effect when the device reconnects to the Control Room.