Message boards : GPUs : Windows, GPU and Remote Desktop
Message board moderation
Author | Message |
---|---|
Send message Joined: 17 Feb 13 Posts: 13 |
When I connect to my PC using Remote Desktop, BOINC stops crunching GPU tasks and reports that GPU is not available. I read a bit about this and found that this is limitation of a WDDM drivers, or as someone wrote a "Windows feature". I am OK with this. Unfortunately GPU stays unavailable until I came to my PC and login locally, what usually happens many hours after I closed my Remote Desktop session - all these hours are lost for GPU tasks. Do you know if there is some software which will restore access to GPU after I close Remote Desktop session? Or maybe there is some hidden Windows option for this? |
Send message Joined: 5 Oct 06 Posts: 5128 |
WDDM drivers (Windows Vista and onwards) run in the logged-on user's security space, and that is destroyed when a different user logs on - eg through remote desktop on desktop computers (computers running Windows Server allow local and remote users to log on at the same time, the last time I tried). You need to do one of two things: 1) Ensure that the normal logged-in user is logged back in after your remote session finishes. Depending on your security environment, can you use AutoAdminLogon to boot to your local account directly? If so, set it up, and issue a 'restart' instruction when you end the remote session. 2) Switch to a different remote access solution. Many varieties of VNC are available, including for free (I've used http://www.tightvnc.com/), and don't suffer from the same security restrictions as Microsoft's offering: ie, they don't destroy the GPU driver environment. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.