Logon Error Message

[Guest]

Hi All,

We have just setup a new Windows 20003 Terminal Server in a domain
environment for testing.

When the user tries to logon, an error message appears like:

The user <domainname>\<adminaccount> is currently logged on to this computer.
Only the current user or an administrator can log onto this computer.

Subsequently, the user is unable to logon to terminal services.

The user account is in the Remote Desktop User group and using a combination
of Windows 2000/XP machines.

Regards,
Sung Duc

 

[Vera Noest [MVP]]

By default, each user is restricted to one session. Configure in TS
Configuration - Server properties or a GPO.

 

[Guest]

Thanks Vera.

The problem is, the user is not previously logged onto TS or have any
disconnected sessions.

Regards,
Sung Duc

 

[Vera Noest [MVP]]

That's weird! Not on the console either?
And how about the <domainname>\<adminaccount> that is reported to
be logged on? I assume that this is an admin account logged on to
the console?
Is the user who get the error trying to connect to the console
session (by using "mstsc /console", or the Remote Desktop Utility
that comes with the Windows 2003 AdminPak)?
Only one user at a time can connect to the console session
(=session 0).

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Guest]

the <domainname>\<adminaccount> is able to logon to the server via mstsc
/console utility when logged on at the console. Yes, it is a admin account.

The user is trying to acccess terminal server via the mstsc/console utility.

I have not installed our TS CALS or activated them as yet. Could this be a
potential issue? I was hoping to utilise the 90 day timeframe before having
to install and activate our licenses in order to have things fully tested
prior to implementing the server into production.

Regards,
Sung Duc

 

[Vera Noest [MVP]]

Well, that's your problem. Let the user connect to the Terminal
server without the /console flag.

As I wrote, only one user at a time can connect to the console
session. This should normally not be allowed to normal users.
In fact, your user should have received a "You have no permission
to logon to this session" error message.
I would remove the "logon locally" rights for the user. This is not
needed in 2003 TS.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Guest]

Thanks Vera.

Your help has been very much appreciated.

Regards,
Sung Duc

 

[Chris White via WinServerKB.com]

Im haveing a problem with the Users loging in when another User logs in
using the same User ID.
The 1st user is getting booted when the 2nd user trys to log in and nether
get any warning. Should be the other way around *shrugs*.

I need to fix this problem when this happens the user losses alot of
unsaved data when they get booted.
Any ideas vera?

 

[Vera Noest [MVP]]

Give each user a unique account.
Sharing user accounts has always been a bad idea, but even more so in
a Terminal Services environment.

 

[Chris White via WinServerKB.com]

I’m just wondering if their is a way to give them a message. Saying user is
already logged in and stops them from login.

Some times the people that work here switch jobs so the account needs to be
used by another person and they will type their old one in *aka boots the
other user off. The job that is done here can not afford to loss that data.

Sorry, I was so unclear in last post.

 

[Vera Noest [MVP]]

I wouldn't know how to achieve that. You could try some fancy script
to send a warning message, but if you run it from a logon script, it
is probably already too late...

I would try to modify working habits so that every user has a unique
account. Shared accounts cause problems with sessions, redirected
printers, corrupt profiles, etc.

 

[Chris White via WinServerKB.com]

Ok well thank you for trying.