Remote desktop licensing mode is not configured

your response is simple. You don't need to install the role RDS. if you only need 2 session which mean you don't need the installation of the role RDS. What you need to do is simple, juste remote all Role RDS on the server and after removing all the role RDS, you just need to activate the remote connection and that's it. 

If you install the RDS role, you will have install all RDS functionality, so the need a license server.

I hope that's help.

Final Notes:

• Since you're working with a workgroup server (not part of a domain), you won’t need domain-based Remote Desktop Licensing.
• If you require more than two concurrent RDP sessions in the future, you’ll need to configure RDS licensing correctly, either through Per User or Per Device licensing, and possibly set up a Remote Desktop License Server.

Disable the RDS Licensing Warning

Since you mentioned that you only need two concurrent RDP sessions and don't require CALs (Client Access Licenses), the following approach can help you disable any licensing warnings or issues:

1. Modify Group Policy to Disable Licensing Warnings:
2. Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
3.  

Remove the RDS License Key (If Applicable)

If your server has been in the grace period and you don't intend to use a license server, you might have a Remote Desktop Services license that is being enforced. Removing this license can help resolve the issue:

1. Open PowerShell as Administrator:
   • Run the following command to remove the existing RDS license (if present)
   • tslicensingdiagnostics /remove

   • Restart Remote Desktop Services:

     • Run the following commands to restart the necessary services
     • Restart-Service -Name TermService

     • Reset the Licensing Grace Period (Optional)

       If the grace period for RDS is expired, and you don’t need additional licenses, you may be able to reset the grace period.

       1. Open the Registry Editor (regedit):
          • Navigate to the following ke
          •  

Step 1: Check Remote Desktop Licensing Mode

Since you only need two concurrent RDP sessions and don't require additional licenses, the best approach is to configure the server to use the Per User or Per Device licensing mode, or simply to leave it without configuring a licensing mode if you don't need to enforce licensing.

1. Open the Local Group Policy Editor:
   • Press Win + R, type gpedit.msc, and press Enter.
2. Navigate to the RDS Licensing Settings:
   • In the Group Policy Editor, go to the following path:
   • Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
   • Configure the Licensing Mode:
     • Look for the "Set the Remote Desktop licensing mode" policy.
     • Set this policy to Per User or Per Device, depending on your needs.
     • Note: Even though you only need two connections, configuring licensing to "Per User" or "Per Device" should prevent the licensing mode from triggering issues.
   • Configure the Licensing Server (Optional, if you decide to install a Remote Desktop License Server):
     • If you ever decide to install a license server, configure the licensing server by setting the "Use the specified Remote Desktop license servers" policy. You can point to a local RDS License Server, but since you don't need more than two concurrent sessions, this step may not be necessary.

3. Verify Licensing and Grace Period

   If your system is still in the grace period, you should be able to log in. However, once the grace period expires, it will block additional sessions unless a valid license server is configured.

   1. Check the RDS Licensing Grace Period:
      • Run the following PowerShell command to check the licensing status
      • Get-WmiObject -Class Win32_OperatingSystem | Select-Object Caption, LicenseStatus

      • Check Event Logs:

        • Open Event Viewer and navigate to
        • Applications and Services Logs > Microsoft > Windows > TerminalServices-RemoteConnectionManager > Operational