Disable Close rdp session forcing users to logout

[Garreth]

We run a custom application through Win 2000 Terminal
Servers. XP clients use rdp to open a session on the 2000
Terminal Servers.
How do we disable the close "x" function on the rdp
connection on the client machines, thus forcing the users
not to close/disconnect,leaving the application running
on the terminal server session. We would like to force
the users to logout of the custom app, which will
automatically log the users off the rdp terminal session
and custom app ?

 

[chris]

-----Original Message-----
We run a custom application through Win 2000 Terminal
Servers. XP clients use rdp to open a session on the 2000
Terminal Servers.
How do we disable the close "x" function on the rdp
connection on the client machines, thus forcing the users
not to close/disconnect,leaving the application running
on the terminal server session. We would like to force
the users to logout of the custom app, which will
automatically log the users off the rdp terminal session
and custom app ?

sooo... you want the custom app to log off the terminal
session when they log off of the said app?

in other words... i log off "Big Time AutoCad" which, in
turn, loggs me off the terminal service client? that kind
of thing?

ooor... logg off the terminal service (RD), which
keeps "Big Time AutoCad" running on the server?

 

[Garreth]

-----Original Message-----


sooo... you want the custom app to log off the terminal
session when they log off of the said app?

in other words... i log off "Big Time AutoCad" which, in
turn, loggs me off the terminal service client? that kind
of thing?

ooor... logg off the terminal service (RD), which
keeps "Big Time AutoCad" running on the server?

Basically, what we want is to disable the X on the
session window, thus, if a user logins into a session,
they are unable to close/disconnect the session. Our app
within the session has it's own close function, and will
log the session out. Users still use the windows
close/disconnect on the actual session, rather than use
our log off function within the session. Hope this makes
sense.

 

[Jeffrey Randow (MVP)]

This won't stop people from being able to close or disconnect the
settings.. You still can bring up Task Manager on the client machine
with CTRL-ALT-DEL (unless you disable this too) to kill the RD
connection client.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Garreth]

Thank You Jeffrey for your help. I have found a fix.
Basically, what I have done, is made a copy of mstsc.exe.
I have then edited the dialog box in this exe to change
the dialog box when a user clicks close, the
message "This will disconnect your session" has been
modified. The OK Button hidden and the Cancel button
changed to display OK. Thus, when a user attempts to
close the session, all they get is a modified Cancel
button, and a message stating this is the incorrect
method of logging off TS.

Thanks again