Re: Licensing.
- From: "kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 20 Jul 2008 01:59:08 -0700
Gregg Hill wrote:
MS once had a doc on line (maybe still does) that showed that SBS is a
"per-seat" licensing model rather than a "per-server" model, which is
why SBS CALs cover access to all Windows servers in the domain. The
"per-seat" model is broken down into "per-user" or "per-device" CALs
for SBS, and maybe even for standard Windows 2003 domains. I'm too
tired to look it up right now!
In a standard 2003 domain (non-SBS), if one has "per-seat" licensing,
then all Windows servers in the domain are covered. Buy 30 CALs, set
them up as "per-seat" licensing mode, and 30 people and/or devices(?)
get coverage to an unlimited number of servers, the same as in
SBS-land.
Gregg Hill
It's pretty straightforward as MS licensing goes. But as always, the best
answer come from the authoritative source (MS).
Q. Do additional servers in my SBS 2003 R2 network require a CAL to
connect to the domain?
A. You do not need a CAL for additional servers to connect to the
domain.
http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:A761A871-B9CF-4E1F-B2A1-A9D6A69ABE88@xxxxxxxxxxxxxxxx
I believe he is asking not about SBS but Windows Server 2003
Standard. I believe he would do well to ask such questions of other than
SBS
users. Short story. SBS CALs differ from 'standard CALs'. Standard CAL
requirements are dependent on 'per server' or 'per user/device'.
SBS _cannot_ answer the question.
"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23JW5vaR6IHA.3684@xxxxxxxxxxxxxxxxxxxxxxx
techjohnny@xxxxxxxxx wrote:
On Jul 18, 1:04 pm, "kj [SBS MVP]" <KevinJ....@xxxxxxxxxxxxxxxxxx>
wrote:
techjoh...@xxxxxxxxx wrote:
On Jul 18, 12:52 pm, "kj [SBS MVP]"
<KevinJ....@xxxxxxxxxxxxxxxxxx> wrote:
techjoh...@xxxxxxxxx wrote:
Do I need to purchase an additional 50-licenses to connect to
an application running on a "member server?" I realized this
is a SBS group, but it's just a licensing question.
Application running on member server authenticates people
through a SBS Domain Controller. Since the users need to
connect to say, port 8350, they still need a license for both
the domain controller and the member server?
So is it correct to say that the user needs a license for both
machines, and not just the domain controller?
Thanks,
--tj
No. One SBS CAL fits all of the above (and more).
--
/kj
OK., so the user can access the Exchange server on the domain
controller and connected to the application running on the member
server with one license?
Yes. An SBS CAL covers any number of Windows Servers (* Windows
2008 -> read the fine print). Access to the "Application" itself
may have additional provisions. What is the "application"?
--
/kj
Would this apply to a Windows 2003 domain controller with member
servers?
--tj
Any Windows servers that are members of the SBS domain are covered
by the SBS CALS. Additional servers with SQL, Exchange, and other
products may be covered by the R2 expanded CAL rights. But for just
Windows services and otherwise provided by third party
applications, no additional Microsoft licensing is required.
(The one noted exception is with 2008 after May of 2009.)
--
/kj
--
/kj
.
- Follow-Ups:
- Re: Licensing.
- From: Gregg Hill
- Re: Licensing.
- References:
- Licensing.
- From: techjohnny@xxxxxxxxx
- Re: Licensing.
- From: kj [SBS MVP]
- Re: Licensing.
- From: techjohnny@xxxxxxxxx
- Re: Licensing.
- From: kj [SBS MVP]
- Re: Licensing.
- From: techjohnny@xxxxxxxxx
- Re: Licensing.
- From: kj [SBS MVP]
- Re: Licensing.
- From: SuperGumby [SBS MVP]
- Re: Licensing.
- From: Gregg Hill
- Licensing.
- Prev by Date: Re: Licensing.
- Next by Date: Re: Licensing.
- Previous by thread: Re: Licensing.
- Next by thread: Re: Licensing.
- Index(es):
Relevant Pages
|
