-u/--user. See the CLI Options Specification.
Desktop->Read Only menu item. It is useful when more users share the same desktop or when you want just to view the desktop without interacting with it.
||The Refresh Daemon is a background process which
keeps the desktop session alive. If you don't move your
mouse or type a key for a long time, the remote server
usually runs a screen saver or locks up the desktop. Some
desktop servers are also known to close the connection after
a period of idle time. The daemon simply moves your mouse
back and forth by one or two pixels after the configured
idle time (5 minutes by default) to prevent these
The daemon doesn't run while a script is being executed. This is intended to prevent unwanted interference into the script execution. There's a flag in the preferences allowing to change this behavior and run the daemon even during automation.
||The Connection Recovery mechanism repairs broken
desktop connections during script executions. The framework
automatically puts on hold any I/O operations (mouse,
keyboard) and makes a few attempts to reconnect to the
desktop until the specified time expires. If the connection
gets recovered successfully the script resumes execution.
This mechanism targets recoverable connection errors such as for example intermittent network outages. It won't help if the target server crashes and it does not get restarted automatically by the SUT.
The recovery feature is by default off and must be enabled through the Desktop Preferences prior to the script execution.
||The Connection Pooling
mechanism allows the executed test scripts to release the
desktop connection to the pool after the use rather than
destroying them (disconnecting). Such connections may be
then picked up by other scripts. This approach avoids the
overhead of the desktop connection and it may significantly
improve performance (while increasing the memory
requirements) of multi threaded automated testing
applications, especially where multiple shorter test scripts
are executed against just one or a few test environments.
Operation of the connection pool requires a license with at least 2 connections (seats). For details see the RemoteDesktopClientFactory class documentation. To find out how many seats your instance is licensed to see the Tool->License Key Manager window.