Re: Windows 2000 TS, restricting users to 1 session
Check this (note that I haven't tested this on a W2K TS):
CTX891671 - Graceful Logoff from a Published Application Keeps
Sessions in Active State
http://support.citrix.com/article/CTX891671
If you are running native Terminal Services without Citrix, you can
still use the method described in the "Resolution" section of the
Citrix article, albeit with another registry entry. Windows
Terminal Services keeps its list of system processes in the
following location in the registry:
HKLM\CurrentControlSet\Control\Terminal Server\SysProcs
If you have identified the process which keeps the session from
logging off, you can create a new REG_DWORD value under the
SysProcs key, with the name of the process as the value name.
_________________________________________________________
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?Q2hyaXMgU3dpbm5leQ==?=
<ChrisSwinney@discussions.microsoft.com> wrote on 13 nov 2007 in
microsoft.public.windows.terminal_services:
> Vera,
>
> I have noted an issue with the application you pointed me to
> (LockSingleUser2), or rather another issue with TS.
>
> We set users environment so that a specific application starts
> when they login to a TS session. This is the only thing required
> by users using TS. This works fine and when the user closes the
> app, the session close as per normal.
>
> However, now that I run LockSingleUser2 by starting it from a
> login batch file, when the user closes the app, the session
> remains active as the LockSingleUser2 exe is still running.
>
> I suppose a user could close the TS client and so disconnect the
> session, then the session would eventually terminate after the
> timeout period is up (15 mins), but this is not ideal.
>
> How can we now close the LockSingleUser2 application and
> terminate the session when the user closes the environment
> started application?
>
> Chris
>
>
> "Vera Noest [MVP]" wrote:
>
>> No, the SingleUser app doesn't help you there. It simply
>> disallows a user to create a second TS session (by creating a
>> lock file in the user's home directory).
>> Reconnection to broken connections doesn't work very well (if
>> at all) in W2K.
>> _________________________________________________________
>> 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?Q2hyaXMgU3dpbm5leQ==?=
>> <ChrisSwinney@discussions.microsoft.com> wrote on 12 nov 2007
>> in microsoft.public.windows.terminal_services:
>>
>> > Many thanks Vera,
>> >
>> > Do you know if the app will force a session to reconnect to
>> > one where the network connection has been unexpectedly
>> > disconnected?
>> >
>> > I belive this situation leads to an "active orphaned seesion"
>> > and as I understandi it, setting the GPO that deals with
>> > keepalive enable the TS server to detect this situation and
>> > hence disconnection the session - but thisonly works with
>> > Windows 2003, not 2000 - unless there is another fix for that
>> > (if needed)?
>> >
>> >
>> > Chris
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> From Microsofts Terminal Services FAQ
>> >> http://www.microsoft.com/technet/community/en-
>> >> us/terminal/terminal_faq.mspx
>> >>
>> >> Q. How can I limit Terminal Services so that a user can
>> >> connect only one time?
>> >>
>> >> A. For Windows 2000, there is a third-party application
>> >> available that does this. For more information, see
>> >> thethin.net/r25b.zip.
>> >>
>> >> For Windows Server 2003, set the Restrict each user to one
>> >> session option to Yes in Terminal Services Configuration.
>> >> Alternatively, set the Restrict Terminal Services users to a
>> >> single remote session group policy to Enabled.
>> >>
>> >> _________________________________________________________
>> >> 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?Q2hyaXMgU3dpbm5leQ==?=
>> >> <ChrisSwinney@discussions.microsoft.com> wrote on 12 nov
>> >> 2007 in microsoft.public.windows.terminal_services:
>> >>
>> >> > Hi all,
>> >> >
>> >> > I see that there are GPOs that can be set to restrict user
>> >> > creating more than 1 session for TS in Win 2003, but we
>> >> > have issues with a Win 2000 TS server. I have also noted
>> >> > that there are GPOs that use keepalive so that dropped
>> >> > session can be disconnected properly.
>> >> >
>> >> > We have remote users that connect in via VPN then use TS
>> >> > to run certain apps. Sometimes the VPN disconnects and the
>> >> > TS session is broken. I have set the option in the
>> >> > properties of the users so that they SHOULD be able to
>> >> > reconnect from any client, however, what appear to be
>> >> > happening is that the user attempts to log back on and a
>> >> > new session is started.
>> >> >
>> >> > I would like to set Win 2000 TS so that only 1 session can
>> >> > be activated per user and if a remote connection fails
>> >> > then the user will be able to reconnect to the correct
>> >> > session.
>> >> >
>> >> > Is this possible, possibly through registry hacks?
>> >> >
>> >> > Chris