Posted by 3 months ago. 4 users have great experience and 0 issues when using the VM when jumping in. I will be attaching a screenshot of the notification pop-up of what the 2 users are seeing. (I haven't exhaustively tested this, just on one server and with one account.) You must log in or register to reply here. Google brought me to: I really do not want to go through the trouble of reapplying this RDP server license to the server again. Same issue as :

I would like users to login from any Computer into the Server 2019 RDS and not a work group device cals.Well that KB article has now been updated to reflect Microsoft's change in position. It was only until 2019 that we get the 60 minute warning message.Please point me to the documentation where this was changed.Our company has been using this article to deploy RDS CALs to workgroup computers.https://support.microsoft.com/en-us/help/2833839/guidelines-for-installing-the-remote-desktop-session-host-role-serviceRun the following command to set the licensing mode.2019 does not allow to use this command, whereas with previous version it has.If you want to Use Per User Cal on a Server 2019 what will you need to install? On the File menu, click Add/Remove Snap-in . Please refer to this post: This site uses cookies for analytics, personalized content and ads.

Remote Desktop Device Cal License Not Assign -There is problem with your remote desktop license and your session will disconnect in 60 min Hello, We are using …

I would assume that all users would get this if it is a license issue. If you try to use RDS 2019 Per User CAL in a workgroup (not in a domain), then the RDSH server will forcibly ending a user session every 60 minutes with a message: “Remote Desktop License Issue: There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes”. to to fix this problem'the license server is specified and the "per user" mode is selected. However, 2 of the users are experiencing an issue that i can't make sense of. "Remote Desktop License Issue There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes. Does anyone know a fix to this issue before I redo the license? Remote Desktop License Issue (Disconnect in 60 minutes) Thread starter Carson Alexander; Start date Mar 15, 2019; Mar 15, 2019 #1 C. Carson Alexander. login to the local account on the server through RDS and then don't get the warning. You can change the Remote Desktop Services Session by following steps: To open the Local Group Policy Editor as an MMC snap-in. Window Server 2019 Remote "There is a problem with Remote Desktop license, and your session will be disconnected in 60 minutes" Close. We want to deploy few new rds servers on server 2019 but it seems that the per user licensing is not working correctly if in aEvertime when a user logs in it gets the following message:https://social.technet.microsoft.com/Forums/windowsserver/en-US/e69d9a47-1e2a-4d37-8073-97327ac91154/problem-with-windows-server-2019-rds-license?forum=winserverTSWe have been using per user CAL's on workgroup servers, on every version of Windows server (even on 2016). 0. By continuing to browse this site, you agree to this use.There is a problem with your Remote Desktop license, and your session will be disconnected in 60 minutes, Contact your system administrator

(Click Start , click in the Start Search box, type mmc , and then press ENTER .) I’ve tried it with the final WS 2019 and the licensing diagnose is not showing problems. Someone help! So it seems in future we'll have to have users logging into a domain account. Window Server 2019 Remote "There is a problem with Remote Desktop license, and your session will be disconnected in 60 minutes" I have created a Window 2019 server and applied RD User CAL. When these 2 users jump in they get a prompt that says in the next 60 min. There are a total of 6 active users that work in my onsite server and use as a VM, through an RDP 10 license user. Contact your system administrator to fix this problem." Here is the situation I am in. By default, Remote Desktop Services Sessions are set to 1 hour.