Skip to main content
Version: 10.3.2

Activate RDS licensing for multiple bots

While the platform supports running multiple bots on a single server concurrently, it is important to ensure you have the correct infrastructure, operating system, and Microsoft licenses.

View system requirements​

To run multiple bots on one machine, your Window Server OS must be one of the following versions:

  • Windows Server 2019
  • Windows Server 2022

You may also need RDS Per User Client Access Licenses (CALs) for your Windows Server.

tip

We recommend running no more than 16 bots per Window Server concurrently to ensure smooth performance. Each bot requires at least 1 CPU and 2 GB RAM.

Ensure that the following ports are open for Remote Desktop Session Hosts to obtain licenses:

  • TCP/135: Microsoft RPC
  • UDP/137: NetBIOS Datagram Service
  • UDP/138: NetBIOS Name Resolutio
  • TCP/139: NetBIOS Session Service
  • TCP/445: SMB
  • TCP/49152–65535: RPC dynamic address range
tip

To check open ports, use PortQry or Test-NetConnection.

Use RDS CALs​

To use Windows Server OS and Remote Desktop Services (RDS) to manage bot sessions, you must purchase licenses. Each bot on the server requires a User CAL. RDS CALs are installed on the RD licensing server that keeps track of license usage. When a bot tries to connect to the RD Session Host server, the server checks if it has a valid CAL. For more details, refer to License Remote Desktop Services with Client Access Licenses.

caution

The Work.AI platform needs RDS Per User CALs and not RDS Per Device CALs.

You can purchase CALs for Windows Server 2019 or 2022 from a reseller.

note

Each bot requires a license for each application it uses, for example, Microsoft Office.

You can run the platform with multiple concurrent bots without RDS CALs during the 120-day RDS grace period. The installer activates bots automatically. However, you must purchase RDS CALs before the grace period expires to remain compliant.

Activate RDS license​

There are two scenarios to activate an RDS license:

  • When there is only one server and no RDS CALs were previously activated
  • When an RDS license server already exists on another machine

Scenario 1. Activate RDS license for the first time​

Follow these steps to activate an RDS license for the first time. The platform should be installed on this server.

The example below is based on Windows Server 2016. Other versions can have slightly different menus and interfaces.

Install roles and features​

  1. Open Server Manager.

  2. Click Add roles and features.

  3. On the Before You Begin tab, click Next.

  4. On the Installation type tab, select Role-based or feature-based installation and click Next.

  5. On Server Selection, choose Select a server from the server pool, select your server, and click Next.

  6. On the Server roles tab, select Remote Desktop Services and click Next.

  7. Go Features > Remote Server Administration Tools > Role Administration Tools > Remote Desktop Services Tools and select the Remote Desktop Licensing Diagnoser Tools and Remote Desktop Licensing Tools options. Click Next.

  8. Go to Remote Desktop Services > Role services and select the Remote Desktop Licensing and Remote Desktop Session Host options. Click Next.

  9. On the Confirmation tab, click Install.

  10. Once installation is complete, click Close and restart your server.

Edit group policies​

  1. Open Server Manager.

  2. Go to Tools > Remote Desktop Services and open Remote Desktop Licensing Diagnoser.

  3. Note the name of your server.

  4. Open Edit group policy.

  5. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing.

  6. Open Use the specified Remote Desktop license servers.

  7. Select Enabled, enter your server name in the License servers to use text box, and click Apply > OK.

  8. Open Set the remote Desktop licensing mode.

  9. Select Enabled, choose Per User, and click Apply > OK.

Activate license server and install RDS license​

  1. Open Server Manager.

  2. Go to Tools > Remote Desktop Services and open Remote Desktop Licensing Manager.

  3. Right-click your server and select Activate Server.

  4. In the Activate Server wizard, click Next.

  5. On the Connection Method screen, select Automatic connection (recommended) and click Next.

  6. On the Company Information screen, enter the required information and click Next.

  7. Provide optional information if needed and click Next.

  8. On the Completing the Activate Server Wizard screen, uncheck Start Install Licenses Wizard now and click Finish.

    Your server status should now show as Activated.

  9. Right-click your server and select Install Licenses.

  10. In the Install Licenses wizard, click Next.

  11. On the License Program screen, select License Pack (Retail Purchase) and click Next.

  12. On the License Code screen, enter your license code, click Add, then Next.

  13. Complete the installation.

Scenario 2. Configure RDS license using existing license server​

If your organization already has an RDS license server, you can use it.

Once the RDS license server is activated and running on another machine in your organization, reconfigure the RD session host to obtain CALs from it. You can set the licensing mode and specify the license server name using the Server Manager GUI, PowerShell, or Group Policy (GPO).

  1. Open Server Manager > Remote Desktop Services > Collections. In the Tasks menu, select Edit Deployment Properties.

  2. On the RD Licensing tab, select the remote desktop licensing mode and the RDS license server. Click Add, then OK.

If licensing type is not configured, you can see the error: "The licensing mode for the Remote Desktop Session Host server is not configured".

Verify license server status​

To check the license server status and issued licenses, go to Administrative Tools > Remote Desktop Services > RD Licensing Diagnoser.

If no warnings appear and you see the message "RD Licensing Diagnoser did not identify any licensing problems for the Remote Desktop Session Host server", the RD Session Host server can successfully receive RDS CALs.