Re: Terminal Server Licensing issues on a SBS 2003 Domain

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Eugene Tan (insights-[dropthis)
Date: 09/25/04 

Date: Sun, 26 Sep 2004 00:46:24 +0800

hi AS,

I read thru the various posts and suspect that the question has not been
really answered, either that or my understanding of your question is
different
from the other replies. So that as you need it here:

SBS is the root of the ActiveDirectory. SBS CALs enable logging in to the
SBS domain which includes additional services (whether installed or not);
besides Win2k3 authentication and File/Print services, you also get Exchange
email services, and for SBS-Prm you also get SQL and ISA services and the
right to use for client PCs.

The key point to note is, devices will login to SBS domain. The Windows
server (2k3 or 2k) is part of the SBS domain, and this will consume 1 CAL,
since it also authenticates with SBS as a member of the domain. All other
devices logging onto this domain will require a CAL, regardless of where
the application actually runs (on Windows server or a client PC). The only
exception is when accessing webserver (LAN or WAN) without doing any
authentication.

PCs accessing thru a TerminalSvr will require TS CALs in addition to SBS
CALs. They require the SBS CALs since a/m login to SBS domain. Using
TS services to login as TS client will require a TS CAL each. So from your
numbers this is 20 TS Win2k3 CALs and 20 SBS CALs, and if all the other
users also login to the same domain this is another 40 SBS CALs. All in
still
cheaper than CoreCAL licenses or probably cheaper than individual server
CALs (it will require at least 60 Windows CALs - same principle of logon
to which domain).

SBS2k3 CALs distinguish between user and device CALs and it is possible
to mix and match but you have to track it. However I don't think the server
actually has a mechanism to distinguish, but I'm not sure.

As for concurrency of CALs aka perServer vs perSeat mode, I thought I
read somewhere that this applies still when all the CALs are device CALs
but I am not very sure for SBS2k3. Esp. since both device and user CALs
exist which allows very specific tailoring. In SBS2k, perServer mode is
permitted.

ok, I re-read your question abt the TS users logging on locally to TS
server:
I haven't actually implemented yet so don't know, but I don't think it is
possible
to login to WinTS itself as local domain except in remote admin mode.
If possible, then you don't even need Windows CALs, since this is needed
only for the Windows domain, not for local login. I suspect we are
confusing
local accounts with TS logins. The moment one logs into a domain then
SBS CALs apply since the TS server is in SBS domain.

HTH,
Eugene Tan

============================
"AS" <as@home> wrote in message
news:eV1jjpynEHA.3464@tk2msftngp13.phx.gbl...
> Hi,
> We are thinking about installing a Terminal Server (Windows 2003) as a
> member server in a Small Business Server 2003 network. I just need to get
> my
> head around the licensing required, from my understanding they will need
> (For 20 users) 20 X Windows 2003 CALS to access the database on the
> server,
> 20 X Terminal Server CALS to run TS and 20 X SBS 2003 CALS to log onto
> the
> domain? Now if that is true it will take them very close (sometimes above)
> the SBS 2003 Max of 75 users. On a Terminal Server running as a member
> server is it possible to select "Log on to: This Machine" at the login
> prompt? This would mean that as long as the users have local accounts and
> everything they need to access is on the TS server they do not need to log
> onto the SBS box (right?). 1 or 2 of the users will need to access some
> files on the SBS box and they can be accomodated with the SBS 2003
> licences.
>
> Am I thinking along the right path ?
>
> Thanks,
>
>

Relevant Pages

  • Re: SBS2003 with Server 2008 Terminal Services
    ... Customers running SBS 2003 R2 can use their CALs to access additional servers running Windows Server 2003, Exchange Server 2003 and SQL Server 2005 Workgroup Edition on the SBS 2003 R2 network. ... See the licensing questions section for additional information on SBS 2003 R2 CALs. ... Remote Web Workplace rather than VPN. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... so that means that I do not need any CALS for the ... Chris> Using up the SBS CALS is something that I want to avoid as it will ... Justin> Are you trying to say that if a user logs onto the terminal server ... The reason I want to make it a member server is because some users will need ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... so that means that I do not need any CALS for the ... Chris> Using up the SBS CALS is something that I want to avoid as it will ... Justin> Are you trying to say that if a user logs onto the terminal server ... The reason I want to make it a member server is because some users will need ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SBS2003 - Transition Pack
    ... If you were under your current purchased CALs, ... If it still says it's SBS, ... Once the transition is complete, ... Server 2003 Standard Edition and Exchange Server 2003 Standard. ...
    (microsoft.public.windows.server.sbs)
  • Re: Licence reset in SBS 2003
    ... I understand that the CALs often disappear on SBS ... Microsoft CSS Online Newsgroup Support ... >> We are maintenaing few SBS 2003 server and sometime we lose all our ...
    (microsoft.public.windows.server.sbs)