Re: Can I stop Remote Desktop from locking host?
- From: "Nepatsfan" <nepatsfan@xxxxxxxxxxx>
- Date: Fri, 21 Sep 2007 18:49:15 -0400
I'm a sir, but can't claim to be a "GENIOUS"! I first learned
of that command on this very newsgroup. Glad to hear it worked
for you.
Nepatsfan
In news:CA09F4C6-E5FF-4798-B440-77CBF27DE4FA@xxxxxxxxxxxxx,
SonicForce <SonicForce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Sir (or Madam?!)... you are a GENIOUS!
Thanks, that works perfectly.
All the best,
Graham
--------
"Nepatsfan" wrote:
In news:FE640A3E-2209-45ED-8A48-8961CD5FF2F5@xxxxxxxxxxxxx,
SonicForce <SonicForce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Is there any way that I can stop Remote Desktop from
locking
the host
machine, or perhaps get it to automatically unlock the host
after the remote
access?
I'm trying to run automated regression tests (using HP's
"QuickTest
Professional") on the host machine, but people around the
world need to be
able to remote into the machine and then just close the
Remote Desktop window
when they're done. If they do this, the host has the
locked
message up on
the screen and GUI tests then fail because the windows
aren't
able to show on
the screen.
One solution to this is using VNC, but there are security
flaws that make
this an unwise choice (according to our Info Security
dept).
Another solution is to use "PC Anywhere", but this
(according
to Symantec)
doesn't work with virtual machines, which is something
we're
moving towards.
Another solution is to use WebEx's "Access Anywhere", but
for
the way that
we want to use our connections, this could be an expensive
solution.
Another solution is to use a ShareWare product I've found
called "Remote
Desktop Control", but I don't know how keen our company
would
be to use
'unknown shareware'.
Another solution is to use NetMeeting, but it's clunky and
requires a
username, password and domain name to be typed each time
you
connect.
One thought I had was to write something in VBScript that
unlocks the host,
since I know what the username and password is, of course,
but I can't work
out how to do that, even after a day of researching the
web.
So..... any ideas anyone please?!
Thanks,
Graham
I don't know how you can work this into your situation, but
I'll pass it along. The following command can be run on the
remote computer and it will leave the system unlocked with
the
account that was used during the remote session logged on.
tscon.exe 0 /dest:console
I connect remotely to my XP Pro system using the credentials
of
the main account on that machine. I created a batch file
that
runs that command and placed it in the C:\Windows folder of
the
remote computer. The batch file is named Disconnect.bat. I
then
put a shortcut to the batch file in the All Users\Desktop
folder. I also changed the shortcut's icon to match the one
for
"Turn Off Computer" on the Start menu.
Instead of closing the remote desktop connection on my local
computer, I double click the shortcut on the remote computer
to
end the session.
Good luck
Nepatsfan
.
- References:
- Re: Can I stop Remote Desktop from locking host?
- From: Nepatsfan
- Re: Can I stop Remote Desktop from locking host?
- From: SonicForce
- Re: Can I stop Remote Desktop from locking host?
- Prev by Date: Re: Can I stop Remote Desktop from locking host?
- Next by Date: connecting remotely to another computer both behind natting firewalls
- Previous by thread: Re: Can I stop Remote Desktop from locking host?
- Next by thread: connecting remotely to another computer both behind natting firewalls
- Index(es):
Relevant Pages
|