Running bots with multi-session

Currently, IBM Robotic Process Automation, runs all bots in the computer's console session, which means that they all run in the same Windows session/user.
When several bots are run concurrently, if these bots use surface automation (OCR, mouse, and keyboard simulation), interference between bots may occur.

With the new multi-session feature, IBM Robotic Process Automation takes advantage of Windows Server's ability to have more than one user simultaneously connected to the machine using Remote Desktop Protocol to run each bot in a different user session. 
Since each Windows session has its own isolated environment, concurrent executions will not interfere with each other.

Enabling computer to use multi-session

IMPORTANT: The computer must have the Windows Server or Azure Windows 10/11 Enterprise Multi-session operating system.
For more information, see the Microsoft Azure Virtual Desktop documentation and Microsoft documentation.

First, you must create a credential pool with the credentials that will be used to run the bots.
NOTE: You must be a Tenant Administrator, Business User or have the Manage credential pool permission.

On the IBM Robotic Process Automation Control Center, you should navigate to the Credentials page, click on the Credential pools tab and click on the Create credential pool button.

Give the Credential pool a name and select the credentials that will be part of it.

Now, you should navigate to the Computers page and create or edit a computer.
Click on the Enable multi-session login button to enable the multi-session for the computer.
Select the Credential pool that will be used to run the bots on the computer.

NOTE:

• This feature will only work if the IBM Robotic Process Automation Client v30.0.1 or higher is installed on the computer.
• Remote Desktop Session must be enabled on the computer's Windows.
• When you enable the multi-session login, the standing by runtimes setting will be automatically disabled.
• The computer capacity will be automatically configured according to the number of credentials defined in the selected Credential pool.

Configuring Windows policies

You need to configure some Windows policies:

1. Press the Windows key or click the Start menu.
2. Type gpedit.msc and press Enter.

• Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits > All options
  • should be Enabled and Never
  • This configuration allows IBM RPA to manage the sessions created for bot execution.
• Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections >  Limit number of connections
  • should be Enabled and enter the number of maximum connections based on your need
  • This configuration defines the number of simultaneous connections to the server.
  • Windows Server gives only two sessions per computer (for free), for more licenses, you need to enable Remote Desktop Service Licensing and buy more Windows licenses. For more information, see Microsoft documentation.
  • IMPORTANT: If the credential pool has more credentials than Windows allows for simultaneous connections, some bots will fail with the message: “Could not connect to server 127.0.0.1. There are too many users signed in.”
• Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Restrict Remote Desktop Services users to a single Remote Desktop Services session
  • should be Enabled
  • This configuration will ensure that each user has only one session on the computer, resulting in better performance for bot execution.
• Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Allow users to connect remotely by using Remote Desktop Services
  • should be Enabled
  • This configuration will enable the Windows Remote Desktop Session feature.

Be sure all users associated to the credential pool have access to Remote Desktop Session

#RoboticProcessAutomation(RPA) #IBMRPA #Automation