User Logon Notification

[Guest Denis]

Hi,

 

I have a just configured Terminal Services on Windows Server 2003.

In our scenario Single Username and Password are being shared by multiple

users for accessing a particular application on the server.

 

But, when a user logs on with the same username, that is already logged on,

the previous user gets logged off.

 

What is the work around to this problem? My application is such that I

cannot give every users their independent User IDs.

 

Thanks in Advance,

 

Regards,

Denis

[Guest Vera Noest [MVP]]

Re: User Logon Notification

 

You have to allow users to have multiple connections.

This can be configured in Terminal Servives Configuration - Server

settings, or in a GPO:

 

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 ___

 

=?Utf-8?B?RGVuaXM=?= <Denis@discussions.microsoft.com> wrote on 03

nov 2007 in microsoft.public.windows.terminal_services:

> Hi,

>

> I have a just configured Terminal Services on Windows Server

> 2003. In our scenario Single Username and Password are being

> shared by multiple users for accessing a particular application

> on the server.

>

> But, when a user logs on with the same username, that is already

> logged on, the previous user gets logged off.

>

> What is the work around to this problem? My application is such

> that I cannot give every users their independent User IDs.

>

> Thanks in Advance,

>

> Regards,

> Denis

[Guest Denis]

Re: User Logon Notification

 

Thanks Vera for your valuable inputs.

 

But, if we do not want to allow multiple sessions per user, than is there

any way system can notify the user that someone is already logged in with the

same User ID.

 

Again, Thanks in Advance,

 

Regards,

Denis

 

 

 

 

 

"Vera Noest [MVP]" wrote:

> You have to allow users to have multiple connections.

> This can be configured in Terminal Servives Configuration - Server

> settings, or in a GPO:

>

> 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 ___

>

> =?Utf-8?B?RGVuaXM=?= <Denis@discussions.microsoft.com> wrote on 03

> nov 2007 in microsoft.public.windows.terminal_services:

>

> > Hi,

> >

> > I have a just configured Terminal Services on Windows Server

> > 2003. In our scenario Single Username and Password are being

> > shared by multiple users for accessing a particular application

> > on the server.

> >

> > But, when a user logs on with the same username, that is already

> > logged on, the previous user gets logged off.

> >

> > What is the work around to this problem? My application is such

> > that I cannot give every users their independent User IDs.

> >

> > Thanks in Advance,

> >

> > Regards,

> > Denis

>

[Guest Vera Noest [MVP]]

Re: User Logon Notification

 

No, not that I know of.

This is one of the many reasons that all users should have a unique

user account.

Profile corruption is another one, as well as unpredictable

behaviour regarding printers and user settings.

 

Just out of curiosity: how can an application make it impossible

for each user to log on to Windows with a unique user account?

 

_________________________________________________________

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?RGVuaXM=?= <Denis@discussions.microsoft.com> wrote on 05

nov 2007 in microsoft.public.windows.terminal_services:

> Thanks Vera for your valuable inputs.

>

> But, if we do not want to allow multiple sessions per user, than

> is there any way system can notify the user that someone is

> already logged in with the same User ID.

>

> Again, Thanks in Advance,

>

> Regards,

> Denis

>

> "Vera Noest [MVP]" wrote:

>

>> You have to allow users to have multiple connections.

>> This can be configured in Terminal Servives Configuration -

>> Server settings, or in a GPO:

>>

>> 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 ___

>>

>> =?Utf-8?B?RGVuaXM=?= <Denis@discussions.microsoft.com> wrote on

>> 03 nov 2007 in microsoft.public.windows.terminal_services:

>>

>> > Hi,

>> >

>> > I have a just configured Terminal Services on Windows Server

>> > 2003. In our scenario Single Username and Password are being

>> > shared by multiple users for accessing a particular

>> > application on the server.

>> >

>> > But, when a user logs on with the same username, that is

>> > already logged on, the previous user gets logged off.

>> >

>> > What is the work around to this problem? My application is

>> > such that I cannot give every users their independent User

>> > IDs.

>> >

>> > Thanks in Advance,

>> >

>> > Regards,

>> > Denis