M
muddyh2o
I have a windows application which starts after Windows XP Professional
does a network autologon. I need to find a way to remotely logoff /
autologon after a termserv session. The problem today is that after a
terminal server session, the windows workstation locks itself,
effectively disabling the autologon feature. The only way around this
is to restart the machine, either via termserv or shutdown.exe.
The application is effectively a "kiosk" activity. The local users
have no keyboard or mouse interaction with the workstation. I need to
occasionally (a few times a week) support this application remotely
(Terminal Services).
When that termserv session ends, the screen locks and users can no
longer see the application. My only remote option is to reboot, which
is overkill and takes a while (minutes) to complete.
I know that the application should run as a service, and it will soon,
but i don't expect that before the end of 2005.
Can anyone suggest a remote tool, like shutdown.exe, that forces a
workstation to logoff as if a local user had logged off, and which
allows AutoLogon to execute? Ideally, i could run this anytime i want
(with the correct permissions) to initiate a logoff. This would be
especially useful after a termserv session, but i could also do this
when the application itself became unstable. (Restarting always fixes
current problems)
I don't expect this to be a long-term solution, but something for the
next 6 months as application stability increases.
i hope i've explained the clearly.
Thanks in advance for your help.
does a network autologon. I need to find a way to remotely logoff /
autologon after a termserv session. The problem today is that after a
terminal server session, the windows workstation locks itself,
effectively disabling the autologon feature. The only way around this
is to restart the machine, either via termserv or shutdown.exe.
The application is effectively a "kiosk" activity. The local users
have no keyboard or mouse interaction with the workstation. I need to
occasionally (a few times a week) support this application remotely
(Terminal Services).
When that termserv session ends, the screen locks and users can no
longer see the application. My only remote option is to reboot, which
is overkill and takes a while (minutes) to complete.
I know that the application should run as a service, and it will soon,
but i don't expect that before the end of 2005.
Can anyone suggest a remote tool, like shutdown.exe, that forces a
workstation to logoff as if a local user had logged off, and which
allows AutoLogon to execute? Ideally, i could run this anytime i want
(with the correct permissions) to initiate a logoff. This would be
especially useful after a termserv session, but i could also do this
when the application itself became unstable. (Restarting always fixes
current problems)
I don't expect this to be a long-term solution, but something for the
next 6 months as application stability increases.
i hope i've explained the clearly.
Thanks in advance for your help.