Re: Terminal Server Licensing issues on a SBS 2003 Domain

From: AS (as_at_home)
Date: 09/23/04 

Date: Thu, 23 Sep 2004 23:57:04 +0100

Thanks for the replys, so that means that I do not need any CALS for the
Windows 2003 member server and the 75 SBS CALS will cover all users to
connect to all servers ?

Chris > Using up the SBS CALS is something that I want to avoid as it will
take them over the 75 user limit.

Justin> Are you trying to say that if a user logs onto the terminal server
with a domain account from the SBS box it dosen't use up an SBS CAL as long
as they don't open up a connection to the SBS box (Outlook, mapped drive
etc?)

The reason I want to make it a member server is because some users will need
resources on the SBS box so my plan is to have 10-12 users logging on
locally to the TS to run a local application and the other 3 users logging
on to the domain to access the sbs box, this should keep them within the 75
user limit (which is 75 concurrent users BTW).

Thanks,

AS

"justin" <justin.nospam@nospam.logicalfusion.com.au> wrote in message
news:u2j0rWQoEHA.596@TK2MSFTNGP11.phx.gbl...
I agree with Chris on the 20 CALs for Windows 2003 box. Member servers in an
SBS 2003 domain are covered by the CALs on the SBS box. To put it simply, if
an SBS 2003 server has 10 CALs on it, any member server has 10 CALs. Think
of it like this: the CALs are cloned & given to the member server when the
member server joins.

Now, in your case, if the TS users aren't using any resources on the SBS
server (Outlook to the Exchange server, connecting to a folder share on the
SBS machine, etc), then they won't add to the number of used CALs on the SBS
2003 box. The 75 user maximum - does that mean you can only add 75 users, or
you can only have 75 concurrent connections (using 75 CALs)? That would be
my first test - adding a 76th user. On SBS 4.5 it was 50 users with a
maximum of 25 concurrent connections.

You'll probably just have to do some tests. Logging on locally would be the
same as not making it a member server - you would have to dulicate
everybody's credentials on the TS machine (what a pain) , you would need the
20 Windows 2003 CAL's, but as you wouldn't be using the SBS 2003 server, you
wouldn't need the extra SBS CALs. Have a go without buying the extra SBS or
Windows 2003 CALs (just getting the Terminal Services CALs). Join the server
to the domain (it will immediately pick up the same number of CALs the SBS
server has) & see how you go.

Good luck. There's always the Transition Pack.

Justin

"CRIS HANNA (SBS-MVP)" <crishannanospam@computingpossibilities.net> wrote in
message news:%23AG$TEznEHA.3520@TK2MSFTNGP15.phx.gbl...
They will not need cals for the Windows 2003 server, since its joining the
domain, the SBS 2003 cals cover it, or so that is my understanding

You will need the TS cals those and the TS cals have no relationship to the
SBS Cals per se 

-- 
Cris Hanna (SBS-MVP)
_____________________
Please only respond in the Newsgroup and not directly to me, so that
everyone can share the information
"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
    ... Each additional server also consumes one cal. ... you're down to a max of 71 users, SBS does not itself consume a CAL. ... SBS2003 CALs are not 'concurrent connection', a CAL is a label, user cals ... > The reason I want to make it a member server is because some users will ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... Each additional server also consumes one cal. ... you're down to a max of 71 users, SBS does not itself consume a CAL. ... SBS2003 CALs are not 'concurrent connection', a CAL is a label, user cals ... > The reason I want to make it a member server is because some users will ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Licensing Question -adding WK3 Server
    ... I understand how you feel abt getting 5 CALs when you only need one. ... required for each member server. ... then a CAL is required because a member server ... would be a device that access the SBS directly or indirectly - by being ...
    (microsoft.public.windows.server.sbs)
Loading