Re: silly questions about CALs

Sorry should have added that the users can login remotely from a physical
aspect just not from a licensing aspect...;-)


"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:OaD%23$Sf8GHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
Hi

You can have as many users as you wish (created)

Device CALS are the pcs so if 10 PCs and you physically nominated your
CALS as devices then it doesn't matter howmany users you have they can all
loginto these 10 PCs.

However, this scenario does not allow anyone to login remotely.

If a user logins in remotely then this is now a USER CAL. Only that user
can login to their pc at the office (they can also login to any other pc).

Your other 19 users can only use the other 9pcs.

Does this help a bit?




"Dhow" <Dhow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20123694-B557-4636-8906-A9C437DC20C3@xxxxxxxxxxxxxxxx
Hi,
I still want to ask about CALs in Win SBS 2003 R2:
If I choose Device CALs for all of the CALs installed in Win SBS 2003 R2,
is
that means I'm only legally allowed to connect the computer devices
instead
of user accounts?
For example:
There are 10 Device CALs installed in Win SBS 2003 R2, and there are 10
workstation computers in our company; where there are 20 people will use
those 10 workstation computers.
So I make 10 computer devices in Add Computers (through Server Management
console), because they are Device CALs after all. I'm not legally allowed
to
create user profiles in Add Users (also through Server Management
console)?
Or, I'm elligible to make 20 user profiles for those 20 employees that
will
access the workstation computers. And automatically I add 20 computer
devices
also in the process?
Or, I make only 10 user profiles and 10 computer devices?

Which one is true? Or is there another legal explanation on using Device
CALs?
Thank you for all of your help.




.

Relevant Pages

  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... SBS is the root of the ActiveDirectory. ... The key point to note is, devices will login to SBS domain. ... server is part of the SBS domain, and this will consume 1 CAL, ... PCs accessing thru a TerminalSvr will require TS CALs in addition to SBS ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... SBS is the root of the ActiveDirectory. ... The key point to note is, devices will login to SBS domain. ... server is part of the SBS domain, and this will consume 1 CAL, ... PCs accessing thru a TerminalSvr will require TS CALs in addition to SBS ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Windows 2003 server terminal serveur licensing
    ... Yes, also a login by an Administrator takes up a license, since ... "Application mode" on a Windows 2003 server). ... To complicate matters, Per User TS CALs are currently unmanaged, ... >> in Windows Server 2003 Terminal Services ...
    (microsoft.public.win2000.termserv.clients)
  • Re: silly questions about CALs
    ... Device CALS are the pcs so if 10 PCs and you physically nominated your CALS ... this scenario does not allow anyone to login remotely. ... create user profiles in Add Users (also through Server Management ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... The immediate answer is buy the sbscals need and then buy the ts cals. ... any device or user that consumes services from sbs require cals. ... > the application actually runs (on Windows server or a client PC). ... They require the SBS CALs since a/m login to SBS domain. ...
    (microsoft.public.windows.terminal_services)