Message boards :
Number crunching :
Windows Server RDP/GPU work around - needs some further input.
Message board moderation
Author | Message |
---|---|
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
Hello everyone, I do not typically post in this section but have found a make shift fix for the GPU RDP issue that throws the "GPU Not Present" error. I looked very briefly to see if this had been posted prior and did not see anything so if I am re-posting something that someone has already posted I am sorry. I have got the issue almost there but just can't figure out one last detail. All of the following Tasks are preformed in the Task Scheduler Library. I have tested several different variations to the re-launch command but it is still throwing the same gpu missing error. To start it off I have scheduled the Task Scheduler Library to close both boinc.exe and boincmgr.exe with the following action "taskkill /f /im boinc.exe" and "taskkill /f /im boincmgr.exe" with the following trigger "On connection to the user session, any user, connection from remote computer, enabled." This command appears to be closing BOINC without a loss of data, I have tracked the progress through a few trails and have not noted any loss. Although input from others would be great. This portion appears to be functioning properly with the correct outcome. ** If someone knows a better command than a force task kill, like a proper close that would be great too. Next I have created a task to launch boincmgr.exe upon disconnect of RDP with the following action "Start a program PATH\boincmgr.exe" the following trigger "on disconnect from user sessions, any user, connection from remote computer." On this one I have changed the conditions to start the task after the computer is idle for 5 Minutes, thinking that it would re-recognize the GPU since the RDP connection had long been released but it doesn't appear to be seeing the GPU. This is where I need input, why isn't the GPU kicking back in after five minutes of RDP disconnect? Am I missing something or is this just not viable? Whew that was painful, let me know and of course happy crunching. -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
If you mean that you're using Remote Desktop then I really think that you won't win. Why not just use 1 of the programs listed in this thread, http://setiathome.berkeley.edu/forum_thread.php?id=73874#1466961, and safe yourself the hassle. Cheers. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
It probably depends what state the user login is left in when the RDP session closes. Is this a true Windows Server, or just the RDP server component of an ordinary Windows Pro machine? It matters, because more than one user can log in to a true server, but RDP into Windows Pro logs out the local user, and you won't be able to do anything until the local user session is re-established. You don't need to worry about the BOINC Manager - the only component that you need to run is the client. And that needs to run in the context of the user logged in to the console, for GPU detection and crunching to work. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
To close BOINC I would use "boinccmd --quit" vs taskkill. I am guessing this is your Windows 8.1 host as there is not currently a GPU on your Server 2012 R2 host? SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
To close BOINC I would use "boinccmd --quit" vs taskkill. The server R2 computer has an NVIDIA GeForce GTX 560M, it works if just the local admin is logged on through the actual machine, but the gpu error occurs with the RDP connection. -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
If you mean that you're using Remote Desktop then I really think that you won't win. I host other applications and VOIP servers on my server and like to keep the server as vanilla as possible for security reasons. I have considered using VNC for another method, but use that server as an RD Gateway for my other computers while at work or school. -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
It probably depends what state the user login is left in when the RDP session closes. Its the computer titled "Lithium" which is running windows server 2012 Data Center or similar. http://setiathome.berkeley.edu/hosts_user.php?sort=rpc_time&rev=0&show_all=0&userid=8444134 -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
To close BOINC I would use "boinccmd --quit" vs taskkill. It has been a while since anyone has brought up RDP issues. So when you have BOINC logged into the console operating normally & a different user logs in via RDP it causes an error, or are the RDP sessions also the admin account? If they are separate account the admin should still be logged in on the server OS. Have you tried just telling BOINC to suspend when there is an RDP session & resume afterward? You could boinccmd to send the run states in the same way you are killing and restarting BOINC now. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
To close BOINC I would use "boinccmd --quit" vs taskkill. The RDP sessions occur with two users, a standard user and the built in administrator account. I have't tried telling BOINC itself to stop with detection of RDP, I didn't know that was possible. Do you think this would pause the state detection of the GPU? I have tried everything short of using VNC, which i stated earlier I did not REALLY want to do because the computer is also the RDP Gateway. -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
To close BOINC I would use "boinccmd --quit" vs taskkill. I was reading some old threads on RDP issues. This one and more so this one, on the BOINC message board, point out an issue that BOINC 7.x has with RDP sessions. BOINC 6.x will suspend GPU processing & resume at the end of a RDP session it would seem. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
To close BOINC I would use "boinccmd --quit" vs taskkill. I was going to download the 64 bit windows BOINC 6 to test it out, but it appears its no longer available. http://boinc.berkeley.edu/download_all.php -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
Unless something was changed and i was not aware. The problem with RDP is not with the windows version itself (after XP of course, with XP you could install the Boinc as a service so RDP works), is the way the windows DL the video driver and the Gforce driver itself. With the GForce drivers you are forced to use a third party program to bypass the Gforce Driver/RDP limitation. This programs creates/uses a new set of video controls who works remotely. I use ThightVNC but there are a lot of others who don´t use the windows drivers and works perfect. FYI That problem does not happening with the NVidia drivers who powers the upper class GPU's like the Quadros or Teslas. So RDP works perfect with this models with no modifications or the necessity to use a third party program. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
To close BOINC I would use "boinccmd --quit" vs taskkill. Try here http://boinc.berkeley.edu/dl/?C=M;O=D The 6.12.43 release is the most recent one, but with 6.10.60 being the version before that. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I was reading some old threads on RDP issues. This one and more so this one, on the BOINC message board, point out an issue that BOINC 7.x has with RDP sessions. BOINC 6.x will suspend GPU processing & resume at the end of a RDP session it would seem. The first one of those was more about 'install as a service', the second one more about 'fast user switching'. Both of those create problems for GPU crunching which are very similar to the RDP issue. 'Install as a service' is never going to work (except on Windows XP): some substantial work has been done on 'fast user switching' in the latest development version v7.3.19, which is available from the download all page. Although it's flagged with all the usual warnings about development versions, I think it's pretty close to ready and safe to use - it certainly suspends GPU tasks properly when the user context switches, and resumes them when it switches back: it would be worth testing with RDP too. |
ML1 Send message Joined: 25 Nov 01 Posts: 20147 Credit: 7,508,002 RAC: 20 |
... 'Install as a service' is never going to work (except on Windows XP): some substantial work has been done on 'fast user switching' in the latest development version v7.3.19, which is available from the download all page. Although it's flagged with all the usual warnings about development versions, I think it's pretty close to ready and safe to use - it certainly suspends GPU tasks properly when the user context switches, and resumes them when it switches back: it would be worth testing with RDP too. Mmmmm... In the Linux world, all that is needed is to add boinc to the "video" group and away you go: local, remote, service, anyway you like. Would Linux be easier/faster? Various "RDP/VNC" or X-forwarding are supported for graphical remote access also. Happy fast crunchin', Martin See new freedom: Mageia Linux Take a look for yourself: Linux Format The Future is what We all make IT (GPLv3) |
James C. Send message Joined: 19 Jul 06 Posts: 640 Credit: 18,352,758 RAC: 11 |
... 'Install as a service' is never going to work (except on Windows XP): some substantial work has been done on 'fast user switching' in the latest development version v7.3.19, which is available from the download all page. Although it's flagged with all the usual warnings about development versions, I think it's pretty close to ready and safe to use - it certainly suspends GPU tasks properly when the user context switches, and resumes them when it switches back: it would be worth testing with RDP too. I mean I could deploy a Linux station as a VM to solve this, but would need extensive direction. It may be best just to stay on Windows Server 2012 and disable CUDA/GPU. -"Young" James "To my mathematical brain, the numbers alone make thinking about aliens perfectly rational. The real challenge is to work out what aliens might actually be like." -Steven Hawking |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
If you use any VNC, or a program like teamviewer/logmein instead of RDP, you could access remotely your hosts and keep the GPU running under any Windows running without any aditional changes. I use TightVNC in all my hosts even in the multiple GPU´s ones and constantly remote access them with no problems. |
rob smith Send message Joined: 7 Mar 03 Posts: 22161 Credit: 416,307,556 RAC: 380 |
Locked at OP's request. He is no longer looking for a GPU/RDP fix. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.