RDS sessions disconnecting after 60 minutes

Ruber Linden 61 Reputation points
2020-08-07T15:52:05.387+00:00

Hi all,

All the servers on my RDS farm are joined to a domain, the licensing server shows no errors on Licensing Diagnostics, but this message is being displayed on all sessions:

"There is a problem with your license for Remote Desktop and the session will end in 60 minutes."

RDS Licensing Server shows that the CALs were assigned to the user, but it keeps showing the error on the sessions, which are disconnected after 60 minutes.

The licensing mode is Per User. I've already set up on the Server Manager, enforced on GPO settings, but still shows the same error.

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

9 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-10T03:22:52.813+00:00

    hi,
    l Have you ever set the session time limits for all user who logged on before?

    If not, here a workaround is to go to Group Policy and try to set session time limit, details shown as below:

    1. Cmd prompt, gpedit.msc
    2. Computer Configuration->Admin Templates-> Windows Components-> Remote Desktop Services->Remote Desktop Session Host->Session Time Limits
      16568-image.png
    3. Enable appropriate group policies and modify as needed
    4. We recommend setting this one because it will prevent disconnected sessions from consuming server resources — “Set time limit for disconnect sessions”
      16614-image.png
    5. After modifying group policies, you can force an update without rebooting by typing “gpupdate /force” at cmd prompt

    plz. inform me if it works well after the setting. And if it’s convenient to you, a clean boot is another workaround we can try.

    --please don't forget to Accept as answer if the reply is helpful--

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Homer Sibayan 131 Reputation points
    2021-01-28T04:26:40.807+00:00

    Hi yvonneyang

    Same Issue here we are encountered. my question is where do i need to go to edit the GPO ? Is it on the Licenses server of RDS ? or in the Session host Server ?

    Thanks
    Homer

    Was this answer helpful?

    0 comments
  3. Tyler 1 Reputation point
    2021-02-02T20:35:35.37+00:00

    If your system is in a domain, then you would go to the AD GPO policy for the OU your system is in and make the changes to the AD GPO, we have a specific OU for our terminal servers and a policy set to that OU, if you have the same, you should make the changes there (note, these changes will affect any other systems that are in that OU and will get the same GPO setting pushed down to them).

    You could do it on the local system if you are not in a domain, you would run gpedit.msc (as is noted in step 1 above) on the local system/terminal and edit the local group policy however, if your domain is pushing the AD GPO, you should make the change there otherwise your domain AD GPO might overwrite your changes on the local system policy...anyone feel free to correct me if I am wrong or clarify if this is unclear....

    Whether it is a Domain GPO or a local GPO you will edit it in the same place with the same setting as listed above.

    Was this answer helpful?

    0 comments
  4. Dominik Bednarski 1 Reputation point
    2021-09-22T22:04:35.683+00:00

    I have the same problem but I do not have AD. On the Windows server 2016 version, it worked correctly with the same licenses.
    Could the reason be the fact that earlier the server had a different naming than today. So I wonder if the license seems to be a different server so they do not want to cooperate?

    In addition, this RDS server 2019 is a virtual machine on HyperV whether it changes anything.

    after I got the time limits and it still doesn't work,

    Please help.

    Was this answer helpful?

  5. Charles Thivierge 4,201 Reputation points
    2021-09-24T16:01:19.43+00:00

    To be able to use RDS with User CAL, the RDSH and the RD License Server must be joined to an Active Directory Domain.

    The Licensing Server must be member of the Active Directory "Builtin\Terminal Server License Servers" group.

    The License Server must be activated and must have RDS CAL that match (or newer) the RDSH server version.
    Ex: A Windows 2012 RDSH will require a RD RDS CAL 2012 or 2016 or 2019

    The licensing server can manage RDS CAL that match the OS or a previous version
    Ex: a license server running on a Windows 2016 server can support RDS CAL 2016 or 2012...

    If you look in Active Directory users & Computers and open the user account that was supposed to receive the RDS CAL, if you click on the Attribute Editor tab, you should see several attributes starting with msTS...

    Look for the following attributes:
    msTSExpireDate --> The expiration date (Date -60 days should gives you when the user has receive the license)
    msTSManagingLS --> This match the ProductID of your License Server

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.