Yes, this will work.
LockSingleUser creates a lockfile in the users home directory, so it
workes from multiple servers and with profiles and home directories
on a SAN.
I assume that you are running W2K TS, correct? Because on 2003 TS,
you can use a Group Policy setting to restrict users to a single
session only (without using Sessions Directory):
Computer Configuration - Administrative templates - Windows
Components - Terminal Services
"Restrict Terminal Services Users to a single remote session"
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Piotr Truszczynski" <truszcz@go2.pl> wrote on 19 sep 2005 in
microsoft.public.windowsnt.terminalserver.connectivity:
> Hi,
>
[quoted text clipped - 7 lines]
> greetings
> Piotr Truszczynski
Piotr Truszczynski - 20 Sep 2005 08:44 GMT
> Yes, this will work.
> LockSingleUser creates a lockfile in the users home directory, so it
> workes from multiple servers and with profiles and home directories
> on a SAN.
>
> I assume that you are running W2K TS, correct? Because on 2003 TS,
Well I'm using 2003 TS, but since it's not a cluster, just bunch of
computers, I have to use some lockfile dependent method, to be sure that
same user will not logon through another server.
BTW, I've heard something about new release of 2003 Server coming this year,
with few new features for TS.
Do you know, maybe, when we can excpect this release ? :))
greetings
Piotr Truszczynski