From: "Geo." 

It's not the unauthenticated, it's customers with a username/password so
they can maintain their websites. Every frontpage user requires a user
license, right now that's not true for ftp based websites.

You don't need user licenses for anonymous browsers.

Geo.

"Ellen K."  wrote
in message news:51o3905efgd2k07eilmgl32sg0qqqj096c{at}4ax.com...
> Sure, for you, not having to count unauthenticated web users is a huge
> deal.   We do have an official company website on the public internet
> but I think it's just kinda there, although we do get a few leads from
> it.   Many employees access their company email from home over the web,
> but that's authenticated... (although I don't know if it counts as being
> authenticated by Windows since it's the GroupWise authentication...)
>
> It turns out we have 320 W2K CALs and 60 2003 ones, which means nobody
> bought any more CALs in recent months as additional employees who use my
> recordings database were hired.  ( I have about 430 users on that one.)
> So we have to get enough to cover the 50-or-so new ones on that one,
> plus additional ones for users who will be using the new databases but
> don't currently use the recordings one.   I think we should have some
> procedure in place where we take a census or something like once a month
> and if more users were hired than left, buy new licenses then, don't let
> it go longer than a month.
>
> On Thu, 29 Apr 2004 20:02:41 -0400, "Geo."
 wrote in
> message :
>
> >"Rich"  wrote in message news:409097a5$1{at}w3.nls.net...
> >>>   See
>
>http://www.microsoft.com/windowsserver2003/howtobuy/licensing/caloverview.m
spx
> >for a description of CALs for Windows Server 2003.<<
> >
> >Thanks for the pointer Rich.
> >
> >Ellen, this is the change in client licensing I was talking about with my
> >ftp server example:
> >
> >Client access licensing requirements have been updated for Windows Server
> >2003. In previous Windows Server licensing models, Windows CALs were
> >automatically triggered when particular server services were invoked
(such
> >as file, print, remote access, and terminal services, as well as
> >authenticated access).
> >
> >With Windows Server 2003, CALs are no longer triggered based on the use
of
> >certain services but are instead based on access to and/or use of the
server
> >software. This holds true for all editions of Windows Server 2003, except
> >Web Edition. Windows CALs are not required for Web Edition.
> >
> >Note the following general exception to Windows CAL requirements: Windows
> >CALs are not required when access to the server software is
unauthenticated
> >and conducted through the Internet. Authenticated access is defined as an
> >exchange of user or application credentials between the server software
and
> >a user or device. An example of this exception would be if unidentified
> >users browsed your public Web site. Windows CALs would not be required
for
> >those users.
> >============
> >
> >Don't know if that would effect you but for us it's a huge difference
> >between 2000 and 2003.
> >
> >Geo.
> >
>

--- BBBS/NT v4.01 Flag-5