Terminal Server 2003 and Per User Licensing

  • Thread starter Eugene Pressley
  • Start date
E

Eugene Pressley

I am getting a error message on our Terminal Server
Clients. "You do not have access to logon to this
session." This started when I switched to Per User
Licensing on the Windows 2003 Server Terminal Server
Configuration. I have puchased and installed "Per User"
licenses on the Licensing server.
 
V

Vera Noest [MVP]

This error has nothing to do with the licensing mode (but maybe you
didn't get as far as the error message when you were in the wrong
licensing mode?).

Have you checked that your users are members of the build-in Remote
Desktop Users group?
 
B

Bruce Chen

Hi Eugene,

Thanks for posting here!

Yes, Vera is right.

When you try to log on using the Terminal Services client, you may receive
the following error message: Logon Message: You do not have access to logon
to this session.

It is due to the terminal Services has a default connection security
setting allows only administrators to log on.

If the security attributes on a specified connection have not been set, the
connection inherits these default security settings.

For additional information, please see the following article in the
Microsoft Knowledge Base:

Default Connection Security Changes Are Not Applied

http://support.microsoft.com/default.aspx?scid=kb;EN-US;225038

If the default connection security settings do not meet your needs, you can
set custom security attributes.

RESOLUTION:
==========

To set custom Terminal Services connection permissions:

(1) Click Start, point to Programs, point to Administrative Tools, and then
click Terminal Services Configuration.

(2)Open the Connections folder.

(3) Right-click the connection (RDP-TCP), and then click Properties.

(4) On the Permissions tab, add the group(s) that needs access to this
connection.

(5) Click OK.

For more detailed information, please refer to the article below.

224395 Terminal Services Client Error Message: You Do Not Have Access to
Logon

http://support.microsoft.com/?id=224395

Hope it helps!

Also thanks for Vera for valuable suggestions!




Sincerely,

Bruce Chen
MCSE, MCDBA, CNE, CLS

Microsoft Partner Online Support

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via
your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.


--------------------
| Content-Class: urn:content-classes:message
| From: "Eugene Pressley" <[email protected]>
| Sender: "Eugene Pressley" <[email protected]>
| Subject: Terminal Server 2003 and Per User Licensing
| Date: Mon, 8 Dec 2003 10:34:38 -0800
| Lines: 6
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcO9ue/A9lBmNzDrT02rMISps1Qu6g==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.win2000.termserv.clients
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.termserv.clients:13776
| NNTP-Posting-Host: tk2msftngxa09.phx.gbl 10.40.1.161
| X-Tomcat-NG: microsoft.public.win2000.termserv.clients
|
| I am getting a error message on our Terminal Server
| Clients. "You do not have access to logon to this
| session." This started when I switched to Per User
| Licensing on the Windows 2003 Server Terminal Server
| Configuration. I have puchased and installed "Per User"
| licenses on the Licensing server.
|
 
E

Eugene Pressley

As it turns out the solution was a simple one. The
documentation refering to switching from Per Device to Per
User mode states the you simple need to make the change
for it to become active. Apparently, and this is not
documented, a reboot is also needed. If you do not reboot
after changing from Per Device to Per User, you will
recieve the "You do not have access to logon to this
session" message. After I reboot all is well.
 
V

Vera Noest [MVP]

I'll be damned! That's quite a misleading error message, then.
Thanks for reporting back here, Eugene!
 
B

Bruce Chen

Hi Eugene!

Thank you for posting back and I am glad to hear that issue has been
resolved.

If you have any questions in the future, please don't hesitate to post in
the newsgroup.

Again, thanks to Vera for valuable suggestions and I hope you all have a
nice day!


Sincerely,

Bruce Chen
MCSE, MCDBA, CNE, CLS

Microsoft Partner Online Support

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via
your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and
confers no rights.


--------------------
| Content-Class: urn:content-classes:message
| From: "Eugene Pressley" <[email protected]>
| Sender: "Eugene Pressley" <[email protected]>
| References: <[email protected]>
<64#[email protected]>
| Subject: RE: Terminal Server 2003 and Per User Licensing
| Date: Tue, 9 Dec 2003 09:26:24 -0800
| Lines: 130
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| thread-index: AcO+eZG1NbcToNCcQ4alpsTrR/PqCw==
| Newsgroups: microsoft.public.win2000.termserv.clients
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.termserv.clients:13806
| NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
| X-Tomcat-NG: microsoft.public.win2000.termserv.clients
|
| As it turns out the solution was a simple one. The
| documentation refering to switching from Per Device to Per
| User mode states the you simple need to make the change
| for it to become active. Apparently, and this is not
| documented, a reboot is also needed. If you do not reboot
| after changing from Per Device to Per User, you will
| recieve the "You do not have access to logon to this
| session" message. After I reboot all is well.
|
|
| >-----Original Message-----
| >Hi Eugene,
| >
| >Thanks for posting here!
| >
| >Yes, Vera is right.
| >
| >When you try to log on using the Terminal Services
| client, you may receive
| >the following error message: Logon Message: You do not
| have access to logon
| >to this session.
| >
| >It is due to the terminal Services has a default
| connection security
| >setting allows only administrators to log on.
| >
| >If the security attributes on a specified connection have
| not been set, the
| >connection inherits these default security settings.
| >
| >For additional information, please see the following
| article in the
| >Microsoft Knowledge Base:
| >
| >Default Connection Security Changes Are Not Applied
| >
| >http://support.microsoft.com/default.aspx?scid=kb;EN-
| US;225038
| >
| >If the default connection security settings do not meet
| your needs, you can
| >set custom security attributes.
| >
| >RESOLUTION:
| >==========
| >
| >To set custom Terminal Services connection permissions:
| >
| >(1) Click Start, point to Programs, point to
| Administrative Tools, and then
| >click Terminal Services Configuration.
| >
| >(2)Open the Connections folder.
| >
| >(3) Right-click the connection (RDP-TCP), and then click
| Properties.
| >
| >(4) On the Permissions tab, add the group(s) that needs
| access to this
| >connection.
| >
| >(5) Click OK.
| >
| >For more detailed information, please refer to the
| article below.
| >
| >224395 Terminal Services Client Error Message: You Do Not
| Have Access to
| >Logon
| >
| >http://support.microsoft.com/?id=224395
| >
| >Hope it helps!
| >
| >Also thanks for Vera for valuable suggestions!
| >
| >
| >
| >
| >Sincerely,
| >
| >Bruce Chen
| >MCSE, MCDBA, CNE, CLS
| >
| >Microsoft Partner Online Support
| >
| >Get Secure! - www.microsoft.com/security
| >
| >====================================================
| >When responding to posts, please "Reply to Group" via
| >your newsreader so
| >that others may learn and benefit from your issue.
| >====================================================
| >This posting is provided "AS IS" with no warranties, and
| >confers no rights.
| >
| >
| >--------------------
| >| Content-Class: urn:content-classes:message
| >| From: "Eugene Pressley" <[email protected]>
| >| Sender: "Eugene Pressley" <[email protected]>
| >| Subject: Terminal Server 2003 and Per User Licensing
| >| Date: Mon, 8 Dec 2003 10:34:38 -0800
| >| Lines: 6
| >| Message-ID: <[email protected]>
| >| MIME-Version: 1.0
| >| Content-Type: text/plain;
| >| charset="iso-8859-1"
| >| Content-Transfer-Encoding: 7bit
| >| X-Newsreader: Microsoft CDO for Windows 2000
| >| Thread-Index: AcO9ue/A9lBmNzDrT02rMISps1Qu6g==
| >| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >| Newsgroups: microsoft.public.win2000.termserv.clients
| >| Path: cpmsftngxa07.phx.gbl
| >| Xref: cpmsftngxa07.phx.gbl
| microsoft.public.win2000.termserv.clients:13776
| >| NNTP-Posting-Host: tk2msftngxa09.phx.gbl 10.40.1.161
| >| X-Tomcat-NG: microsoft.public.win2000.termserv.clients
| >|
| >| I am getting a error message on our Terminal Server
| >| Clients. "You do not have access to logon to this
| >| session." This started when I switched to Per User
| >| Licensing on the Windows 2003 Server Terminal Server
| >| Configuration. I have puchased and installed "Per User"
| >| licenses on the Licensing server.
| >|
| >
| >.
| >
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top