Problem with Licensing and "mstsc /console"

[Guest JSmith]

We purchased 9 terminal server licenses (setup as per device). Whenever all

9 client computers are logged in, we are unable to connect to the server

console using "mstsc /console" from a 10th management computer. However, if

we log out 1 client computer then we are able to connect. We need to be able

to remote control the 9 sessions from the management computer.

 

Server: Windows 2003 Server x64

RDP Client: version 6

Management computer OS: Windows XP

Client computer OS: HP thin client (t5135) connecting via RDP

[Guest Lanwench [MVP - Exchange]]

Re: Problem with Licensing and "mstsc /console"

 

JSmith <JSmith@discussions.microsoft.com> wrote:

> We purchased 9 terminal server licenses (setup as per device).

> Whenever all 9 client computers are logged in, we are unable to

> connect to the server console using "mstsc /console" from a 10th

> management computer. However, if we log out 1 client computer then

> we are able to connect. We need to be able to remote control the 9

> sessions from the management computer.

>

> Server: Windows 2003 Server x64

> RDP Client: version 6

> Management computer OS: Windows XP

> Client computer OS: HP thin client (t5135) connecting via RDP

 

I think you'll need another TS CAL for this.

[Guest JSmith]

Re: Problem with Licensing and "mstsc /console"

 

Thanks for the quick reply, however, Microsoft states:

 

"A Terminal Server Client Access License (TS CAL) is required to use

Terminal Server or otherwise host a remote graphical user interface (GUI)

session, except for a console session."

 

See:

(http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overview.mspx)

 

As far as I understand, using "mstsc /console" is using a console session.

Am I missing something?

 

 

 

"Lanwench [MVP - Exchange]" wrote:

> JSmith <JSmith@discussions.microsoft.com> wrote:

> > We purchased 9 terminal server licenses (setup as per device).

> > Whenever all 9 client computers are logged in, we are unable to

> > connect to the server console using "mstsc /console" from a 10th

> > management computer. However, if we log out 1 client computer then

> > we are able to connect. We need to be able to remote control the 9

> > sessions from the management computer.

> >

> > Server: Windows 2003 Server x64

> > RDP Client: version 6

> > Management computer OS: Windows XP

> > Client computer OS: HP thin client (t5135) connecting via RDP

>

> I think you'll need another TS CAL for this.

>

>

>

[Guest JSmith]

Re: Problem with Licensing and "mstsc /console"

 

Here is some more text that Microsoft has about the console:

 

"If you need to connect to the server console session remotely (for example,

to access applications that direct only their user interface to the console),

either use the Remote Desktops snap-in or use Remote Desktop Connection from

the command line."

 

See:

(http://technet2.microsoft.com/WindowsServer/en/library/2cb5c8c9-cadc-44a9-bf39-856127f4c8271033.mspx?mfr=true)

 

"Lanwench [MVP - Exchange]" wrote:

> JSmith <JSmith@discussions.microsoft.com> wrote:

> > We purchased 9 terminal server licenses (setup as per device).

> > Whenever all 9 client computers are logged in, we are unable to

> > connect to the server console using "mstsc /console" from a 10th

> > management computer. However, if we log out 1 client computer then

> > we are able to connect. We need to be able to remote control the 9

> > sessions from the management computer.

> >

> > Server: Windows 2003 Server x64

> > RDP Client: version 6

> > Management computer OS: Windows XP

> > Client computer OS: HP thin client (t5135) connecting via RDP

>

> I think you'll need another TS CAL for this.

>

>

>

[Guest Vera Noest [MVP]]

Re: Problem with Licensing and "mstsc /console"

 

You are right, JSmith, a console session never uses or needs a TS

CAL. And moreover, TS CALs are not per concurrent connection, so if

you would run short of TS CALs, logging out one client would not

enable another client to log on.

 

So the problem that you have is *not* related to TS CALs at all.

I can think of two reasons for the behaviour that you see and you

should be able to verify which one applies to you by checking the

EventLog on the server:

 

a) the rdp-tcp connection settings are hardcoded to allow a maximum

of 9 concurrent connections. Check in Terminal Services

Configuration - rdp-tcp connection properties - network

 

b) your server is configured to use the "Per Server" licensing mode

for OS licensing, and you are running out of server CALs, not TS

CALs. Server CALs are per concurrent connection. Check in Control

Panel - Licensing applet. If that's the problem, make sure that you

have enough server CALs for all connecting devices and then disable

the Licensing Logging Service completely. Documented here:

 

824196 - Description of the License Logging Service in Windows

Server Operating Systems

http://support.microsoft.com/?kbid=824196

 

_________________________________________________________

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?SlNtaXRo?= <JSmith@discussions.microsoft.com> wrote on

28 mar 2008 in microsoft.public.windows.terminal_services:

> Thanks for the quick reply, however, Microsoft states:

>

> "A Terminal Server Client Access License (TS CAL) is required to

> use Terminal Server or otherwise host a remote graphical user

> interface (GUI) session, except for a console session."

>

> See:

> (http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ov

> erview.mspx)

>

> As far as I understand, using "mstsc /console" is using a

> console session. Am I missing something?

>

>

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> JSmith <JSmith@discussions.microsoft.com> wrote:

>> > We purchased 9 terminal server licenses (setup as per

>> > device). Whenever all 9 client computers are logged in, we

>> > are unable to connect to the server console using "mstsc

>> > /console" from a 10th management computer. However, if we

>> > log out 1 client computer then we are able to connect. We

>> > need to be able to remote control the 9 sessions from the

>> > management computer.

>> >

>> > Server: Windows 2003 Server x64

>> > RDP Client: version 6

>> > Management computer OS: Windows XP

>> > Client computer OS: HP thin client (t5135) connecting via

>> > RDP

>>

>> I think you'll need another TS CAL for this.

[Guest JSmith]

Re: Problem with Licensing and "mstsc /console"

 

Thank you for the information. I am going there after work and I will check

both of these items.

 

"Vera Noest [MVP]" wrote:

> You are right, JSmith, a console session never uses or needs a TS

> CAL. And moreover, TS CALs are not per concurrent connection, so if

> you would run short of TS CALs, logging out one client would not

> enable another client to log on.

>

> So the problem that you have is *not* related to TS CALs at all.

> I can think of two reasons for the behaviour that you see and you

> should be able to verify which one applies to you by checking the

> EventLog on the server:

>

> a) the rdp-tcp connection settings are hardcoded to allow a maximum

> of 9 concurrent connections. Check in Terminal Services

> Configuration - rdp-tcp connection properties - network

>

> b) your server is configured to use the "Per Server" licensing mode

> for OS licensing, and you are running out of server CALs, not TS

> CALs. Server CALs are per concurrent connection. Check in Control

> Panel - Licensing applet. If that's the problem, make sure that you

> have enough server CALs for all connecting devices and then disable

> the Licensing Logging Service completely. Documented here:

>

> 824196 - Description of the License Logging Service in Windows

> Server Operating Systems

> http://support.microsoft.com/?kbid=824196

>

> _________________________________________________________

> 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?SlNtaXRo?= <JSmith@discussions.microsoft.com> wrote on

> 28 mar 2008 in microsoft.public.windows.terminal_services:

>

> > Thanks for the quick reply, however, Microsoft states:

> >

> > "A Terminal Server Client Access License (TS CAL) is required to

> > use Terminal Server or otherwise host a remote graphical user

> > interface (GUI) session, except for a console session."

> >

> > See:

> > (http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ov

> > erview.mspx)

> >

> > As far as I understand, using "mstsc /console" is using a

> > console session. Am I missing something?

> >

> >

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> JSmith <JSmith@discussions.microsoft.com> wrote:

> >> > We purchased 9 terminal server licenses (setup as per

> >> > device). Whenever all 9 client computers are logged in, we

> >> > are unable to connect to the server console using "mstsc

> >> > /console" from a 10th management computer. However, if we

> >> > log out 1 client computer then we are able to connect. We

> >> > need to be able to remote control the 9 sessions from the

> >> > management computer.

> >> >

> >> > Server: Windows 2003 Server x64

> >> > RDP Client: version 6

> >> > Management computer OS: Windows XP

> >> > Client computer OS: HP thin client (t5135) connecting via

> >> > RDP

> >>

> >> I think you'll need another TS CAL for this.

>

[Guest JSmith]

Re: Problem with Licensing and "mstsc /console"

 

THANK YOU!!!!!!! It turned out to be the rdp-tcp connection settings. I

really appreciate your time and help with this issue.

 

"Vera Noest [MVP]" wrote:

> You are right, JSmith, a console session never uses or needs a TS

> CAL. And moreover, TS CALs are not per concurrent connection, so if

> you would run short of TS CALs, logging out one client would not

> enable another client to log on.

>

> So the problem that you have is *not* related to TS CALs at all.

> I can think of two reasons for the behaviour that you see and you

> should be able to verify which one applies to you by checking the

> EventLog on the server:

>

> a) the rdp-tcp connection settings are hardcoded to allow a maximum

> of 9 concurrent connections. Check in Terminal Services

> Configuration - rdp-tcp connection properties - network

>

> b) your server is configured to use the "Per Server" licensing mode

> for OS licensing, and you are running out of server CALs, not TS

> CALs. Server CALs are per concurrent connection. Check in Control

> Panel - Licensing applet. If that's the problem, make sure that you

> have enough server CALs for all connecting devices and then disable

> the Licensing Logging Service completely. Documented here:

>

> 824196 - Description of the License Logging Service in Windows

> Server Operating Systems

> http://support.microsoft.com/?kbid=824196

>

> _________________________________________________________

> 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?SlNtaXRo?= <JSmith@discussions.microsoft.com> wrote on

> 28 mar 2008 in microsoft.public.windows.terminal_services:

>

> > Thanks for the quick reply, however, Microsoft states:

> >

> > "A Terminal Server Client Access License (TS CAL) is required to

> > use Terminal Server or otherwise host a remote graphical user

> > interface (GUI) session, except for a console session."

> >

> > See:

> > (http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ov

> > erview.mspx)

> >

> > As far as I understand, using "mstsc /console" is using a

> > console session. Am I missing something?

> >

> >

> >

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> JSmith <JSmith@discussions.microsoft.com> wrote:

> >> > We purchased 9 terminal server licenses (setup as per

> >> > device). Whenever all 9 client computers are logged in, we

> >> > are unable to connect to the server console using "mstsc

> >> > /console" from a 10th management computer. However, if we

> >> > log out 1 client computer then we are able to connect. We

> >> > need to be able to remote control the 9 sessions from the

> >> > management computer.

> >> >

> >> > Server: Windows 2003 Server x64

> >> > RDP Client: version 6

> >> > Management computer OS: Windows XP

> >> > Client computer OS: HP thin client (t5135) connecting via

> >> > RDP

> >>

> >> I think you'll need another TS CAL for this.

>

[Guest Vera Noest [MVP]]

Re: Problem with Licensing and "mstsc /console"

 

Great! I'm glad that your problem is solved, and thanks for the

feedback!

_________________________________________________________

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?SlNtaXRo?= <JSmith@discussions.microsoft.com> wrote on

31 mar 2008 in microsoft.public.windows.terminal_services:

> THANK YOU!!!!!!! It turned out to be the rdp-tcp connection

> settings. I really appreciate your time and help with this

> issue.

>

> "Vera Noest [MVP]" wrote:

>

>> You are right, JSmith, a console session never uses or needs a

>> TS CAL. And moreover, TS CALs are not per concurrent

>> connection, so if you would run short of TS CALs, logging out

>> one client would not enable another client to log on.

>>

>> So the problem that you have is *not* related to TS CALs at

>> all. I can think of two reasons for the behaviour that you see

>> and you should be able to verify which one applies to you by

>> checking the EventLog on the server:

>>

>> a) the rdp-tcp connection settings are hardcoded to allow a

>> maximum of 9 concurrent connections. Check in Terminal Services

>> Configuration - rdp-tcp connection properties - network

>>

>> b) your server is configured to use the "Per Server" licensing

>> mode for OS licensing, and you are running out of server CALs,

>> not TS CALs. Server CALs are per concurrent connection. Check

>> in Control Panel - Licensing applet. If that's the problem,

>> make sure that you have enough server CALs for all connecting

>> devices and then disable the Licensing Logging Service

>> completely. Documented here:

>>

>> 824196 - Description of the License Logging Service in Windows

>> Server Operating Systems

>> http://support.microsoft.com/?kbid=824196

>>

>> _________________________________________________________

>> 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?SlNtaXRo?= <JSmith@discussions.microsoft.com> wrote

>> on 28 mar 2008 in microsoft.public.windows.terminal_services:

>>

>> > Thanks for the quick reply, however, Microsoft states:

>> >

>> > "A Terminal Server Client Access License (TS CAL) is required

>> > to use Terminal Server or otherwise host a remote graphical

>> > user interface (GUI) session, except for a console session."

>> >

>> > See:

>> > (http://www.microsoft.com/windowsserver2003/howtobuy/licensing

>> > /ov erview.mspx)

>> >

>> > As far as I understand, using "mstsc /console" is using a

>> > console session. Am I missing something?

>> >

>> >

>> >

>> > "Lanwench [MVP - Exchange]" wrote:

>> >

>> >> JSmith <JSmith@discussions.microsoft.com> wrote:

>> >> > We purchased 9 terminal server licenses (setup as per

>> >> > device). Whenever all 9 client computers are logged in, we

>> >> > are unable to connect to the server console using "mstsc

>> >> > /console" from a 10th management computer. However, if we

>> >> > log out 1 client computer then we are able to connect. We

>> >> > need to be able to remote control the 9 sessions from the

>> >> > management computer.

>> >> >

>> >> > Server: Windows 2003 Server x64

>> >> > RDP Client: version 6

>> >> > Management computer OS: Windows XP

>> >> > Client computer OS: HP thin client (t5135) connecting via

>> >> > RDP

>> >>

>> >> I think you'll need another TS CAL for this.

[Guest Lanwench [MVP - Exchange]]

Re: Problem with Licensing and "mstsc /console"

 

Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se> wrote:

> You are right, JSmith, a console session never uses or needs a TS

> CAL. And moreover, TS CALs are not per concurrent connection, so if

> you would run short of TS CALs, logging out one client would not

> enable another client to log on.

 

<cough>

 

I knew that.

 

<nibbles on hatbrim quietly>

>

 

<snipp>