At my office there's talk of moving from a "WorkGroup" currently
hosted
through samba to a Domain, possibly hosted through samba. Anyone got a
definitive "why we should or should not rip out the existing, working
workgroup to put in a domain?"
:wq!
---------------------------------------------------------------------------
Robert L. Harris | PGP Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Diagnosis: witzelsucht
IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net http://www.rdlg.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/20030508/eb89a9bf/attachment.bin
Robert, Please share with us WHY? What are you hoping to achive? For the record, I run only domain architecture. The reasons are being documented in the new Samba-HOWTO-Collection - which is still being developed. You can check it out from: http://samba.org/~jht/NT4migration/Samba-HOWTO-Collection.pdf You would need to read the chapter on Domain Control and the one on Domain Membership. - John T. -- John H Terpstra Email: jht@samba.org -------------- next part -------------- Skipped content of type multipart/signed-------------- next part -------------- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Robert L. Harris wrote:>At my office there's talk of moving from a "WorkGroup" currently hosted >through samba to a Domain, possibly hosted through samba. Anyone got a >definitive "why we should or should not rip out the existing, working >workgroup to put in a domain?" > > >Pro-- Centralized account management. If you change your password on the workgroup, you may have to change your password on every computer in order to regain access to shares. Pro-- greater security-- often people leave shares wide open on workgroups in order to avoid proiblems regarding password authentication. Domains solve this problems. Con: Centralized point fo failure. If tyhe domain controllers are down, your network is down. Period. Fortunately that is what a BDC is for. Best Wishes, Chris Travers, MCSE, MCSA, LPIC-2