That is the response I got back from our Univeristy's license
purchaser after she contacted the schools Microsoft Rep.
"...whether you need to buy extra CALs for Windows Server depends on
whether or not those users would be authenticated by the system or
not. If they have to identify themselves when they use the server,then
yes, they need CALs. The next question is whether they are employees
or students. If they are accessing the server from inside the
university or if they are other faculty or school employees, they will
each need a CAL. If, on the other hand, they are students, trading
partners, or customers of some sort accessing the server from outside
the school, then they could all be covered by a Windows External
I wish Microsoft would simplify there licensing agreements, because
for a small group that is not use to licensing it is very confusing
and easy to make a mistake.
> Hey Jason,
> The best thing to do is to contact your local Microsoft rep and have
> them explain what needs to happen. We just went through this whole nut
> roll, and we still don't have it right, because we listened to someone that
> "thought" they knew how it all worked. It's so danged complicated now that
> you can't just look at a chart and figure it out. The bottom line answer
> is, any unauthenticated user can access the database no problem on a per
> processor machine, with Win2K3, but any user that connects needs to have a
> CAL. Atleast that's my understanding.
> Don R. Watters
> Data Group Manager
> PhotoWorks, Inc.
> > Hello All,
> > I am putting together a budget to migrate our databases to SQL Server
> > 2000. We will have about 500 internal users and 1000's of web users.
> > We will be purchasing the SQL Per Processor License, but my question
> > is since the SQL Server will be on a new Windows 2003 server do we
> > have to buy Windows 2003 CALS for every potential SQL user?
> > Thanks for your help,
> > Jason