User licensing

  • Thread starter Thread starter Markus
  • Start date Start date
M

Markus

Guest
I am planning to install Server 2003 and need some advice on licensing.

My client needs a maximum of 10 concurrent users using an application.
However, they have hundreds of employees, any one of which could be one of
the 10 concurrent users.

On the server side, I understand Server 2003 comes with 5 CALs, so I assume
I will need 5 additional CALs. But am not sure what other licenses I need.

I read about roaming users, and would assume I need per user licensing for
10 roaming users, since the 10 users on any one day could log in from
different departments and so different devices.

Could someone clarify just what licensing I would need for this configuration.

Thanks for any help you can give,
Mark
 
RE: User licensing

If the licenses are needed for connection to a terminal server, you'll need
TS CALs. Microsoft licensing is not based on concurrent users as Citrix is
but on user/device CALs.

"Markus" wrote:

> I am planning to install Server 2003 and need some advice on licensing.
>
> My client needs a maximum of 10 concurrent users using an application.
> However, they have hundreds of employees, any one of which could be one of
> the 10 concurrent users.
>
> On the server side, I understand Server 2003 comes with 5 CALs, so I assume
> I will need 5 additional CALs. But am not sure what other licenses I need.
>
> I read about roaming users, and would assume I need per user licensing for
> 10 roaming users, since the 10 users on any one day could log in from
> different departments and so different devices.
>
> Could someone clarify just what licensing I would need for this configuration.
>
> Thanks for any help you can give,
> Mark
>
 
Re: User licensing

Hi Mark,

TS licensing is *not* concurrent. It is either Per Device or Per
User (named employee). Licenses can be reassigned away from
one device/user to another but the reassignment must be
permanent *except* in the case of when you use a temporary
replacement device (in the case of the primary device needing
repair) or a temporary employee (in the case of a temp worker
filling in while an employee is out).

The same is true for Windows CALs if you choose the
Per Device/Per User option for those. Other software have
different licensing requirements, for example, Office is licensed
Per Device.

You should count up the total number of devices and employees
that will be connecting and based on that choose between
Per Device or Per User or a mix of the two. If you post more
information regarding the number of PCs, employees, employees
that need to roam, etc., I will give you more advice.

Thanks.

-TP

Markus wrote:
> I am planning to install Server 2003 and need some advice on
> licensing.
>
> My client needs a maximum of 10 concurrent users using an application.
> However, they have hundreds of employees, any one of which could be
> one of the 10 concurrent users.
>
> On the server side, I understand Server 2003 comes with 5 CALs, so I
> assume
> I will need 5 additional CALs. But am not sure what other licenses I
> need.
>
> I read about roaming users, and would assume I need per user
> licensing for 10 roaming users, since the 10 users on any one day
> could log in from different departments and so different devices.
>
> Could someone clarify just what licensing I would need for this
> configuration.
>
> Thanks for any help you can give,
> Mark
 
Re: User licensing

TP,

There are just under 3000 employees working in just under 1000 departments.
However, this application is small, and will require no more than 10 of those
3000 people to use the application at any one time, and probably more like 5
on average.

Their use would involve less than 10 minutes a day, resulting in maybe 50 to
100 minutes of actual time logged in each day across all departments. The
login can occur at any department computer, and each department has an
average of 3 computers.

We could not licensse on a per machine basis, since that would require
thousands of licenses and give far more capability than we need. I thought
we could license 10 roaming users. This would allow an employee to log in to
add a record to a database and log out from any one of their department
computers.

Appreciate your help in explaining how this works.

Thanks again,
Mark

"TP" wrote:

> Hi Mark,
>
> TS licensing is *not* concurrent. It is either Per Device or Per
> User (named employee). Licenses can be reassigned away from
> one device/user to another but the reassignment must be
> permanent *except* in the case of when you use a temporary
> replacement device (in the case of the primary device needing
> repair) or a temporary employee (in the case of a temp worker
> filling in while an employee is out).
>
> The same is true for Windows CALs if you choose the
> Per Device/Per User option for those. Other software have
> different licensing requirements, for example, Office is licensed
> Per Device.
>
> You should count up the total number of devices and employees
> that will be connecting and based on that choose between
> Per Device or Per User or a mix of the two. If you post more
> information regarding the number of PCs, employees, employees
> that need to roam, etc., I will give you more advice.
>
> Thanks.
>
> -TP
>
> Markus wrote:
> > I am planning to install Server 2003 and need some advice on
> > licensing.
> >
> > My client needs a maximum of 10 concurrent users using an application.
> > However, they have hundreds of employees, any one of which could be
> > one of the 10 concurrent users.
> >
> > On the server side, I understand Server 2003 comes with 5 CALs, so I
> > assume
> > I will need 5 additional CALs. But am not sure what other licenses I
> > need.
> >
> > I read about roaming users, and would assume I need per user
> > licensing for 10 roaming users, since the 10 users on any one day
> > could log in from different departments and so different devices.
> >
> > Could someone clarify just what licensing I would need for this
> > configuration.
> >
> > Thanks for any help you can give,
> > Mark
>
 
Re: User licensing

As TP explained, that's not a valid licensing mode of TS. It's
either per specific user, or per specific device.
I understand that it would become very costly for your specific
requirements, but still, it's what the EULA dictates.

Is this application the *only* application that you plan to deploy
through TS? If so, maybe TS is not the best way to deploy it. But
if the users connect to the TS also to run other applications, they
will need a TS CAL anyway.
_________________________________________________________
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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
12 dec 2007 in microsoft.public.windows.terminal_services:

> TP,
>
> There are just under 3000 employees working in just under 1000
> departments. However, this application is small, and will
> require no more than 10 of those 3000 people to use the
> application at any one time, and probably more like 5 on
> average.
>
> Their use would involve less than 10 minutes a day, resulting in
> maybe 50 to 100 minutes of actual time logged in each day across
> all departments. The login can occur at any department
> computer, and each department has an average of 3 computers.
>
> We could not licensse on a per machine basis, since that would
> require thousands of licenses and give far more capability than
> we need. I thought we could license 10 roaming users. This
> would allow an employee to log in to add a record to a database
> and log out from any one of their department computers.
>
> Appreciate your help in explaining how this works.
>
> Thanks again,
> Mark
>
> "TP" wrote:
>
>> Hi Mark,
>>
>> TS licensing is *not* concurrent. It is either Per Device or
>> Per User (named employee). Licenses can be reassigned away
>> from one device/user to another but the reassignment must be
>> permanent *except* in the case of when you use a temporary
>> replacement device (in the case of the primary device needing
>> repair) or a temporary employee (in the case of a temp worker
>> filling in while an employee is out).
>>
>> The same is true for Windows CALs if you choose the
>> Per Device/Per User option for those. Other software have
>> different licensing requirements, for example, Office is
>> licensed Per Device.
>>
>> You should count up the total number of devices and employees
>> that will be connecting and based on that choose between
>> Per Device or Per User or a mix of the two. If you post more
>> information regarding the number of PCs, employees, employees
>> that need to roam, etc., I will give you more advice.
>>
>> Thanks.
>>
>> -TP
>>
>> Markus wrote:
>> > I am planning to install Server 2003 and need some advice on
>> > licensing.
>> >
>> > My client needs a maximum of 10 concurrent users using an
>> > application. However, they have hundreds of employees, any
>> > one of which could be one of the 10 concurrent users.
>> >
>> > On the server side, I understand Server 2003 comes with 5
>> > CALs, so I assume
>> > I will need 5 additional CALs. But am not sure what other
>> > licenses I need.
>> >
>> > I read about roaming users, and would assume I need per user
>> > licensing for 10 roaming users, since the 10 users on any one
>> > day could log in from different departments and so different
>> > devices.
>> >
>> > Could someone clarify just what licensing I would need for
>> > this configuration.
>> >
>> > Thanks for any help you can give,
>> > Mark
 
Re: User licensing

Vera,

Yes, this is the only app that will need TS. I guess I misunderstood
roaming users. Couldn't you establish generic user logins (USER1, USER2,
etc.) that could be used by any employee from any department?

If not, we'll have to forget TS and go with a web app for this function that
can be accessed thru our Intranet. Or maybe there is someone more reasonable
in their licensing that you know of (e.g., that provides concurrent licensing
that would allow a small app lie this to be accessible to a few staff at a
time)?

Thanks again,
Mark


"Vera Noest [MVP]" wrote:

> As TP explained, that's not a valid licensing mode of TS. It's
> either per specific user, or per specific device.
> I understand that it would become very costly for your specific
> requirements, but still, it's what the EULA dictates.
>
> Is this application the *only* application that you plan to deploy
> through TS? If so, maybe TS is not the best way to deploy it. But
> if the users connect to the TS also to run other applications, they
> will need a TS CAL anyway.
> _________________________________________________________
> 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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
> 12 dec 2007 in microsoft.public.windows.terminal_services:
>
> > TP,
> >
> > There are just under 3000 employees working in just under 1000
> > departments. However, this application is small, and will
> > require no more than 10 of those 3000 people to use the
> > application at any one time, and probably more like 5 on
> > average.
> >
> > Their use would involve less than 10 minutes a day, resulting in
> > maybe 50 to 100 minutes of actual time logged in each day across
> > all departments. The login can occur at any department
> > computer, and each department has an average of 3 computers.
> >
> > We could not licensse on a per machine basis, since that would
> > require thousands of licenses and give far more capability than
> > we need. I thought we could license 10 roaming users. This
> > would allow an employee to log in to add a record to a database
> > and log out from any one of their department computers.
> >
> > Appreciate your help in explaining how this works.
> >
> > Thanks again,
> > Mark
> >
> > "TP" wrote:
> >
> >> Hi Mark,
> >>
> >> TS licensing is *not* concurrent. It is either Per Device or
> >> Per User (named employee). Licenses can be reassigned away
> >> from one device/user to another but the reassignment must be
> >> permanent *except* in the case of when you use a temporary
> >> replacement device (in the case of the primary device needing
> >> repair) or a temporary employee (in the case of a temp worker
> >> filling in while an employee is out).
> >>
> >> The same is true for Windows CALs if you choose the
> >> Per Device/Per User option for those. Other software have
> >> different licensing requirements, for example, Office is
> >> licensed Per Device.
> >>
> >> You should count up the total number of devices and employees
> >> that will be connecting and based on that choose between
> >> Per Device or Per User or a mix of the two. If you post more
> >> information regarding the number of PCs, employees, employees
> >> that need to roam, etc., I will give you more advice.
> >>
> >> Thanks.
> >>
> >> -TP
> >>
> >> Markus wrote:
> >> > I am planning to install Server 2003 and need some advice on
> >> > licensing.
> >> >
> >> > My client needs a maximum of 10 concurrent users using an
> >> > application. However, they have hundreds of employees, any
> >> > one of which could be one of the 10 concurrent users.
> >> >
> >> > On the server side, I understand Server 2003 comes with 5
> >> > CALs, so I assume
> >> > I will need 5 additional CALs. But am not sure what other
> >> > licenses I need.
> >> >
> >> > I read about roaming users, and would assume I need per user
> >> > licensing for 10 roaming users, since the 10 users on any one
> >> > day could log in from different departments and so different
> >> > devices.
> >> >
> >> > Could someone clarify just what licensing I would need for
> >> > this configuration.
> >> >
> >> > Thanks for any help you can give,
> >> > Mark
>
 
Re: User licensing

Per User licenses are per *person*, not per user account. So using
a generic account for all users is not a solution either.

Citrix licensing is per concurrent session, but since Citrix runs
on top of MS Terminal Services, that won't help you either.

Maybe you could setup a couple of (virtual?) XP clients where users
can run this application, and users connect with rdp to those XPs?
That would only cost you the licenses for the XP OS, no TS CALs.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
13 dec 2007:

> Vera,
>
> Yes, this is the only app that will need TS. I guess I
> misunderstood roaming users. Couldn't you establish generic
> user logins (USER1, USER2, etc.) that could be used by any
> employee from any department?
>
> If not, we'll have to forget TS and go with a web app for this
> function that can be accessed thru our Intranet. Or maybe there
> is someone more reasonable in their licensing that you know of
> (e.g., that provides concurrent licensing that would allow a
> small app lie this to be accessible to a few staff at a time)?
>
> Thanks again,
> Mark
>
>
> "Vera Noest [MVP]" wrote:
>
>> As TP explained, that's not a valid licensing mode of TS. It's
>> either per specific user, or per specific device.
>> I understand that it would become very costly for your specific
>> requirements, but still, it's what the EULA dictates.
>>
>> Is this application the *only* application that you plan to
>> deploy through TS? If so, maybe TS is not the best way to
>> deploy it. But if the users connect to the TS also to run other
>> applications, they will need a TS CAL anyway.
>> _________________________________________________________
>> 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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote
>> on 12 dec 2007 in microsoft.public.windows.terminal_services:
>>
>> > TP,
>> >
>> > There are just under 3000 employees working in just under
>> > 1000 departments. However, this application is small, and
>> > will require no more than 10 of those 3000 people to use the
>> > application at any one time, and probably more like 5 on
>> > average.
>> >
>> > Their use would involve less than 10 minutes a day, resulting
>> > in maybe 50 to 100 minutes of actual time logged in each day
>> > across all departments. The login can occur at any
>> > department computer, and each department has an average of 3
>> > computers.
>> >
>> > We could not licensse on a per machine basis, since that
>> > would require thousands of licenses and give far more
>> > capability than we need. I thought we could license 10
>> > roaming users. This would allow an employee to log in to add
>> > a record to a database and log out from any one of their
>> > department computers.
>> >
>> > Appreciate your help in explaining how this works.
>> >
>> > Thanks again,
>> > Mark
>> >
>> > "TP" wrote:
>> >
>> >> Hi Mark,
>> >>
>> >> TS licensing is *not* concurrent. It is either Per Device
>> >> or Per User (named employee). Licenses can be reassigned
>> >> away from one device/user to another but the reassignment
>> >> must be permanent *except* in the case of when you use a
>> >> temporary replacement device (in the case of the primary
>> >> device needing repair) or a temporary employee (in the case
>> >> of a temp worker filling in while an employee is out).
>> >>
>> >> The same is true for Windows CALs if you choose the
>> >> Per Device/Per User option for those. Other software have
>> >> different licensing requirements, for example, Office is
>> >> licensed Per Device.
>> >>
>> >> You should count up the total number of devices and
>> >> employees that will be connecting and based on that choose
>> >> between Per Device or Per User or a mix of the two. If you
>> >> post more information regarding the number of PCs,
>> >> employees, employees that need to roam, etc., I will give
>> >> you more advice.
>> >>
>> >> Thanks.
>> >>
>> >> -TP
>> >>
>> >> Markus wrote:
>> >> > I am planning to install Server 2003 and need some advice
>> >> > on licensing.
>> >> >
>> >> > My client needs a maximum of 10 concurrent users using an
>> >> > application. However, they have hundreds of employees, any
>> >> > one of which could be one of the 10 concurrent users.
>> >> >
>> >> > On the server side, I understand Server 2003 comes with 5
>> >> > CALs, so I assume
>> >> > I will need 5 additional CALs. But am not sure what other
>> >> > licenses I need.
>> >> >
>> >> > I read about roaming users, and would assume I need per
>> >> > user licensing for 10 roaming users, since the 10 users on
>> >> > any one day could log in from different departments and so
>> >> > different devices.
>> >> >
>> >> > Could someone clarify just what licensing I would need for
>> >> > this configuration.
>> >> >
>> >> > Thanks for any help you can give,
>> >> > Mark
 
Re: User licensing

Hi Vera,

Am unfamiliar with virtual XP clients. Have done a google search and will
read up on them.

Am I correct to think you could have multiple virtual XP sessions running on
a single Server 2003 machine that could be used to run the app, with up to 10
users connecting at once? My goal is to let this small group of concurrent
users run the app, but not the same individuals or same devices.

Apologies for my limited experience, and hope this question makes sense.
Mark

"Vera Noest [MVP]" wrote:

> Per User licenses are per *person*, not per user account. So using
> a generic account for all users is not a solution either.
>
> Citrix licensing is per concurrent session, but since Citrix runs
> on top of MS Terminal Services, that won't help you either.
>
> Maybe you could setup a couple of (virtual?) XP clients where users
> can run this application, and users connect with rdp to those XPs?
> That would only cost you the licenses for the XP OS, no TS CALs.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
> 13 dec 2007:
>
> > Vera,
> >
> > Yes, this is the only app that will need TS. I guess I
> > misunderstood roaming users. Couldn't you establish generic
> > user logins (USER1, USER2, etc.) that could be used by any
> > employee from any department?
> >
> > If not, we'll have to forget TS and go with a web app for this
> > function that can be accessed thru our Intranet. Or maybe there
> > is someone more reasonable in their licensing that you know of
> > (e.g., that provides concurrent licensing that would allow a
> > small app lie this to be accessible to a few staff at a time)?
> >
> > Thanks again,
> > Mark
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> As TP explained, that's not a valid licensing mode of TS. It's
> >> either per specific user, or per specific device.
> >> I understand that it would become very costly for your specific
> >> requirements, but still, it's what the EULA dictates.
> >>
> >> Is this application the *only* application that you plan to
> >> deploy through TS? If so, maybe TS is not the best way to
> >> deploy it. But if the users connect to the TS also to run other
> >> applications, they will need a TS CAL anyway.
> >> _________________________________________________________
> >> 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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote
> >> on 12 dec 2007 in microsoft.public.windows.terminal_services:
> >>
> >> > TP,
> >> >
> >> > There are just under 3000 employees working in just under
> >> > 1000 departments. However, this application is small, and
> >> > will require no more than 10 of those 3000 people to use the
> >> > application at any one time, and probably more like 5 on
> >> > average.
> >> >
> >> > Their use would involve less than 10 minutes a day, resulting
> >> > in maybe 50 to 100 minutes of actual time logged in each day
> >> > across all departments. The login can occur at any
> >> > department computer, and each department has an average of 3
> >> > computers.
> >> >
> >> > We could not licensse on a per machine basis, since that
> >> > would require thousands of licenses and give far more
> >> > capability than we need. I thought we could license 10
> >> > roaming users. This would allow an employee to log in to add
> >> > a record to a database and log out from any one of their
> >> > department computers.
> >> >
> >> > Appreciate your help in explaining how this works.
> >> >
> >> > Thanks again,
> >> > Mark
> >> >
> >> > "TP" wrote:
> >> >
> >> >> Hi Mark,
> >> >>
> >> >> TS licensing is *not* concurrent. It is either Per Device
> >> >> or Per User (named employee). Licenses can be reassigned
> >> >> away from one device/user to another but the reassignment
> >> >> must be permanent *except* in the case of when you use a
> >> >> temporary replacement device (in the case of the primary
> >> >> device needing repair) or a temporary employee (in the case
> >> >> of a temp worker filling in while an employee is out).
> >> >>
> >> >> The same is true for Windows CALs if you choose the
> >> >> Per Device/Per User option for those. Other software have
> >> >> different licensing requirements, for example, Office is
> >> >> licensed Per Device.
> >> >>
> >> >> You should count up the total number of devices and
> >> >> employees that will be connecting and based on that choose
> >> >> between Per Device or Per User or a mix of the two. If you
> >> >> post more information regarding the number of PCs,
> >> >> employees, employees that need to roam, etc., I will give
> >> >> you more advice.
> >> >>
> >> >> Thanks.
> >> >>
> >> >> -TP
> >> >>
> >> >> Markus wrote:
> >> >> > I am planning to install Server 2003 and need some advice
> >> >> > on licensing.
> >> >> >
> >> >> > My client needs a maximum of 10 concurrent users using an
> >> >> > application. However, they have hundreds of employees, any
> >> >> > one of which could be one of the 10 concurrent users.
> >> >> >
> >> >> > On the server side, I understand Server 2003 comes with 5
> >> >> > CALs, so I assume
> >> >> > I will need 5 additional CALs. But am not sure what other
> >> >> > licenses I need.
> >> >> >
> >> >> > I read about roaming users, and would assume I need per
> >> >> > user licensing for 10 roaming users, since the 10 users on
> >> >> > any one day could log in from different departments and so
> >> >> > different devices.
> >> >> >
> >> >> > Could someone clarify just what licensing I would need for
> >> >> > this configuration.
> >> >> >
> >> >> > Thanks for any help you can give,
> >> >> > Mark
>
 
Re: User licensing

What I meant was: you can run Virtual Server on a Windows 2003
server, and then inside the Virtual Server create a couple of
virtual XP clients. Then one user at a time can connect to each of
these virtual XP clients and run the software. How many virtual XP
workstations you can run on a single Virtual Server depends on the
hardware specs of the server.

Without virtualization, you could simply buy 10 workstations,
install XP and your application on them, and let users rdp into
these XP clients.
_________________________________________________________
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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
13 dec 2007 in microsoft.public.windows.terminal_services:

> Hi Vera,
>
> Am unfamiliar with virtual XP clients. Have done a google
> search and will read up on them.
>
> Am I correct to think you could have multiple virtual XP
> sessions running on a single Server 2003 machine that could be
> used to run the app, with up to 10 users connecting at once? My
> goal is to let this small group of concurrent users run the app,
> but not the same individuals or same devices.
>
> Apologies for my limited experience, and hope this question
> makes sense. Mark
>
> "Vera Noest [MVP]" wrote:
>
>> Per User licenses are per *person*, not per user account. So
>> using a generic account for all users is not a solution either.
>>
>> Citrix licensing is per concurrent session, but since Citrix
>> runs on top of MS Terminal Services, that won't help you
>> either.
>>
>> Maybe you could setup a couple of (virtual?) XP clients where
>> users can run this application, and users connect with rdp to
>> those XPs? That would only cost you the licenses for the XP OS,
>> no TS CALs.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote
>> on 13 dec 2007:
>>
>> > Vera,
>> >
>> > Yes, this is the only app that will need TS. I guess I
>> > misunderstood roaming users. Couldn't you establish generic
>> > user logins (USER1, USER2, etc.) that could be used by any
>> > employee from any department?
>> >
>> > If not, we'll have to forget TS and go with a web app for
>> > this function that can be accessed thru our Intranet. Or
>> > maybe there is someone more reasonable in their licensing
>> > that you know of (e.g., that provides concurrent licensing
>> > that would allow a small app lie this to be accessible to a
>> > few staff at a time)?
>> >
>> > Thanks again,
>> > Mark
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> As TP explained, that's not a valid licensing mode of TS.
>> >> It's either per specific user, or per specific device.
>> >> I understand that it would become very costly for your
>> >> specific requirements, but still, it's what the EULA
>> >> dictates.
>> >>
>> >> Is this application the *only* application that you plan to
>> >> deploy through TS? If so, maybe TS is not the best way to
>> >> deploy it. But if the users connect to the TS also to run
>> >> other applications, they will need a TS CAL anyway.
>> >> _________________________________________________________
>> >> 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?TWFya3Vz?= <Markus@discussions.microsoft.com>
>> >> wrote on 12 dec 2007 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > TP,
>> >> >
>> >> > There are just under 3000 employees working in just under
>> >> > 1000 departments. However, this application is small, and
>> >> > will require no more than 10 of those 3000 people to use
>> >> > the application at any one time, and probably more like 5
>> >> > on average.
>> >> >
>> >> > Their use would involve less than 10 minutes a day,
>> >> > resulting in maybe 50 to 100 minutes of actual time logged
>> >> > in each day across all departments. The login can occur
>> >> > at any department computer, and each department has an
>> >> > average of 3 computers.
>> >> >
>> >> > We could not licensse on a per machine basis, since that
>> >> > would require thousands of licenses and give far more
>> >> > capability than we need. I thought we could license 10
>> >> > roaming users. This would allow an employee to log in to
>> >> > add a record to a database and log out from any one of
>> >> > their department computers.
>> >> >
>> >> > Appreciate your help in explaining how this works.
>> >> >
>> >> > Thanks again,
>> >> > Mark
>> >> >
>> >> > "TP" wrote:
>> >> >
>> >> >> Hi Mark,
>> >> >>
>> >> >> TS licensing is *not* concurrent. It is either Per
>> >> >> Device or Per User (named employee). Licenses can be
>> >> >> reassigned away from one device/user to another but the
>> >> >> reassignment must be permanent *except* in the case of
>> >> >> when you use a temporary replacement device (in the case
>> >> >> of the primary device needing repair) or a temporary
>> >> >> employee (in the case of a temp worker filling in while
>> >> >> an employee is out).
>> >> >>
>> >> >> The same is true for Windows CALs if you choose the
>> >> >> Per Device/Per User option for those. Other software
>> >> >> have different licensing requirements, for example,
>> >> >> Office is licensed Per Device.
>> >> >>
>> >> >> You should count up the total number of devices and
>> >> >> employees that will be connecting and based on that
>> >> >> choose between Per Device or Per User or a mix of the
>> >> >> two. If you post more information regarding the number
>> >> >> of PCs, employees, employees that need to roam, etc., I
>> >> >> will give you more advice.
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> -TP
>> >> >>
>> >> >> Markus wrote:
>> >> >> > I am planning to install Server 2003 and need some
>> >> >> > advice on licensing.
>> >> >> >
>> >> >> > My client needs a maximum of 10 concurrent users using
>> >> >> > an application. However, they have hundreds of
>> >> >> > employees, any one of which could be one of the 10
>> >> >> > concurrent users.
>> >> >> >
>> >> >> > On the server side, I understand Server 2003 comes with
>> >> >> > 5 CALs, so I assume
>> >> >> > I will need 5 additional CALs. But am not sure what
>> >> >> > other licenses I need.
>> >> >> >
>> >> >> > I read about roaming users, and would assume I need per
>> >> >> > user licensing for 10 roaming users, since the 10 users
>> >> >> > on any one day could log in from different departments
>> >> >> > and so different devices.
>> >> >> >
>> >> >> > Could someone clarify just what licensing I would need
>> >> >> > for this configuration.
>> >> >> >
>> >> >> > Thanks for any help you can give,
>> >> >> > Mark
 
Re: User licensing

Thanks again Vera,

Setting up multiple XP machines would not be practical, but will have to
find out more on virtualization.

Appreciate all your help,
Mark


"Vera Noest [MVP]" wrote:

> What I meant was: you can run Virtual Server on a Windows 2003
> server, and then inside the Virtual Server create a couple of
> virtual XP clients. Then one user at a time can connect to each of
> these virtual XP clients and run the software. How many virtual XP
> workstations you can run on a single Virtual Server depends on the
> hardware specs of the server.
>
> Without virtualization, you could simply buy 10 workstations,
> install XP and your application on them, and let users rdp into
> these XP clients.
> _________________________________________________________
> 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?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on
> 13 dec 2007 in microsoft.public.windows.terminal_services:
>
> > Hi Vera,
> >
> > Am unfamiliar with virtual XP clients. Have done a google
> > search and will read up on them.
> >
> > Am I correct to think you could have multiple virtual XP
> > sessions running on a single Server 2003 machine that could be
> > used to run the app, with up to 10 users connecting at once? My
> > goal is to let this small group of concurrent users run the app,
> > but not the same individuals or same devices.
> >
> > Apologies for my limited experience, and hope this question
> > makes sense. Mark
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Per User licenses are per *person*, not per user account. So
> >> using a generic account for all users is not a solution either.
> >>
> >> Citrix licensing is per concurrent session, but since Citrix
> >> runs on top of MS Terminal Services, that won't help you
> >> either.
> >>
> >> Maybe you could setup a couple of (virtual?) XP clients where
> >> users can run this application, and users connect with rdp to
> >> those XPs? That would only cost you the licenses for the XP OS,
> >> no TS CALs.
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> =?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote
> >> on 13 dec 2007:
> >>
> >> > Vera,
> >> >
> >> > Yes, this is the only app that will need TS. I guess I
> >> > misunderstood roaming users. Couldn't you establish generic
> >> > user logins (USER1, USER2, etc.) that could be used by any
> >> > employee from any department?
> >> >
> >> > If not, we'll have to forget TS and go with a web app for
> >> > this function that can be accessed thru our Intranet. Or
> >> > maybe there is someone more reasonable in their licensing
> >> > that you know of (e.g., that provides concurrent licensing
> >> > that would allow a small app lie this to be accessible to a
> >> > few staff at a time)?
> >> >
> >> > Thanks again,
> >> > Mark
> >> >
> >> >
> >> > "Vera Noest [MVP]" wrote:
> >> >
> >> >> As TP explained, that's not a valid licensing mode of TS.
> >> >> It's either per specific user, or per specific device.
> >> >> I understand that it would become very costly for your
> >> >> specific requirements, but still, it's what the EULA
> >> >> dictates.
> >> >>
> >> >> Is this application the *only* application that you plan to
> >> >> deploy through TS? If so, maybe TS is not the best way to
> >> >> deploy it. But if the users connect to the TS also to run
> >> >> other applications, they will need a TS CAL anyway.
> >> >> _________________________________________________________
> >> >> 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?TWFya3Vz?= <Markus@discussions.microsoft.com>
> >> >> wrote on 12 dec 2007 in
> >> >> microsoft.public.windows.terminal_services:
> >> >>
> >> >> > TP,
> >> >> >
> >> >> > There are just under 3000 employees working in just under
> >> >> > 1000 departments. However, this application is small, and
> >> >> > will require no more than 10 of those 3000 people to use
> >> >> > the application at any one time, and probably more like 5
> >> >> > on average.
> >> >> >
> >> >> > Their use would involve less than 10 minutes a day,
> >> >> > resulting in maybe 50 to 100 minutes of actual time logged
> >> >> > in each day across all departments. The login can occur
> >> >> > at any department computer, and each department has an
> >> >> > average of 3 computers.
> >> >> >
> >> >> > We could not licensse on a per machine basis, since that
> >> >> > would require thousands of licenses and give far more
> >> >> > capability than we need. I thought we could license 10
> >> >> > roaming users. This would allow an employee to log in to
> >> >> > add a record to a database and log out from any one of
> >> >> > their department computers.
> >> >> >
> >> >> > Appreciate your help in explaining how this works.
> >> >> >
> >> >> > Thanks again,
> >> >> > Mark
> >> >> >
> >> >> > "TP" wrote:
> >> >> >
> >> >> >> Hi Mark,
> >> >> >>
> >> >> >> TS licensing is *not* concurrent. It is either Per
> >> >> >> Device or Per User (named employee). Licenses can be
> >> >> >> reassigned away from one device/user to another but the
> >> >> >> reassignment must be permanent *except* in the case of
> >> >> >> when you use a temporary replacement device (in the case
> >> >> >> of the primary device needing repair) or a temporary
> >> >> >> employee (in the case of a temp worker filling in while
> >> >> >> an employee is out).
> >> >> >>
> >> >> >> The same is true for Windows CALs if you choose the
> >> >> >> Per Device/Per User option for those. Other software
> >> >> >> have different licensing requirements, for example,
> >> >> >> Office is licensed Per Device.
> >> >> >>
> >> >> >> You should count up the total number of devices and
> >> >> >> employees that will be connecting and based on that
> >> >> >> choose between Per Device or Per User or a mix of the
> >> >> >> two. If you post more information regarding the number
> >> >> >> of PCs, employees, employees that need to roam, etc., I
> >> >> >> will give you more advice.
> >> >> >>
> >> >> >> Thanks.
> >> >> >>
> >> >> >> -TP
> >> >> >>
> >> >> >> Markus wrote:
> >> >> >> > I am planning to install Server 2003 and need some
> >> >> >> > advice on licensing.
> >> >> >> >
> >> >> >> > My client needs a maximum of 10 concurrent users using
> >> >> >> > an application. However, they have hundreds of
> >> >> >> > employees, any one of which could be one of the 10
> >> >> >> > concurrent users.
> >> >> >> >
> >> >> >> > On the server side, I understand Server 2003 comes with
> >> >> >> > 5 CALs, so I assume
> >> >> >> > I will need 5 additional CALs. But am not sure what
> >> >> >> > other licenses I need.
> >> >> >> >
> >> >> >> > I read about roaming users, and would assume I need per
> >> >> >> > user licensing for 10 roaming users, since the 10 users
> >> >> >> > on any one day could log in from different departments
> >> >> >> > and so different devices.
> >> >> >> >
> >> >> >> > Could someone clarify just what licensing I would need
> >> >> >> > for this configuration.
> >> >> >> >
> >> >> >> > Thanks for any help you can give,
> >> >> >> > Mark
>
 
Back
Top