Lars Clausen
asked on
Ekstra monitor turns off when users are connected to terminal server
Hi Experts.
I have a issue with a few users. They have a laptop computer with 2 external monitors. When then connect to our terminalserver using RDP the second monitor turns off after a few minutes, and cant be turned back on again unlead the power it off and on.
It seems like windows is not seeing any activity on the monitor, and therefor puts it to sleep. They are running Windows10x64 ENT
Any suggestions?
I have a issue with a few users. They have a laptop computer with 2 external monitors. When then connect to our terminalserver using RDP the second monitor turns off after a few minutes, and cant be turned back on again unlead the power it off and on.
It seems like windows is not seeing any activity on the monitor, and therefor puts it to sleep. They are running Windows10x64 ENT
Any suggestions?
Go to control panel, power options, change turn off Monitor after to "Never"
ASKER
I dont think thats an option for us, as it´s the company policy to have monitors go to standby after 15 min.
Well, sometimes things have to change... I had to make a new group policy which extended it and then drop machines in that group
Your only other option is to move your TS session over to that screen... if you don't want to do that then if you minimize your MSTSC connection to the TS server and then click on the monitor (move your pointer over to it) it should wake up again.
Cheers
Alex
Your only other option is to move your TS session over to that screen... if you don't want to do that then if you minimize your MSTSC connection to the TS server and then click on the monitor (move your pointer over to it) it should wake up again.
Cheers
Alex
ASKER
Hi Alex.
The strange part here is that not all users are affected by this. Its only a 5-6 users out of 100-120 users.
I know there is a GPO setting the monitor stand-by somewhere, may bee i could tweak it somehow.
The option of minimizing the RDP windows and thereby making activity on the secondary monitor is off corse a solution. I just think its strange, because i can be on a RDP session for hours without my monitor switching off
The strange part here is that not all users are affected by this. Its only a 5-6 users out of 100-120 users.
I know there is a GPO setting the monitor stand-by somewhere, may bee i could tweak it somehow.
The option of minimizing the RDP windows and thereby making activity on the secondary monitor is off corse a solution. I just think its strange, because i can be on a RDP session for hours without my monitor switching off
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You have not described yet, if the monitor reawakens if you move the mouse to it.
ASKER
The monitor does not wake up again, the user has to unplug the power to get it working again.
Interesting. I use remote desktop heavily and I have two screens - never seen that. Do you have any power management software installed from the manufacturer of the computer, maybe?
ASKER
I agree, this is very strange. I have 3 monitors, the build-in in my lenovo w541 and 2 samsung connected to my dockingstation and have never seen this behavior before. There is not any other power management somftware installed other than the Windows power options. I will contact the user today and see if a driver/bios update can solve anything
ASKER
It seems the problem has disappered over night for all the users. It looks like an windows update somewhere has fixed the problem..
Thanks for the help guys
Thanks for the help guys
it was probably a driver update, which I specified a few days back :-p
ASKER
Perhaps, but the computers affected are not identical :-D
That's not really an issue, I'm guessing they are all using intel processors, more than likely i5 or i7's, therefore they would use the same driver package for the GPU. Therefore they don't have to be identical :-p
ASKER
True, i think they all are i5 and some HD4000. It stille is strange that only a handfull clients where affected considering i have 100-120 client connecting to the the same terminal server and they alle more or less have the same Lenovo clients
Exactly, some could have a different base image which has an older driver etc etc/