Windows 2016 RDP Connection Issue

Question

Hi, We are using Windows-2016 Server for our application & Windows-10 Desktop computers are connected on RDP with Server. the issue we are facing that, After somedays Windows Server machine wont allow to connect on RDP until restart. Once system restarted, Server Machine will allow RDP Clients the there wont be any issues for some days. After somedays, again machine wont accept RDP connection, it mostly showing "Black Screen".

We checked & couldn't find any specific issue with software / installations. Also, quite surprised, since the behavior is same for 12 Machines which we are using in different building.

Answer 1

Hi Eleven,
Thanks for the details. So how can I resolve my problem. We have similar set-ups in 12 building & all building have similar problem.

The Server (Windows 2016) & Client Machine (Windows - 10) is connected for our application HMI on rdp session.

The Client Machine is having three users Operator, Engineer & Administrator. The server machine is accessed on rdp by one of the sessions from client machine. So with the scenario as explained below, how can we resolve the problem?

• Administrator User Loged in Client Machine
• RDP Connected with Server Machine : 1,2,3,4 & 5 active connections established from same client machine
• Now at this stage, if we disconnect/close /sign out one RDP connection from Client Machine (Its confirmed from Task Manger of server machine)
• At this situation new connection is not possible from client machine
• Once this condition reached, server wont allow any additional RDP connection (Even we disconnect all the RDP connection from client machine)

Since we are using our HMI application, the disconnection & connection of rdp is very much common. To attain the solution, what we can do?

Also, what exactly happens, when server restarting time. Because, once server machine restarted, it allowing new rdp sessions.

Answer 2

Hi,

Thanks for your detailed information. I noticed that all your RDP connections were established from the same client machine. In this secnario, we suggest that you could only install a per-device RDS cal so that the licensing server only needs to issue the cal to this specific client machine. By this way, any user can use this machine to remote connect to the RDS server.

But I am afraid that there might be some RDS configuration issue in your environment. From your description, we do not know if you have set any RDS deployment or there is only one RDS session host role installed and no other RDS roles such as (RDCB, RDWeb, RDGateway).

However, please make sure you have installed RD Licensing role and the licensing server has been activated successfully. After that, you can install the RDS CALs in the licensing server to issue to the device or user. Also, you will need to set the RDS licensing mode and specify the licensing server on the session host server (windows 2016) by editing local group policy. (Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Licensing —— Use the specified Remote Desktop license server & Set the Remote Desktop licensing mode)

If you would like to deploy a RDS environment, please refer to below articles for destails.
https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-deploy-infrastructure
https://nedimmehic.org/2017/01/21/deploying-remote-desktop-services-2016-step-by-step/

Thanks,
Eleven

----------

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 3

Hi Eleven,
Thanks for the reply. I have an insight, Currently we are using Windows 2016 Server with Version 1607 & OS build is 14393.2608. I could find today there is some patch update
February 19, 2019—KB4487006 (OS Build 14393.2828) (microsoft.com)

related to RDP - Black Creen. Is it the case for me??

Answer 4

Hi,

If there is no problem on all above mentioned setting or configuration, we suggest that you should install the latest KB4594441 for improving the working experience and the system security.
https://support.microsoft.com/en-us/help/4594441

Thanks,

Eleven

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Answer 5

Hi Eleven,
Thanks for the details. Can we install directly 4594441 or do we install any pre - requisite for this? also, should we install any other patch prior to this update or directly can be installed?