RemoteDesktop: are admin privileges different?

[Beemer Biker]

Have run into a strange behavior and am trying to figure out what is
happening. If I reboot a home vista 64 system from my office over RDP, the
nVidia coprocessor (CUDA object) is no longer recognized and tasks that are
supposed to run on it will not start. I have to go home and cycle the
power. This does not happen if I am at home and I select restart.

I looked thru the event logs and did not see anything out of the ordinary.
If there was some privilege denied to remote desktop admins I would think it
would show up in the security or system log. The only error message I can
find is the one displayed interactively by the app when it starts up, ie: to
the effect it cannot find the CUDA object.


Yes, I do admit to downloading and installing the remote desktop dll into
this home premium system. However, this same problem (unable to find CUDA)
has been reported by other users at gpugrid and seti and they are using
business vista which has the legit remote desktop service.
NETCOP-DISCLAIMER: I do own 2 legit copies of business vista one of which
has not been installed yet.

TIA

--
======================================================================
Joseph "Beemer Biker" Stateson
http://TipsForTheComputingImpaired.com
http://ResearchRiders.org Ask about my 99'R1100RT
======================================================================

 

[Mark L. Ferguson]

I would guess the remote desktop is not getting a graceful shutdown. I would
use a kludge. Launch a timed shutdown script, and then log off the remote
connection, letting the script do the restart. Something like:

---wait to restart.vbs--
wscript.sleep 30000
' wait, in milliseconds
set shell=creatobject("wscript.shell")
shell.run "shutdown /r"
--end--
--
Use the "Ratings" feature. It helps the new users.
Need more Answers? Try the new Microsoft Answers pages.
http://answers.microsoft.com/en-us/windows/dd228912.aspx
Mark L. Ferguson MS-MVP
https://mvp.support.microsoft.com/profile/Mark.Ferguson

 

[Beemer Biker]

I would guess the remote desktop is not getting a graceful shutdown. I
would use a kludge. Launch a timed shutdown script, and then log off the
remote connection, letting the script do the restart. Something like:

---wait to restart.vbs--
wscript.sleep 30000
' wait, in milliseconds
set shell=creatobject("wscript.shell")
shell.run "shutdown /r"
--end--

I went home and restarted without turning the power off and it worked
fine. There was no need to cycle the power There is definately
something bizarre about issueing a restart from a
remote desktop connection. I poked around the All Users directory
file and found a log file with this message whenever I issued a restart
remotely

[12/17/08 09:45:31] TRACE [680]: Event: CTRL-LOGOFF Event
17-Dec-2008 09:45:32 [---] Exit requested by user

whenever I restarted while sitting in front of the computer I found this

[12/17/08 16:40:58] TRACE [344]: Event: CTRL-CLOSE or
CTRL-SHUTDOWN Event
17-Dec-2008 16:40:58 [---] Exit requested by user

I am guessing the restart only works properly when the event is
CTRL-CLOSE or CTRL-SHUTDOWN.

There may be a problem in the way the developer handles a CTRL-LOGOFF
(whatever that is) as opposed to a CTRL_CLOSE

When I installed the software (BOINC application) there was a warning not to
install it as a service under vista or the CUDA processor would not be
found. Typically, if you log off, services continue to run and that is the
case for boinc on XP and w2003s, and w2k, but under vista it cannot (as yet)
run as a service so a log-off must cause a problem. I am guessing of
course.

 

[Beemer Biker]

<SNIP>

clarification on my previous post.

(1) That CTRL-LOGOFF was the message printed up when I ran your suggested
script that does the "shutdown /r" after a 30 second delay. That same
message also appeared if i merely pressed ALT-F4 and did the shutdown that
way.

(2) Boinc can run as a service under vista, the problem is that the CUDA is
not recognized. I read that in the release notes.