HowTo Logon to Console with non-Administrator to W2003 Terminal Server

  • Thread starter Thread starter Celina
  • Start date Start date
C

Celina

Hello,
We use Terminal Services to administer our Windows 2003
Servers remotely. Normally we do that using an
administrative account, but with tree servers we want to
use a non-administrative account.

I changed the permissions for connections in the rdp-tcp-
Properties to full for that specific account (as mentioned
in 253831). (There are no GPOs or anything like that to
restrict local logons.) Then I tried to connect so console
either with Remote Desktops with XP or with the
switch /console with Remote Desktop Client from W2K.

I get the error message "you do not have access to logon
to this session", when the account is not actually logged
on locally at the console on the machine. I can connect
and use the console when the account is already logged on
locally at the console on the machines.

If I grant admin rights to the account, I can connect to
the console without error message in both circumstances.

I would like to have the account able to use the console,
without the need to be logged on locally at the console
first (this would be useful in case of reboots of the
server).

Any suggestions would be helpful. Thanks in advance.

Celina
 
Hello,
Thanks for your reply.
I assigned the account to "Remote Desktop Users" Group and
to "Power Users". The behaviour is all the same.
I even tried to create a new group, assign the account and
give this group the same permissions in local user
policies and rdp-tcp-permissions like the admin group ->
without success (but perhaps I missed a specific
permission ...?).

Celina
 
Hello, Eric
Yes, I've read this article. The account I've mentioned is
able to logon to the server when I sit at the console
directly. It is also possible to logon through "Remote
Desktop Client" into a terminal service session without
console access. (I mean, I can't see console messages, e.
g. a "net send"-window to the server, though I can use NT-
Explorer or Computer Management.)
The error message below appears in case of trying to make
the connection to console when no user is actually logged
on at the server.

Thanks.

Celina
 
Celina said:
Hello, Eric
Yes, I've read this article. The account I've mentioned is
able to logon to the server when I sit at the console
directly. It is also possible to logon through "Remote
Desktop Client" into a terminal service session without
console access. (I mean, I can't see console messages, e.
g. a "net send"-window to the server, though I can use NT-
Explorer or Computer Management.)
The error message below appears in case of trying to make
the connection to console when no user is actually logged
on at the server.

Thanks.

Celina
Click to expand...
 
Hello Celina,

I'm experiencing exactly the same problem here. The strange thing is that it worked fine until last tuesday (15-june-2004). I used non-administrative accounts to connect to the console of my W2003 servers without any problems. All of a sudden it stopped working. Now i can only set up a "normal" terminal server session with my non-administrative accounts. If you find the solution to this strange behaviour please let me know, i'll most certainly post a reply here if i find the answer first.

Kind Regards,
Arjan
 
Back
Top