Re: LimitLogin not working on Terminal Server
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Jun 2007 14:12:43 -0700
No, that's not what the OP wants to achieve.
The goal is to limit the users in one group to a single session per
user. There should not be a restriction on the number of concurrent
connections to the rdp listener.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Soo Kuan Teo [MSFT]" <sookuant@xxxxxxxxxxxxxxxxxxxx> wrote on 22
jun 2007 in microsoft.public.windows.terminal_services:
If I understand correctly, one possible way may be to have 2.
rdp-tcp connections on your server. You need to have 2 network
cards on your server. Say you set permissions on rdp-tcp1 so
that only Group A can connect. Then you set permissions to
rdp-tcp2 so that Group B can connect with Samin's suggestion to
set the connections limit. Thanks
Soo Kuan
- References:
- LimitLogin not working on Terminal Server
- From: TWolfICP
- Re: LimitLogin not working on Terminal Server
- From: Soo Kuan Teo [MSFT]
- LimitLogin not working on Terminal Server
- Prev by Date: Re: TS Licensing Issue
- Next by Date: Re: How add users to Term Services in order std users my connect r
- Previous by thread: Re: LimitLogin not working on Terminal Server
- Next by thread: best machine for Wyse thin clients
- Index(es):
Relevant Pages
|
