SADMS takes care of handling configuration files to achieve the the integration (joining) of Linux hosts to an ActiveDirectory domain, to the effect that

As a domain member, the Linux host

SADMS was designed for use by administrators and takes care of the gory details of configuring a Linux host as an Active Directory (Windows 200x) Domain, an operation that involves modifying a number of arcane configuration files.

The Linux host, running on Samba 3, though not an Active Directory controller, operates as a member of the domain and, as such, refers to controllers for user authentication. No local accounts for Active Directory members are needed.

Communication with Active Directory controllers is carried out through Kerberos and LDAP (not the NT LAN Manager protocols).

Optionally, PAM can be configured to accept domain users for local interactive sessions on the host, which then acts as a workstation.

SADMS takes care of:

  • configuring Kerberos
  • configuring Winbind
  • configuring Samba
  • configuring the Name Switch Service
  • optionally configuring PAM
  • synchronizing clocks
  • joining the server to the Active Directory Domain
  • making the users' homes and shares
  • making shares
  • configuring the start of the daemons
  • installing PAM modules
  • managing ACLs

SADMS requires:

  • Kerberos 5
  • Samba 3
  • Python and GTK for the GUI front-end (optional)

SADMS offers: a GUI front end:

  • Kerberos diagnosis
  • Winbind diagnostics
  • Netbios diagnostics
  • Domain diagnostics
  • Graphical User interface for managing ACLs

Target distributions are:

  • Fedora
  • Redhat
  • Mandriva
  • Debian
  • Ubuntu

Added commands: