Re: Resetting the Client Name on a disconnected Console seession

Thanks -
1) The task runs at night so if a user is logged in its OK to force them out
2) The application does not require that a user is logged on the pysical
console.
However I tried teh suggestion of scheduling a task with logoff console to
run before the actual job and got the follwing result:
If a user was logged on to the physical console then it works fine.
But then if a user is logged on remotely as the console and is active the
user gets the schedule job DOS window showing the logoff console command
follwed with a prompt "If you reset this session all users using this
protocal will be logged off Continue (n=no)" . Is there a way to supress
this and just force the logoff.

I have checked with the admin users and even if they logout correctly and we
check the session using the Terminal server manager we see the users session
shows as disconnected and the client name remains the client name of the
workstation from where the user logged in

Current environement is the Server is Wondows 2003 sp1 and the workstations
are XP. Not sure how to tell what vesion of the remote client they run

Thanks
--
Andrew


"Soo Kuan Teo [MSFT]" wrote:

Since you mentioned rebooting the server, I'm assuming its ok to logoff
console without any warning to the console user, (so the console user can
take appropriate action to save his/her work).
If possible, before running your scheduled application, you can schedule a
task to logoff console using cmd line tool:
logoff.exe console

Can your application runs without any user logon to physical console?
Thanks
Soo Kuan


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns995798A3BF192veranoesthemutforsse@xxxxxxxxxxxxxxxx
The real problem is that the admin is not logging of from the
console session, he or she is merely disconnecting from it.
Either teach your administrators to logoff properly, or configure
an idle time-out on disconnected sessions and reset them
automatically.
This could be a wise step anyway, to ensure that disconnected
sessions are not locking you out from remotely accessing your
server (if 3 admins have one disconnected session each).

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

=?Utf-8?B?QW5kcmV3IENhbGR3ZWxs?=
<AndrewCaldwell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 22 jun 2007 in
microsoft.public.windows.terminal_services:

I need to find a solution to a problem we are having after a
admin user connects from his workstation to the console of a
remote machine. Once the user logouts out, the console session
is disconnected but the Cleint Name of the session remains the
name of the workstation of the user that last connected to the
server. The problem is I also have a Schedule Task that runs an
end of day application (supplied by an external vendor) that
does a call using WTSQuerySessionInformation to determine the
workstation name. This then returns the name of the workstation
of the last user that logged on remotly using a console
connection. Unfortunately the application then checks of this
workstation is allowed to run the end of day process and as it
is not the server name it exits without running anything.

If we reboot teh server and ensure that no users access the
console remotely then the application works correctly as ot
picks up the servers name and not any other workstation

One solution is to stop the admin users logging in using a
console sesson (which will never happen). Alternativly we
define all workstation from which the admin users may logon
using the remote console option as machines that can run the end
of day in the application. But given that we have a number of
administrators logging in from varous workstations this list is
endless

Another other is to get the vendor to change how the application
determines what workstation/Server it is running on. But this
will take time and money


What I would prefer is to find another way that we could either
clear the Client Name from the console session or to change how
the scheduler runs.

Any suggestions ?


.

Relevant Pages

  • Re: Non Administrative Console Access
    ... "To log on to this remote session, ... This only appears when trying to access the server via TS Console session, ... Microsoft MVP - Terminal Server ... made a member of the Local Administrators group. ...
    (microsoft.public.windows.terminal_services)
  • Re: Applying computer setting
    ... If you're the primary administrator of a server, ... that is the console session. ... If there is more than one person that is allowed to log onto the server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Username of who is logged into workstation via remote desktop
    ... sessions - I assume the ones that have happened since the workstation was ... currently logged into either the console or RDP? ... > session and the same line will also contain the user account name. ... > torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway ...
    (microsoft.public.scripting.vbscript)
  • Re: RDC Console connection locks up server
    ... Does this happen only when there is an active console session ... can you logon to the physical console of the server? ... find when used w/o the /console switch. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Duh question about TS versus RDC
    ... When the server is in Remote Administration mode, ... connections (+ 1 console session), which don't require any TS CALs ... *all* connections need a TS ...
    (microsoft.public.windows.terminal_services)