Hi All.
I just thought I would share my recent Windows Server - RDS2016 Hellish nightmare with you.
I have now resolved our issue after an exhaustive search, implementing every possible potential fix for this issue we finally discovered that the black screen disconnecting | server crashing | logoff processes hang & ability to no longer login thereafter were all caused by a Cisco Wireless 8821 Phone being plugged into our client device USB. (Dell Wyse Terminals).
This particular phone was being plugged in by our users to charge the device. However; the device then installed as a NIC on our RDSH. If you then unplugged\plugged in the device eth1 would then disappear and eth2 would appear and so on. It would eventually get to around eth17 and the server was completely deadlocked in terms of logon\logoff and shutdown. Users still working and active were able to continue to do so however the only way the server could be restored was by a reboot.
I also found literally hundreds of NICs listed under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards
Right before the issue occurred for any particular server in the event log TerminalServices-LocalSessionManager > Event 36
> An error occurred when transitioning from DisconnectedLoggedOn in response to EvConnected. (ErrorCode 0x80070102)
> An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070102)
We eventually tied the 2 together after seeing a common device installation on affected collections vs unaffected collections event log TerminalServices-ServerUSBDevices shortly before each reported server deadlock.
I now have a GPO in place to disable installation of this particular device after obtaining the HID (Hardware ID) from my local machine with it plugged in.
I know there are many other causes of black screen particularly in 2016 RDS and believe me we have implemented every other solution for reported black screens thanks to these forums. None of them worked for us until this so i thought i'd share just in case anyone else has similar issues - worth looking at what is being re-directed\installed via the client!
Any additional questions please reply below - I’d be happy to help. I wonder if Microsoft need to patch for this issue in future KBs.