Disable using of UDP port 3389 for RDP traffic (it is used together with the default RDP TCP Port 3389 on Windows Server 2012 R2/Windows 8.1 and newer).Or configure more aggressive settings to terminate disconnected user sessions Only a user can end up their RDP session ( CTRL ALT End -> Sign out) or an administrator can forcefully close it (like it is described in the article Remote Desktop Services Is Currently Busy). In Windows Server 2016 with configured RDP session timeouts, I came across user complaints that after trying to connect to a disconnected session it didn’t activate correctly and they saw a black screen.Update the Group Policy settings on your RDP/RDS host To do it, open the Local Group Policy Editor (gpedit.msc) and set Use WDDM graphics display driver for Remote Desktop Connections = Disabled in Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment (or the same in the registry: reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services” /v “fEnableWddmDriver” /t REG_DWORD /d 0 /f). In some cases, you must set using XDDM video driver instead of the WDDM one. Try to use automatic driver update (if you have not disabled it, or download and install the driver manually) Make sure that both your computer and the remote one are using the latest video driver versions.Make sure that caching is disabled in the RDP client settings (disable the Persistent bitmap caching option on the Experience tab) and the screen resolution supported by the remote host is used (set lower screen resolution in the Display tab or try to use the Full Screen mode).If this doesn’t help, open the Task Manager from this screen and run the File Explorer process (File -> Run new task -> explorer.exe -> OK) This sometimes allows you to get back to a desktop in an RDP session.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |