HI SimonMiles,
Did you ever find out what was wrong? We got the exact same issue, both for external- and LAN users on our brand new WinSRV2022 RDSH.
Greets!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We've recently installed a Server 2022 as a Remote Desktop Server.
We have a load of Mac users, some laptops, some desktops who connect using the Microsoft Remote Desktop app from the app store.
We are finding that when a user gets disconnected, whether its VPN drops out, or the Mac goes to sleep and closes the RDP connection, when that user tries to log back into their remote desktop session, they get a black screen.
If I try and connect to that session on the server, the black screen appears for me too. I also notice the network information bar shows 1 or 2 bars out of the 4.
To get the user back signed in, I have to manually close the Windows Logon User Interface service (I think thats what its called)
Some of these users are connecting on the local network over wireless and some are connected with an ethernet cable.
Really odd. Has anyone else seen this before?
Many thanks
HI SimonMiles,
Did you ever find out what was wrong? We got the exact same issue, both for external- and LAN users on our brand new WinSRV2022 RDSH.
Greets!
Thanks for helping! We did not utilize RemoteFX though. We managed to pinpoint the issue to the fact that RDS licensing role was installed on the RDS session host itself. After migrating the licensing server & reinstalled the licenses the black screens went away.
Couple of weeks later we had similar issues with a different client, also WinSRV2022. Turned out that it was RDS licensing role again. Moved it, problem solved.
Hope this helps!
Same here, 4 W2022 RDSH, fully patched, 54 users, about 2-3 times per day, frustrating
Good afternoon to you both
Nope, never did find the issue.
The client doesn't get it so often now but it appears to be linked to Mac devices connecting wirelessly!
Many thanks
Simon
Hello i had the excat same issue, and i found that this fixed our problem.
Kind regards.