Re: Disconnecting & Forcing Logoff

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



The "explain" text says:

"Note: This setting does not apply to console sessions such as
Remote Desktop sessions with computers running Windows XP
Professional."

which means that the time-out settings don't work when you connect
*to* an XP host, or to the console session of a 2003 server.
For normal sessions to your TS, the time-out will work.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

compsosinc@xxxxxxxxx wrote on 04 mar 2008 in
microsoft.public.windows.terminal_services:

On Mar 4, 3:06 pm, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
comments inline

compsos...@xxxxxxxxx wrote on 04 mar 2008 in
microsoft.public.windows.terminal_services:

1. Is there a way to disable a user's ability to disconnect
(using the X on the RDP connection) from a session and to
force them to logoff without following this procedure below:

http://terminal.servebeer.com/php/x_box_disable.php

For instance, can the "X" be disabled or if they click it,
can their session be "instantly" reconnected.

The AppScape Lockdown Utility disables the
X-boxhttp://www.dabcc.com/ThinS
ol/Downloads/default.htm

The only other approach is to configure your server to
immediately reset disconnected sessions, but that can cause
data loss if users disconnect while they have unsaved data in
the session.

2. In our particular situation, our Terminal Server users
(note, we have 1 generic user account/machine that need
identical settings) & they do not need to use their local XP
workstation for anything else. Currently, if they have to
reboot their workstations, they get the CTRL +ALT+DEL to
login to the domain. Once they login, a saved an .RDP file in
the User's Startup folder connects them to the Terminal
Server. Not sure of another way....

A hardware or software thin client would be the other way to
go. Check Patrick's
website:http://www.sessioncomputing.com/thin-clients.htm

3. Once they connect to the TS, we would like a particular
program to open. Is this best configured in the Group Policy
or in the TS Profile of the User account? We have a Group
Policy created to lockdown the TS (in its own OU).

A GPO is *always* best! You only have to make the configuration
in one place, and you are already setup for when you add a
second TS.

4. We only want (1) program shortcut icon on the desktop in
case they close the program and have to reopen it. Is it
possible to prevent deletion of this shortcut, OR if it is
deleted, have only it on the Start Menu (not using Classic)
where it cannot be deleted? Then, if they reconnect the
desktop icons come back. We have read about Folder
Redirection, mandatory profiles, roaming profiles, default
profiles, etc but seem to need guidance on the best method to
use.

You can just put the shortcut on the All Users Desktop if it
isn't already there and make it read-only.
But note that if you define a Starting application, users will
never see the desktop, the session will logoff as soon as they
exit the application.

Thanks so much

You're welcome!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:  http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Concerning resetting the connection when a user disconnects
instead of logging off. We are going to keep the X on the RDP
connection. However we are looking through the GP for resetting
the disconnected session under User Config> Admin Temp>Wind
Comp> Term Serv> Sesssions: "set time limit for disconnected
sessions". Is this where --it explains that this cannot be used
with WindowsXP RDP??
.



Relevant Pages

  • Re: GPO Settings
    ... |> Enabled - Terminate session when time limits are reached ... | disconnected from the Terminal Server. ... |> "Set path for TS Roaming Profiles" ...
    (microsoft.public.windows.terminal_services)
  • Re: GPO Settings
    ... EXISTING SETTINGS: ... Enabled - Terminate session when time limits are reached ... disconnected from the Terminal Server. ... I have roaming user profiles set for my local domain environment ...
    (microsoft.public.windows.terminal_services)
  • Re: RWW Timing
    ... I understand that you want to monitor when and how ... > to an internal Windows XP or Terminal Server computer. ... SBS creates a connection to the internal client on port 3389 which is ... But it can not tell which one session from the RWW, ...
    (microsoft.public.windows.server.sbs)
  • Re: AAAAAAHHHHHH This problem is killing me!!!
    ... > The program .exe is located on a database server and they connect via UNC. ... > How do I end the session on the database server whenever the connection is lost on the Terminal server? ... terminating the session rather than letting it remain open on the server. ... So if the settings are already as Arno suggests you set them, ...
    (microsoft.public.win2000.termserv.apps)
  • Re: remote web workplace server admin login problem
    ... deploy our server "Proper" when we move offices would anybody object if I ... >> I can also use it to connect to the servers console session. ... (the TS login session opens and I enter ... >> "saving your settings" and it then kicks me back to the server ...
    (microsoft.public.windows.server.sbs)