From owner-freebsd-newbies Fri Oct 12 7:53:38 2001 Delivered-To: freebsd-newbies@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id A55B737B408 for ; Fri, 12 Oct 2001 07:53:34 -0700 (PDT) Received: from computer ([62.255.43.108]) by mta01-svc.ntlworld.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20011012145332.FGQA15984.mta01-svc.ntlworld.com@computer>; Fri, 12 Oct 2001 15:53:32 +0100 Message-ID: <030501c1532d$4e829920$6760ff3e@computer> From: "Kastaki" To: "Luke Boyett" Cc: References: <000201c152da$2df40700$1401a8c0@tedm.placo.com> <02ba01c15324$4e241480$6760ff3e@computer> <20011012100551.C6700@setel.com> Subject: Re: UNIX and Networking Date: Fri, 12 Oct 2001 15:50:58 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org That was the explanation I was looking for......thanks.... Effectively, we are running AD, and I would like to phase that out and move on to FreeBSD and Samba! It will not be easy, but as long as it can be done, then I can do it. I have set up a lab running Win2k and FreeBSD, and I am experimenting wih all of this..... ----- Original Message ----- From: Luke Boyett To: Kastaki Sent: Friday, October 12, 2001 3:05 PM Subject: Re: UNIX and Networking > > In any case, where will the users and groups list be - at the central server > > or at the Unix workstation or both??? > > There are a variety of options here. You can use NIS/yp or LDAP for > centrally-administered control of authentication down to the workstation > level. Both are effectively directory services like AD. As far as > controlling software installation and configuration down to the > workstation level, this is also able to be done in a multitude of > ways. X-terminals would do the trick. As would not giving 'root' > access to local workstations, thus allowing the traditional Un*x > permissions implementation to limit users to only necessary daily > tasks. Now if you're still running w/ Windows workstations, you can > use Samba to handle domain wide authentication from a Un*x machine. > To control domain-wide policies like Active Directory, there is no > Un*x substitute to manage windows clients in this manner. However, > there are a variety of options, both on the server and workstation > level that should accomplish much of what you want to do in a more > flexible and stable fashion. Just depends on how entrenched > Windows is in your organization and how much you are willing to > shake things up, depending at what level you decide to implement a > Un*x-based solutionw much you are willing to shake things up, > depending at what level you decide to implement a Un*x-based > solution. > > > > -- > Luke Boyett (Work) > Network Administrator > Southeast Telephone, Inc. > PGP Key ID = DEC7301B > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message