Re: How does Licensing Work by kj
kj
Wed Apr 30 10:46:23 PDT 2008
Griff5w wrote:
> On Apr 30, 1:17 pm, "AllenM" <nore...@NoEmail.com> wrote:
>> You either need User CAL's or Device CAL's. Basically you need a
>> license for every user and or device that "authenticates" to your
>> domain.
>>
>> "Griff5w" <grif...@gmail.com> wrote in message
>>
>> news:60b74692-7ace-4a11-9cc6-4c053f6b84a1@2g2000hsn.googlegroups.com...
>>
>>> I am curious about how the licensing works.
>>
>>> I have a server that is running Windows Server 2003 and MSSql Server
>>> 2000. We have five user machines running XP. If I understand
>>> correctly, Win2003 and MSSql come with 5 Client licenses. What if I
>>> need to add another user? We don't use Active Directory are
>>> anything like that. We are only using the server to host the
>>> database that our application connects to.
>>
>>> So, if I need to add a sixth user, do I need more licenses for Win
>>> 2003 AND MSSql?
>>
>>> And what about Terminal Services? I am thinking maybe of moving our
>>> users over to Linux/Mac computers and having them access that one
>>> application via TS. How does that work in regards to licenses? And
>>> do I really need to setup another Windows 2003 machine to host the
>>> TS License Server?????
>>
>>> Thanks.
>>> Griff
>
> I am not using Domains. It is just a simple Workgroup. The server
> exists solely to run MSSql which hosts the data for an application
> that we run. All other network tasks (printing, file shares, email,
> etc) are handled on Linux. Unfortunately we have this one application
> that we must use only hosts data in MSSql.
>
> So, for the sixth user to use the application and have it get the data
> in MSSql, we have to buy another CAL for both Win2003 AND MSSql??
>
> Now, if I decide to use Terminal Services for the users to run that
> application, do I still need a CAL for Win2003 and MSSql for EACH
> User? Plus TS Licenses?
Still need a user or device license for windows (domain or not - doesn't
matter).
SQL *may* be licensed "Per Processor" and if so, you needn't a sperate CAL
for that. You need to look at your SQL license.
TS licensing is yet another need if you go that way.
--
/kj