Terminal Server Licensing with multiple TS machines...

  • Thread starter Thread starter Cary W. Shultz
  • Start date Start date
C

Cary W. Shultz

Good morning!

Here is a somewhat convoluted sitatuion (and I am sure that I will add to
that with my 'verbage'). This is for a client that I manage but only
recently came on-board as the "guy" for this client. Previous "guy" is no
longer with the company and the documentation is, er, lacking....let's just
keep it at that.

Okay. Client has two locations: the main corporate office and the
co-location space. There are three servers in each location.

Corporate office: SBS2003, WIN2003 member server (running TS and Citrix -
computer name is CITRIX2003 for purposes of this post) and another member
server....

Co-Load: Windows 2003 Server (DC), Windows 2003 member server (running TS -
computer name is TERMSERV2003 for purposes of this post) and another member
server

Here is how things currently work: user's log into CITRIX2003 as this
server is currently the "remote access" server. However, there is an
application that everyone needs to use (ACT!2008) and this application was
installed on TERMSERV2003. Accessing that is simple: users double-click an
icon (rdp shortcut) on their Citrix desktop.

Issue: when the users are connected to TERMSERV2003 they are starting to
receive the "temporary license will expire on DateX".

My guess (somewhat educated in this case): the 30 TS CALs that we have are
for CITRIX2003. So, to continue using TERMSERV2003 we need to purchase an
additional set of 30 TS CALs? Sure seems to be the case.

Any thoughts?

thanks,

Cary
 
Cary W. Shultz wrote:
> Good morning!
>
> Here is a somewhat convoluted sitatuion (and I am sure that I will add to
> that with my 'verbage'). This is for a client that I manage but only
> recently came on-board as the "guy" for this client. Previous "guy" is no
> longer with the company and the documentation is, er, lacking....let's just
> keep it at that.
>
> Okay. Client has two locations: the main corporate office and the
> co-location space. There are three servers in each location.
>
> Corporate office: SBS2003, WIN2003 member server (running TS and Citrix -
> computer name is CITRIX2003 for purposes of this post) and another member
> server....
>
> Co-Load: Windows 2003 Server (DC), Windows 2003 member server (running TS -
> computer name is TERMSERV2003 for purposes of this post) and another member
> server
>
> Here is how things currently work: user's log into CITRIX2003 as this
> server is currently the "remote access" server. However, there is an
> application that everyone needs to use (ACT!2008) and this application was
> installed on TERMSERV2003. Accessing that is simple: users double-click an
> icon (rdp shortcut) on their Citrix desktop.
>
> Issue: when the users are connected to TERMSERV2003 they are starting to
> receive the "temporary license will expire on DateX".
>
> My guess (somewhat educated in this case): the 30 TS CALs that we have are
> for CITRIX2003. So, to continue using TERMSERV2003 we need to purchase an
> additional set of 30 TS CALs? Sure seems to be the case.
>
> Any thoughts?

1. Where is the TS licensing server located?
1a. How many TS licenses are there? User or Device?

2. Are the co-location systems part of the domain also?
2a. If so, is the TERMSERV2003 pointing to the TS License server
in question 1?

moncho
 
Moncho,

Thanks - please see waaaayyy below - in-line!

"moncho" <moncho@NOspmanywhere.com> wrote in message
news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
> Cary W. Shultz wrote:
>> Good morning!
>>
>> Here is a somewhat convoluted sitatuion (and I am sure that I will add to
>> that with my 'verbage'). This is for a client that I manage but only
>> recently came on-board as the "guy" for this client. Previous "guy" is
>> no longer with the company and the documentation is, er, lacking....let's
>> just keep it at that.
>>
>> Okay. Client has two locations: the main corporate office and the
>> co-location space. There are three servers in each location.
>>
>> Corporate office: SBS2003, WIN2003 member server (running TS and
>> Citrix - computer name is CITRIX2003 for purposes of this post) and
>> another member server....
>>
>> Co-Load: Windows 2003 Server (DC), Windows 2003 member server (running
>> TS - computer name is TERMSERV2003 for purposes of this post) and another
>> member server
>>
>> Here is how things currently work: user's log into CITRIX2003 as this
>> server is currently the "remote access" server. However, there is an
>> application that everyone needs to use (ACT!2008) and this application
>> was installed on TERMSERV2003. Accessing that is simple: users
>> double-click an icon (rdp shortcut) on their Citrix desktop.
>>
>> Issue: when the users are connected to TERMSERV2003 they are starting to
>> receive the "temporary license will expire on DateX".
>>
>> My guess (somewhat educated in this case): the 30 TS CALs that we have
>> are for CITRIX2003. So, to continue using TERMSERV2003 we need to
>> purchase an additional set of 30 TS CALs? Sure seems to be the case.
>>
>> Any thoughts?
>
> 1. Where is the TS licensing server located?
> 1a. How many TS licenses are there? User or Device?


1. CITRIX2003 is the TSLS
1A. 30 CALs - user


>
> 2. Are the co-location systems part of the domain also?
> 2a. If so, is the TERMSERV2003 pointing to the TS License server
> in question 1?


2. yes, all machines are part of the same SBS2003 domain...there is a
Site-to-Site VPN between the two locations...everything seems to be working
fine on that end.

2A - not sure. How would I tell? If not, how would I configure this.

Also, just thinking ahead - CITRIX2003 will eventually be replaced -
meaning, TERMSERV2003 will do everything that CITRIX2003 does...not really
applicable to this specific issue, but something to consider....



>
> moncho
 
I *think* that this can be done via GPO....or, you can follow this link:

http://support.microsoft.com/kb/279561

There is, however, only one TSLS in the environment - CITRIX2003 and it is
handing out the Temporary Licenses. I used lsview and lsreport to determine
this.

Still, not sure wht the Licensing Server is handing out only Temporary
licenses....

Thanks,

cary
"Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote in message
news:Of5X5wlyIHA.2208@TK2MSFTNGP04.phx.gbl...
> Moncho,
>
> Thanks - please see waaaayyy below - in-line!
>
> "moncho" <moncho@NOspmanywhere.com> wrote in message
> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>> Cary W. Shultz wrote:
>>> Good morning!
>>>
>>> Here is a somewhat convoluted sitatuion (and I am sure that I will add
>>> to that with my 'verbage'). This is for a client that I manage but only
>>> recently came on-board as the "guy" for this client. Previous "guy" is
>>> no longer with the company and the documentation is, er,
>>> lacking....let's just keep it at that.
>>>
>>> Okay. Client has two locations: the main corporate office and the
>>> co-location space. There are three servers in each location.
>>>
>>> Corporate office: SBS2003, WIN2003 member server (running TS and
>>> Citrix - computer name is CITRIX2003 for purposes of this post) and
>>> another member server....
>>>
>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member server (running
>>> TS - computer name is TERMSERV2003 for purposes of this post) and
>>> another member server
>>>
>>> Here is how things currently work: user's log into CITRIX2003 as this
>>> server is currently the "remote access" server. However, there is an
>>> application that everyone needs to use (ACT!2008) and this application
>>> was installed on TERMSERV2003. Accessing that is simple: users
>>> double-click an icon (rdp shortcut) on their Citrix desktop.
>>>
>>> Issue: when the users are connected to TERMSERV2003 they are starting to
>>> receive the "temporary license will expire on DateX".
>>>
>>> My guess (somewhat educated in this case): the 30 TS CALs that we have
>>> are for CITRIX2003. So, to continue using TERMSERV2003 we need to
>>> purchase an additional set of 30 TS CALs? Sure seems to be the case.
>>>
>>> Any thoughts?
>>
>> 1. Where is the TS licensing server located?
>> 1a. How many TS licenses are there? User or Device?
>
>
> 1. CITRIX2003 is the TSLS
> 1A. 30 CALs - user
>
>
>>
>> 2. Are the co-location systems part of the domain also?
>> 2a. If so, is the TERMSERV2003 pointing to the TS License server
>> in question 1?
>
>
> 2. yes, all machines are part of the same SBS2003 domain...there is a
> Site-to-Site VPN between the two locations...everything seems to be
> working fine on that end.
>
> 2A - not sure. How would I tell? If not, how would I configure this.
>
> Also, just thinking ahead - CITRIX2003 will eventually be replaced -
> meaning, TERMSERV2003 will do everything that CITRIX2003 does...not really
> applicable to this specific issue, but something to consider....
>
>
>
>>
>> moncho
>
>
 
Cary W. Shultz wrote:
> Moncho,
>
> Thanks - please see waaaayyy below - in-line!
>
> "moncho" <moncho@NOspmanywhere.com> wrote in message
> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>> Cary W. Shultz wrote:
>>> Good morning!
>>>
>>> Here is a somewhat convoluted sitatuion (and I am sure that I will add to
>>> that with my 'verbage'). This is for a client that I manage but only
>>> recently came on-board as the "guy" for this client. Previous "guy" is
>>> no longer with the company and the documentation is, er, lacking....let's
>>> just keep it at that.
>>>
>>> Okay. Client has two locations: the main corporate office and the
>>> co-location space. There are three servers in each location.
>>>
>>> Corporate office: SBS2003, WIN2003 member server (running TS and
>>> Citrix - computer name is CITRIX2003 for purposes of this post) and
>>> another member server....
>>>
>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member server (running
>>> TS - computer name is TERMSERV2003 for purposes of this post) and another
>>> member server
>>>
>>> Here is how things currently work: user's log into CITRIX2003 as this
>>> server is currently the "remote access" server. However, there is an
>>> application that everyone needs to use (ACT!2008) and this application
>>> was installed on TERMSERV2003. Accessing that is simple: users
>>> double-click an icon (rdp shortcut) on their Citrix desktop.
>>>
>>> Issue: when the users are connected to TERMSERV2003 they are starting to
>>> receive the "temporary license will expire on DateX".
>>>
>>> My guess (somewhat educated in this case): the 30 TS CALs that we have
>>> are for CITRIX2003. So, to continue using TERMSERV2003 we need to
>>> purchase an additional set of 30 TS CALs? Sure seems to be the case.
>>>
>>> Any thoughts?
>> 1. Where is the TS licensing server located?
>> 1a. How many TS licenses are there? User or Device?
>
>
> 1. CITRIX2003 is the TSLS
> 1A. 30 CALs - user
>
>
>> 2. Are the co-location systems part of the domain also?
>> 2a. If so, is the TERMSERV2003 pointing to the TS License server
>> in question 1?
>
>
> 2. yes, all machines are part of the same SBS2003 domain...there is a
> Site-to-Site VPN between the two locations...everything seems to be working
> fine on that end.
>
> 2A - not sure. How would I tell? If not, how would I configure this.
>
> Also, just thinking ahead - CITRIX2003 will eventually be replaced -
> meaning, TERMSERV2003 will do everything that CITRIX2003 does...not really
> applicable to this specific issue, but something to consider....
>

You can look in the TS Configuration -> Server Settings ->
License Server Discovery to see where it is pointing.

Check out http://ts.veranoest.net/ts_licensing.htm

This may help with some of the other issues you are having.
There is some info on TS + Citrix also.

Another thing is, 2003 TS licensing (don't know about Citrix) does
not track user licenses, only device licenses.

If you are under the 30 User licenses in your entire domain, I would
verify that TERMSERV2003 is able to connect to the CITRIX2003 server.

moncho
 
Cary, if your LS is issueing temporary licenses, than at least one
of your servers (either the Citrix server or the TS or both) is
configured to use the Per Device licensing mode.
You have to make sure that both servers are in Per User licensing
mode, since you installed Per user licenses on the LS.
That's done in Terminal Services Configuration - Server settings.

And no, you don't need to buy TS CALs for each servers. You need
one Per User TS CAL for each user which connect, and that gives
those users the right to connect to any TS/Citrix server.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
microsoft.public.windows.terminal_services:

> Cary W. Shultz wrote:
>> Moncho,
>>
>> Thanks - please see waaaayyy below - in-line!
>>
>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>> Cary W. Shultz wrote:
>>>> Good morning!
>>>>
>>>> Here is a somewhat convoluted sitatuion (and I am sure that I
>>>> will add to that with my 'verbage'). This is for a client
>>>> that I manage but only recently came on-board as the "guy"
>>>> for this client. Previous "guy" is no longer with the
>>>> company and the documentation is, er, lacking....let's just
>>>> keep it at that.
>>>>
>>>> Okay. Client has two locations: the main corporate office
>>>> and the co-location space. There are three servers in each
>>>> location.
>>>>
>>>> Corporate office: SBS2003, WIN2003 member server (running TS
>>>> and Citrix - computer name is CITRIX2003 for purposes of this
>>>> post) and another member server....
>>>>
>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>> server (running TS - computer name is TERMSERV2003 for
>>>> purposes of this post) and another member server
>>>>
>>>> Here is how things currently work: user's log into
>>>> CITRIX2003 as this server is currently the "remote access"
>>>> server. However, there is an application that everyone needs
>>>> to use (ACT!2008) and this application was installed on
>>>> TERMSERV2003. Accessing that is simple: users double-click
>>>> an icon (rdp shortcut) on their Citrix desktop.
>>>>
>>>> Issue: when the users are connected to TERMSERV2003 they are
>>>> starting to receive the "temporary license will expire on
>>>> DateX".
>>>>
>>>> My guess (somewhat educated in this case): the 30 TS CALs
>>>> that we have are for CITRIX2003. So, to continue using
>>>> TERMSERV2003 we need to purchase an additional set of 30 TS
>>>> CALs? Sure seems to be the case.
>>>>
>>>> Any thoughts?
>>> 1. Where is the TS licensing server located?
>>> 1a. How many TS licenses are there? User or Device?
>>
>>
>> 1. CITRIX2003 is the TSLS
>> 1A. 30 CALs - user
>>
>>
>>> 2. Are the co-location systems part of the domain also?
>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>> server in question 1?
>>
>>
>> 2. yes, all machines are part of the same SBS2003
>> domain...there is a Site-to-Site VPN between the two
>> locations...everything seems to be working fine on that end.
>>
>> 2A - not sure. How would I tell? If not, how would I
>> configure this.
>>
>> Also, just thinking ahead - CITRIX2003 will eventually be
>> replaced - meaning, TERMSERV2003 will do everything that
>> CITRIX2003 does...not really applicable to this specific issue,
>> but something to consider....
>>
>
> You can look in the TS Configuration -> Server Settings ->
> License Server Discovery to see where it is pointing.
>
> Check out http://ts.veranoest.net/ts_licensing.htm
>
> This may help with some of the other issues you are having.
> There is some info on TS + Citrix also.
>
> Another thing is, 2003 TS licensing (don't know about Citrix)
> does not track user licenses, only device licenses.
>
> If you are under the 30 User licenses in your entire domain, I
> would verify that TERMSERV2003 is able to connect to the
> CITRIX2003 server.
>
> moncho
 
Vera,

Dag gum it! I checked and mis-saw....

As usual, you are correct. The TERMSERV2003 was in 'device mode'. I knew
this and missed it.

However, thank you for answering another question that I had....license per
server. I thought that this was the case...obviously not!

Thanks,

Cary
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AB8DC7A19739veranoesthemutforsse@207.46.248.16...
> Cary, if your LS is issueing temporary licenses, than at least one
> of your servers (either the Citrix server or the TS or both) is
> configured to use the Per Device licensing mode.
> You have to make sure that both servers are in Per User licensing
> mode, since you installed Per user licenses on the LS.
> That's done in Terminal Services Configuration - Server settings.
>
> And no, you don't need to buy TS CALs for each servers. You need
> one Per User TS CAL for each user which connect, and that gives
> those users the right to connect to any TS/Citrix server.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
> microsoft.public.windows.terminal_services:
>
>> Cary W. Shultz wrote:
>>> Moncho,
>>>
>>> Thanks - please see waaaayyy below - in-line!
>>>
>>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>>> Cary W. Shultz wrote:
>>>>> Good morning!
>>>>>
>>>>> Here is a somewhat convoluted sitatuion (and I am sure that I
>>>>> will add to that with my 'verbage'). This is for a client
>>>>> that I manage but only recently came on-board as the "guy"
>>>>> for this client. Previous "guy" is no longer with the
>>>>> company and the documentation is, er, lacking....let's just
>>>>> keep it at that.
>>>>>
>>>>> Okay. Client has two locations: the main corporate office
>>>>> and the co-location space. There are three servers in each
>>>>> location.
>>>>>
>>>>> Corporate office: SBS2003, WIN2003 member server (running TS
>>>>> and Citrix - computer name is CITRIX2003 for purposes of this
>>>>> post) and another member server....
>>>>>
>>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>>> server (running TS - computer name is TERMSERV2003 for
>>>>> purposes of this post) and another member server
>>>>>
>>>>> Here is how things currently work: user's log into
>>>>> CITRIX2003 as this server is currently the "remote access"
>>>>> server. However, there is an application that everyone needs
>>>>> to use (ACT!2008) and this application was installed on
>>>>> TERMSERV2003. Accessing that is simple: users double-click
>>>>> an icon (rdp shortcut) on their Citrix desktop.
>>>>>
>>>>> Issue: when the users are connected to TERMSERV2003 they are
>>>>> starting to receive the "temporary license will expire on
>>>>> DateX".
>>>>>
>>>>> My guess (somewhat educated in this case): the 30 TS CALs
>>>>> that we have are for CITRIX2003. So, to continue using
>>>>> TERMSERV2003 we need to purchase an additional set of 30 TS
>>>>> CALs? Sure seems to be the case.
>>>>>
>>>>> Any thoughts?
>>>> 1. Where is the TS licensing server located?
>>>> 1a. How many TS licenses are there? User or Device?
>>>
>>>
>>> 1. CITRIX2003 is the TSLS
>>> 1A. 30 CALs - user
>>>
>>>
>>>> 2. Are the co-location systems part of the domain also?
>>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>>> server in question 1?
>>>
>>>
>>> 2. yes, all machines are part of the same SBS2003
>>> domain...there is a Site-to-Site VPN between the two
>>> locations...everything seems to be working fine on that end.
>>>
>>> 2A - not sure. How would I tell? If not, how would I
>>> configure this.
>>>
>>> Also, just thinking ahead - CITRIX2003 will eventually be
>>> replaced - meaning, TERMSERV2003 will do everything that
>>> CITRIX2003 does...not really applicable to this specific issue,
>>> but something to consider....
>>>
>>
>> You can look in the TS Configuration -> Server Settings ->
>> License Server Discovery to see where it is pointing.
>>
>> Check out http://ts.veranoest.net/ts_licensing.htm
>>
>> This may help with some of the other issues you are having.
>> There is some info on TS + Citrix also.
>>
>> Another thing is, 2003 TS licensing (don't know about Citrix)
>> does not track user licenses, only device licenses.
>>
>> If you are under the 30 User licenses in your entire domain, I
>> would verify that TERMSERV2003 is able to connect to the
>> CITRIX2003 server.
>>
>> moncho
 
The "license per server" versus license per user or device" concept
is applicable to Windows CALs, but not to TS CALs.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 09
jun 2008 in microsoft.public.windows.terminal_services:

> Vera,
>
> Dag gum it! I checked and mis-saw....
>
> As usual, you are correct. The TERMSERV2003 was in 'device
> mode'. I knew this and missed it.
>
> However, thank you for answering another question that I
> had....license per server. I thought that this was the
> case...obviously not!
>
> Thanks,
>
> Cary
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9AB8DC7A19739veranoesthemutforsse@207.46.248.16...
>> Cary, if your LS is issueing temporary licenses, than at least
>> one of your servers (either the Citrix server or the TS or
>> both) is configured to use the Per Device licensing mode.
>> You have to make sure that both servers are in Per User
>> licensing mode, since you installed Per user licenses on the
>> LS. That's done in Terminal Services Configuration - Server
>> settings.
>>
>> And no, you don't need to buy TS CALs for each servers. You
>> need one Per User TS CAL for each user which connect, and that
>> gives those users the right to connect to any TS/Citrix server.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> Cary W. Shultz wrote:
>>>> Moncho,
>>>>
>>>> Thanks - please see waaaayyy below - in-line!
>>>>
>>>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>>>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>>>> Cary W. Shultz wrote:
>>>>>> Good morning!
>>>>>>
>>>>>> Here is a somewhat convoluted sitatuion (and I am sure that
>>>>>> I will add to that with my 'verbage'). This is for a
>>>>>> client that I manage but only recently came on-board as the
>>>>>> "guy" for this client. Previous "guy" is no longer with
>>>>>> the company and the documentation is, er, lacking....let's
>>>>>> just keep it at that.
>>>>>>
>>>>>> Okay. Client has two locations: the main corporate office
>>>>>> and the co-location space. There are three servers in each
>>>>>> location.
>>>>>>
>>>>>> Corporate office: SBS2003, WIN2003 member server (running
>>>>>> TS and Citrix - computer name is CITRIX2003 for purposes of
>>>>>> this post) and another member server....
>>>>>>
>>>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>>>> server (running TS - computer name is TERMSERV2003 for
>>>>>> purposes of this post) and another member server
>>>>>>
>>>>>> Here is how things currently work: user's log into
>>>>>> CITRIX2003 as this server is currently the "remote access"
>>>>>> server. However, there is an application that everyone
>>>>>> needs to use (ACT!2008) and this application was installed
>>>>>> on TERMSERV2003. Accessing that is simple: users
>>>>>> double-click an icon (rdp shortcut) on their Citrix
>>>>>> desktop.
>>>>>>
>>>>>> Issue: when the users are connected to TERMSERV2003 they
>>>>>> are starting to receive the "temporary license will expire
>>>>>> on DateX".
>>>>>>
>>>>>> My guess (somewhat educated in this case): the 30 TS CALs
>>>>>> that we have are for CITRIX2003. So, to continue using
>>>>>> TERMSERV2003 we need to purchase an additional set of 30 TS
>>>>>> CALs? Sure seems to be the case.
>>>>>>
>>>>>> Any thoughts?
>>>>> 1. Where is the TS licensing server located?
>>>>> 1a. How many TS licenses are there? User or Device?
>>>>
>>>>
>>>> 1. CITRIX2003 is the TSLS
>>>> 1A. 30 CALs - user
>>>>
>>>>
>>>>> 2. Are the co-location systems part of the domain also?
>>>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>>>> server in question 1?
>>>>
>>>>
>>>> 2. yes, all machines are part of the same SBS2003
>>>> domain...there is a Site-to-Site VPN between the two
>>>> locations...everything seems to be working fine on that end.
>>>>
>>>> 2A - not sure. How would I tell? If not, how would I
>>>> configure this.
>>>>
>>>> Also, just thinking ahead - CITRIX2003 will eventually be
>>>> replaced - meaning, TERMSERV2003 will do everything that
>>>> CITRIX2003 does...not really applicable to this specific
>>>> issue, but something to consider....
>>>>
>>>
>>> You can look in the TS Configuration -> Server Settings ->
>>> License Server Discovery to see where it is pointing.
>>>
>>> Check out http://ts.veranoest.net/ts_licensing.htm
>>>
>>> This may help with some of the other issues you are having.
>>> There is some info on TS + Citrix also.
>>>
>>> Another thing is, 2003 TS licensing (don't know about Citrix)
>>> does not track user licenses, only device licenses.
>>>
>>> If you are under the 30 User licenses in your entire domain, I
>>> would verify that TERMSERV2003 is able to connect to the
>>> CITRIX2003 server.
>>>
>>> moncho
 
Vera,

Follow up question: with multiple Terminal servers in a single
environment - especially with the way things work in this specific
environment (user remote into CITRIX2003 and when they need to use one
specific application they - from the CITRIX2003 box - RDP into TERMSERV2003)
if I configure the GPO to 'Restrict Terminal Services users to a single
remote session' is this going to cause an issue? Meaning, they could
connect to CITRIX2003 but would then not be allowed to connect to
TErMSERV2003?

Thanks,

Cary


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AB8E75B61FFBveranoesthemutforsse@207.46.248.16...
> The "license per server" versus license per user or device" concept
> is applicable to Windows CALs, but not to TS CALs.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 09
> jun 2008 in microsoft.public.windows.terminal_services:
>
>> Vera,
>>
>> Dag gum it! I checked and mis-saw....
>>
>> As usual, you are correct. The TERMSERV2003 was in 'device
>> mode'. I knew this and missed it.
>>
>> However, thank you for answering another question that I
>> had....license per server. I thought that this was the
>> case...obviously not!
>>
>> Thanks,
>>
>> Cary
>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>> in message
>> news:Xns9AB8DC7A19739veranoesthemutforsse@207.46.248.16...
>>> Cary, if your LS is issueing temporary licenses, than at least
>>> one of your servers (either the Citrix server or the TS or
>>> both) is configured to use the Per Device licensing mode.
>>> You have to make sure that both servers are in Per User
>>> licensing mode, since you installed Per user licenses on the
>>> LS. That's done in Terminal Services Configuration - Server
>>> settings.
>>>
>>> And no, you don't need to buy TS CALs for each servers. You
>>> need one Per User TS CAL for each user which connect, and that
>>> gives those users the right to connect to any TS/Citrix server.
>>>
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
>>> microsoft.public.windows.terminal_services:
>>>
>>>> Cary W. Shultz wrote:
>>>>> Moncho,
>>>>>
>>>>> Thanks - please see waaaayyy below - in-line!
>>>>>
>>>>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>>>>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>>>>> Cary W. Shultz wrote:
>>>>>>> Good morning!
>>>>>>>
>>>>>>> Here is a somewhat convoluted sitatuion (and I am sure that
>>>>>>> I will add to that with my 'verbage'). This is for a
>>>>>>> client that I manage but only recently came on-board as the
>>>>>>> "guy" for this client. Previous "guy" is no longer with
>>>>>>> the company and the documentation is, er, lacking....let's
>>>>>>> just keep it at that.
>>>>>>>
>>>>>>> Okay. Client has two locations: the main corporate office
>>>>>>> and the co-location space. There are three servers in each
>>>>>>> location.
>>>>>>>
>>>>>>> Corporate office: SBS2003, WIN2003 member server (running
>>>>>>> TS and Citrix - computer name is CITRIX2003 for purposes of
>>>>>>> this post) and another member server....
>>>>>>>
>>>>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>>>>> server (running TS - computer name is TERMSERV2003 for
>>>>>>> purposes of this post) and another member server
>>>>>>>
>>>>>>> Here is how things currently work: user's log into
>>>>>>> CITRIX2003 as this server is currently the "remote access"
>>>>>>> server. However, there is an application that everyone
>>>>>>> needs to use (ACT!2008) and this application was installed
>>>>>>> on TERMSERV2003. Accessing that is simple: users
>>>>>>> double-click an icon (rdp shortcut) on their Citrix
>>>>>>> desktop.
>>>>>>>
>>>>>>> Issue: when the users are connected to TERMSERV2003 they
>>>>>>> are starting to receive the "temporary license will expire
>>>>>>> on DateX".
>>>>>>>
>>>>>>> My guess (somewhat educated in this case): the 30 TS CALs
>>>>>>> that we have are for CITRIX2003. So, to continue using
>>>>>>> TERMSERV2003 we need to purchase an additional set of 30 TS
>>>>>>> CALs? Sure seems to be the case.
>>>>>>>
>>>>>>> Any thoughts?
>>>>>> 1. Where is the TS licensing server located?
>>>>>> 1a. How many TS licenses are there? User or Device?
>>>>>
>>>>>
>>>>> 1. CITRIX2003 is the TSLS
>>>>> 1A. 30 CALs - user
>>>>>
>>>>>
>>>>>> 2. Are the co-location systems part of the domain also?
>>>>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>>>>> server in question 1?
>>>>>
>>>>>
>>>>> 2. yes, all machines are part of the same SBS2003
>>>>> domain...there is a Site-to-Site VPN between the two
>>>>> locations...everything seems to be working fine on that end.
>>>>>
>>>>> 2A - not sure. How would I tell? If not, how would I
>>>>> configure this.
>>>>>
>>>>> Also, just thinking ahead - CITRIX2003 will eventually be
>>>>> replaced - meaning, TERMSERV2003 will do everything that
>>>>> CITRIX2003 does...not really applicable to this specific
>>>>> issue, but something to consider....
>>>>>
>>>>
>>>> You can look in the TS Configuration -> Server Settings ->
>>>> License Server Discovery to see where it is pointing.
>>>>
>>>> Check out http://ts.veranoest.net/ts_licensing.htm
>>>>
>>>> This may help with some of the other issues you are having.
>>>> There is some info on TS + Citrix also.
>>>>
>>>> Another thing is, 2003 TS licensing (don't know about Citrix)
>>>> does not track user licenses, only device licenses.
>>>>
>>>> If you are under the 30 User licenses in your entire domain, I
>>>> would verify that TERMSERV2003 is able to connect to the
>>>> CITRIX2003 server.
>>>>
>>>> moncho
 
The "single session" setting applies to the TS, not the user
account. So users will still be able to start a new rdp-over-rdp
session from the Citrix server to the TS.
Note that in a TS farm with session directory, users trying to
start a second session will be redirected to the same server where
they already have a session, so there the setting effectively
applies to the whole TS farm.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 10
jun 2008 in microsoft.public.windows.terminal_services:

> Vera,
>
> Follow up question: with multiple Terminal servers in a single
> environment - especially with the way things work in this
> specific environment (user remote into CITRIX2003 and when they
> need to use one specific application they - from the CITRIX2003
> box - RDP into TERMSERV2003) if I configure the GPO to 'Restrict
> Terminal Services users to a single remote session' is this
> going to cause an issue? Meaning, they could connect to
> CITRIX2003 but would then not be allowed to connect to
> TErMSERV2003?
>
> Thanks,
>
> Cary
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9AB8E75B61FFBveranoesthemutforsse@207.46.248.16...
>> The "license per server" versus license per user or device"
>> concept is applicable to Windows CALs, but not to TS CALs.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>> 09 jun 2008 in microsoft.public.windows.terminal_services:
>>
>>> Vera,
>>>
>>> Dag gum it! I checked and mis-saw....
>>>
>>> As usual, you are correct. The TERMSERV2003 was in 'device
>>> mode'. I knew this and missed it.
>>>
>>> However, thank you for answering another question that I
>>> had....license per server. I thought that this was the
>>> case...obviously not!
>>>
>>> Thanks,
>>>
>>> Cary
>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>> wrote in message
>>> news:Xns9AB8DC7A19739veranoesthemutforsse@207.46.248.16...
>>>> Cary, if your LS is issueing temporary licenses, than at
>>>> least one of your servers (either the Citrix server or the TS
>>>> or both) is configured to use the Per Device licensing mode.
>>>> You have to make sure that both servers are in Per User
>>>> licensing mode, since you installed Per user licenses on the
>>>> LS. That's done in Terminal Services Configuration - Server
>>>> settings.
>>>>
>>>> And no, you don't need to buy TS CALs for each servers. You
>>>> need one Per User TS CAL for each user which connect, and
>>>> that gives those users the right to connect to any TS/Citrix
>>>> server.
>>>>
>>>> _________________________________________________________
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> TS troubleshooting: http://ts.veranoest.net
>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>
>>>> moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
>>>> microsoft.public.windows.terminal_services:
>>>>
>>>>> Cary W. Shultz wrote:
>>>>>> Moncho,
>>>>>>
>>>>>> Thanks - please see waaaayyy below - in-line!
>>>>>>
>>>>>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>>>>>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>>>>>> Cary W. Shultz wrote:
>>>>>>>> Good morning!
>>>>>>>>
>>>>>>>> Here is a somewhat convoluted sitatuion (and I am sure
>>>>>>>> that I will add to that with my 'verbage'). This is for
>>>>>>>> a client that I manage but only recently came on-board as
>>>>>>>> the "guy" for this client. Previous "guy" is no longer
>>>>>>>> with the company and the documentation is, er,
>>>>>>>> lacking....let's just keep it at that.
>>>>>>>>
>>>>>>>> Okay. Client has two locations: the main corporate
>>>>>>>> office and the co-location space. There are three
>>>>>>>> servers in each location.
>>>>>>>>
>>>>>>>> Corporate office: SBS2003, WIN2003 member server
>>>>>>>> (running TS and Citrix - computer name is CITRIX2003 for
>>>>>>>> purposes of this post) and another member server....
>>>>>>>>
>>>>>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>>>>>> server (running TS - computer name is TERMSERV2003 for
>>>>>>>> purposes of this post) and another member server
>>>>>>>>
>>>>>>>> Here is how things currently work: user's log into
>>>>>>>> CITRIX2003 as this server is currently the "remote
>>>>>>>> access" server. However, there is an application that
>>>>>>>> everyone needs to use (ACT!2008) and this application was
>>>>>>>> installed on TERMSERV2003. Accessing that is simple:
>>>>>>>> users double-click an icon (rdp shortcut) on their Citrix
>>>>>>>> desktop.
>>>>>>>>
>>>>>>>> Issue: when the users are connected to TERMSERV2003 they
>>>>>>>> are starting to receive the "temporary license will
>>>>>>>> expire on DateX".
>>>>>>>>
>>>>>>>> My guess (somewhat educated in this case): the 30 TS
>>>>>>>> CALs that we have are for CITRIX2003. So, to continue
>>>>>>>> using TERMSERV2003 we need to purchase an additional set
>>>>>>>> of 30 TS CALs? Sure seems to be the case.
>>>>>>>>
>>>>>>>> Any thoughts?
>>>>>>> 1. Where is the TS licensing server located?
>>>>>>> 1a. How many TS licenses are there? User or Device?
>>>>>>
>>>>>>
>>>>>> 1. CITRIX2003 is the TSLS
>>>>>> 1A. 30 CALs - user
>>>>>>
>>>>>>
>>>>>>> 2. Are the co-location systems part of the domain also?
>>>>>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>>>>>> server in question 1?
>>>>>>
>>>>>>
>>>>>> 2. yes, all machines are part of the same SBS2003
>>>>>> domain...there is a Site-to-Site VPN between the two
>>>>>> locations...everything seems to be working fine on that
>>>>>> end.
>>>>>>
>>>>>> 2A - not sure. How would I tell? If not, how would I
>>>>>> configure this.
>>>>>>
>>>>>> Also, just thinking ahead - CITRIX2003 will eventually be
>>>>>> replaced - meaning, TERMSERV2003 will do everything that
>>>>>> CITRIX2003 does...not really applicable to this specific
>>>>>> issue, but something to consider....
>>>>>>
>>>>>
>>>>> You can look in the TS Configuration -> Server Settings ->
>>>>> License Server Discovery to see where it is pointing.
>>>>>
>>>>> Check out http://ts.veranoest.net/ts_licensing.htm
>>>>>
>>>>> This may help with some of the other issues you are having.
>>>>> There is some info on TS + Citrix also.
>>>>>
>>>>> Another thing is, 2003 TS licensing (don't know about
>>>>> Citrix) does not track user licenses, only device licenses.
>>>>>
>>>>> If you are under the 30 User licenses in your entire domain,
>>>>> I would verify that TERMSERV2003 is able to connect to the
>>>>> CITRIX2003 server.
>>>>>
>>>>> moncho
 
Vera,

As always - Thanks!

Cary

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AB9E164AA482veranoesthemutforsse@207.46.248.16...
> The "single session" setting applies to the TS, not the user
> account. So users will still be able to start a new rdp-over-rdp
> session from the Citrix server to the TS.
> Note that in a TS farm with session directory, users trying to
> start a second session will be redirected to the same server where
> they already have a session, so there the setting effectively
> applies to the whole TS farm.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on 10
> jun 2008 in microsoft.public.windows.terminal_services:
>
>> Vera,
>>
>> Follow up question: with multiple Terminal servers in a single
>> environment - especially with the way things work in this
>> specific environment (user remote into CITRIX2003 and when they
>> need to use one specific application they - from the CITRIX2003
>> box - RDP into TERMSERV2003) if I configure the GPO to 'Restrict
>> Terminal Services users to a single remote session' is this
>> going to cause an issue? Meaning, they could connect to
>> CITRIX2003 but would then not be allowed to connect to
>> TErMSERV2003?
>>
>> Thanks,
>>
>> Cary
>>
>>
>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>> in message
>> news:Xns9AB8E75B61FFBveranoesthemutforsse@207.46.248.16...
>>> The "license per server" versus license per user or device"
>>> concept is applicable to Windows CALs, but not to TS CALs.
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> TS troubleshooting: http://ts.veranoest.net
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> "Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote on
>>> 09 jun 2008 in microsoft.public.windows.terminal_services:
>>>
>>>> Vera,
>>>>
>>>> Dag gum it! I checked and mis-saw....
>>>>
>>>> As usual, you are correct. The TERMSERV2003 was in 'device
>>>> mode'. I knew this and missed it.
>>>>
>>>> However, thank you for answering another question that I
>>>> had....license per server. I thought that this was the
>>>> case...obviously not!
>>>>
>>>> Thanks,
>>>>
>>>> Cary
>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>> wrote in message
>>>> news:Xns9AB8DC7A19739veranoesthemutforsse@207.46.248.16...
>>>>> Cary, if your LS is issueing temporary licenses, than at
>>>>> least one of your servers (either the Citrix server or the TS
>>>>> or both) is configured to use the Per Device licensing mode.
>>>>> You have to make sure that both servers are in Per User
>>>>> licensing mode, since you installed Per user licenses on the
>>>>> LS. That's done in Terminal Services Configuration - Server
>>>>> settings.
>>>>>
>>>>> And no, you don't need to buy TS CALs for each servers. You
>>>>> need one Per User TS CAL for each user which connect, and
>>>>> that gives those users the right to connect to any TS/Citrix
>>>>> server.
>>>>>
>>>>> _________________________________________________________
>>>>> Vera Noest
>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>
>>>>> moncho <moncho@NOspmanywhere.com> wrote on 09 jun 2008 in
>>>>> microsoft.public.windows.terminal_services:
>>>>>
>>>>>> Cary W. Shultz wrote:
>>>>>>> Moncho,
>>>>>>>
>>>>>>> Thanks - please see waaaayyy below - in-line!
>>>>>>>
>>>>>>> "moncho" <moncho@NOspmanywhere.com> wrote in message
>>>>>>> news:KSd3k.2632$cW3.1246@nlpi064.nbdc.sbc.com...
>>>>>>>> Cary W. Shultz wrote:
>>>>>>>>> Good morning!
>>>>>>>>>
>>>>>>>>> Here is a somewhat convoluted sitatuion (and I am sure
>>>>>>>>> that I will add to that with my 'verbage'). This is for
>>>>>>>>> a client that I manage but only recently came on-board as
>>>>>>>>> the "guy" for this client. Previous "guy" is no longer
>>>>>>>>> with the company and the documentation is, er,
>>>>>>>>> lacking....let's just keep it at that.
>>>>>>>>>
>>>>>>>>> Okay. Client has two locations: the main corporate
>>>>>>>>> office and the co-location space. There are three
>>>>>>>>> servers in each location.
>>>>>>>>>
>>>>>>>>> Corporate office: SBS2003, WIN2003 member server
>>>>>>>>> (running TS and Citrix - computer name is CITRIX2003 for
>>>>>>>>> purposes of this post) and another member server....
>>>>>>>>>
>>>>>>>>> Co-Load: Windows 2003 Server (DC), Windows 2003 member
>>>>>>>>> server (running TS - computer name is TERMSERV2003 for
>>>>>>>>> purposes of this post) and another member server
>>>>>>>>>
>>>>>>>>> Here is how things currently work: user's log into
>>>>>>>>> CITRIX2003 as this server is currently the "remote
>>>>>>>>> access" server. However, there is an application that
>>>>>>>>> everyone needs to use (ACT!2008) and this application was
>>>>>>>>> installed on TERMSERV2003. Accessing that is simple:
>>>>>>>>> users double-click an icon (rdp shortcut) on their Citrix
>>>>>>>>> desktop.
>>>>>>>>>
>>>>>>>>> Issue: when the users are connected to TERMSERV2003 they
>>>>>>>>> are starting to receive the "temporary license will
>>>>>>>>> expire on DateX".
>>>>>>>>>
>>>>>>>>> My guess (somewhat educated in this case): the 30 TS
>>>>>>>>> CALs that we have are for CITRIX2003. So, to continue
>>>>>>>>> using TERMSERV2003 we need to purchase an additional set
>>>>>>>>> of 30 TS CALs? Sure seems to be the case.
>>>>>>>>>
>>>>>>>>> Any thoughts?
>>>>>>>> 1. Where is the TS licensing server located?
>>>>>>>> 1a. How many TS licenses are there? User or Device?
>>>>>>>
>>>>>>>
>>>>>>> 1. CITRIX2003 is the TSLS
>>>>>>> 1A. 30 CALs - user
>>>>>>>
>>>>>>>
>>>>>>>> 2. Are the co-location systems part of the domain also?
>>>>>>>> 2a. If so, is the TERMSERV2003 pointing to the TS License
>>>>>>>> server in question 1?
>>>>>>>
>>>>>>>
>>>>>>> 2. yes, all machines are part of the same SBS2003
>>>>>>> domain...there is a Site-to-Site VPN between the two
>>>>>>> locations...everything seems to be working fine on that
>>>>>>> end.
>>>>>>>
>>>>>>> 2A - not sure. How would I tell? If not, how would I
>>>>>>> configure this.
>>>>>>>
>>>>>>> Also, just thinking ahead - CITRIX2003 will eventually be
>>>>>>> replaced - meaning, TERMSERV2003 will do everything that
>>>>>>> CITRIX2003 does...not really applicable to this specific
>>>>>>> issue, but something to consider....
>>>>>>>
>>>>>>
>>>>>> You can look in the TS Configuration -> Server Settings ->
>>>>>> License Server Discovery to see where it is pointing.
>>>>>>
>>>>>> Check out http://ts.veranoest.net/ts_licensing.htm
>>>>>>
>>>>>> This may help with some of the other issues you are having.
>>>>>> There is some info on TS + Citrix also.
>>>>>>
>>>>>> Another thing is, 2003 TS licensing (don't know about
>>>>>> Citrix) does not track user licenses, only device licenses.
>>>>>>
>>>>>> If you are under the 30 User licenses in your entire domain,
>>>>>> I would verify that TERMSERV2003 is able to connect to the
>>>>>> CITRIX2003 server.
>>>>>>
>>>>>> moncho
 
Back
Top