I am having a huge problem with radmin server 3.5.2.1. It doesn't render any image when the remote pc lid is closed. I've changed the power settings to ensure that windows does nothing when the lid is closed, however everytime I connect to a lid closed notebook, all I get is a black screen. As soon as I open the lid the server starts rendering images. How do I resolve such an issue?
Any suggestions?
1. open device manager
2. in "System devices" find "ACPI lid"
3. Open "ACPI lid" properties, and go to "Driver" tab.
4. Sel ect "Update driver"
5. Choose "Browse my computer for driver software" and "Let me pick.."
uncheck "Show compatible hardware"
6. And now...in "Manufacturer" sel ect "(Standard system devices)" and model:
"Volume manager" (yes, "Volume manager")
7. next, next, restart the system and it works!
------------------------------------------------------------------------------
I couldn't find volume manager, so I used this alternative solution: Changing the "ACPI lid" device driver to Microsoft Basic Display Driver instead and it appears to fix the issue with shutting the lid as well:In your device manager this shows as having an error which is fine since you don't want the ACPI Lid device to do what it's doing. As an added benefit, with the Basic Display Driver selected for the ACPI Lid, you can now disable the device which will hopefully keep it fr om updating, repairing, etc. I have no idea what other functions this might disable. Since it's ACPI, it's likely just power savings, but with the lid closed, this driver being non-functional may leave your screen turned on, so you might want to use some type of burn in prevention like a screen saver or screen off.
+++++++++++++++++++++++++++++++++++++++++++++
Nonetheless, I think this shold be addressed by the radmin development team which should send the correct command to ACPI Lid so that it turns on the display even when closed.
+++++++++++++++++++++++++++++++++++++++++++++Thank you for this information.
Using the Microsoft Basic Display Driver (which I accomplished by using Device Manager to delete the active proprietary driver, allowing Windows to install Basic) is a workaround, if you can tolerate the really poor performance of that driver.
My workaround is to leave the laptop lid propped open enough that the display turns on.
I would very much appreciate an update to this issue. I have my suspicions that the issue relates to a display driver architecture update implemented in Windows 10 v1803. I have to believe that RAdmin developers understand what is going on.
Developers - how about being more forthright and telling your customer base just what is going on here?