![]() ![]() When you try again (or just immediatelly cancel the connection and reconnect), the connection may or may not go through. The connection is never successfully estabilished when this happens and it is closed without any errorĬouple minutes later. The problem is that in 30-50% of the connection attempts via these gateways, the connection is stuck at the "Configuring remote session" message. We have a new WS2016 RDS deployment (VMs on Hyper-V): Or is there any other underlying reason for the black screen phenomenon which I should address? Up with an identical setup no matter what original media file was used, with all the updates? That should be the point of the updates, or not? They have the same update level, just one was installed from a later base media - but it's the same edition. ![]() So is it recommended to make a new install for all session host servers? Do not really understand why I would have to do that. They do, however, all show the same build number in the settings app: 14393.2248. Then converted to Standard edition by inputting a license). Same update status but was installed from later download media (evaluation edition download from internet, Note - I installed an additional session host server recently and noticed that this phenomena does not seem to happen on that one (at least not as frequent). The servers are updated to PT (July 2018). The only solution is to reboot this session host server. Normally, every additional user logging in after this occured also gets the black screen. Sometimes, after 10-15 minutes the user desktop becomes Users can see moving mouse cursor, and they can bring up the Task Mgr with Ctrl+Alt+End. That is, they can successfully log in but then see only a black screen, no task bar, nothing. ![]() Occasionally (that means approx every 7-10 days), new users logging in to RDS get aīlack screen. This is a session-based deployment for RDP sessions. Windows Server 2016 RDS setup with one DC and 3 session host servers, all running as VMs under Citrix XenServer. But with the latest update, it's back.Īny assistance would be greatly appreciated. I had the same problem with an earlier build but there was a patch that fixed it. except for installing the suggested patch because that patch seems to be for 1903 I have also tried all the suggestions at this link changing Local Policy on host machine to Disabled. disabling persistent bitmap caching on client machine in RDP experience tab doing a clean boot with all services disabled except Microsoft, Intel and Acer, plus all startup programs except for core essential reverting back to the Microsoft generic driver by deleting display driver The only way I have found to bring it back is to hold the power off button for 10 seconds, then restart. The monitor power light is blue which indicates the monitor is not in a sleep However, when remote client is disconnected the host remains stuck on black screen and unresponsive to any keyboard input. The connection is then shows the actual screen. I continue to get black screen unless I delete credentials and manually enter the same password as was previously saved. If I disconnect the remote and retry connection If I then try to reconnect, the remote shows the same black screen as the host. My Jump Desktop version is Version 5.0.When I try to connect using RDP the host screen turns black and remains black after remote client disconnects. The thing I am not sure about, is does my imac have this problem because it is OS X, or because its screen resolution is higher than the Win7 PC I am connecting to? Because the only other machine I have to test with is a Win7 laptop whose screen resolutions is less than the Win7 PC I am connecting to. Once the situation is fixed both Microsoft RDC and Jump Desktop work fine, so this does not appear to be a problem with Jump Desktop itself. Once I do that I can connect from my imac again without issue (until I upgrade OS X again, presumably). The workaround is to then connect with a Win7 laptop whose resolution is less than the PC I am connecting to. I can connect multiple times and it happens every time. At this time the connection freezes and when I move the mouse it starts painting black wherever the mouse moves. Then (I presume) negotiation begins about the screen resolution. When it happens the initial connection appears to exceed because I can view a corporate warning about connecting to the network (I connect via a VPN). I think it happens because the screen resolution of my imac exceeds that of the PC. More information: It happens when connecting from my imac to my desktop Win7 PC. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |