NT PDC licensing
teilo at cdt.luth.se
Wed Dec 12 09:35:04 GMT 2001
Probably not, acording to
IANAL and havn't read the full NT licence aggreement
*CALs are Required *
Windows NT 4.0 Server can be used for any of the following, in which
CALs are required:
(*Note:* that some of these functions are "basic" and will be a common
use of Windows NT Server, while others are more specialized and thus
will be less common)
* File Services--i.e. accessing or managing files on the network.
* Printing Services--i.e. sharing and managing printers on the network.
* Macintosh connectivity--file sharing and/or printing sharing.
* Remote Access Services--i.e. accessing a server from a remote
location through a communications link, including the use of
Internet Connection Services.
* Message Queue Server--i.e. sending or receiving messages from
Message Queue Server.
* Transaction Server--invoking component-based applications managed
by Transaction Server.
* Terminal Server Functionality--using Windows NT Server to display
or use Windows-based or Windows NT-based applications on a device.
No mention of Authenticating users here... But you must not share any
files from them.
Adam Killian wrote:
>I was wondering if anyone has any experience with Micorosft's licensing policy wrt samba.
>I want to use an NT PDC and some BDCs to do my username/password authentication, and use Samba for all my file/print servers. Obviously, I will need licenses for each NT server, but if all I am doing with it is authenticating users, do I need a CAL for each user? This is going to be a 2500 user installation, so it makes a big difference to the total cost. If I do end up needing CALS, I will have to use some other authentication mechanism.
>As I understand it, I can configure Samba to act as a PDC, but not as a BDC. Since this will be a mutli-site deployment, that won't work. I guess that leaves me with NIS or LDAP. Does anyone have any reccomendations/suggestions/horror stories?
>akillian at footlocker.com
Technology is a word that describes something that doesn't work yet.
More information about the samba-ntdom