http://bugzilla.opensuse.org/show_bug.cgi?id=1014367 Bug ID: 1014367 Summary: network:samba:STABLE/samba: Bug:lack of AD Domain Controller feature Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: OBS Request Assignee: jmcdonough@suse.com Reporter: j.peter0123@gmail.com QA Contact: adrian@suse.com Found By: --- Blocker: --- Created attachment 705459 --> http://bugzilla.opensuse.org/attachment.cgi?id=705459&action=edit systemd journal and samba status (partial and full Samba4 versions) The official openSUSE Samba4 updates (not just in leap 42.1 and 42.2), and the Samba4 on the installation media are lacking of the Active Directory Domain Controller role feature. The components needed for Samba to act as an AD DC, are completely excluded from the build, it is a lesser version compared to the official Samba ( samba.org ). This Samba4 server can just be set up as an NT Domain Controller, which is obsolete and it is unsupported by newer Windows clients. The latest Windows client was Win 7, what included support of joining NT domains after a registry modification, newer clients doesn’t support this. Because of this, it is beyond possibility to set up any openSUSE based Samba server as domain controller for not antiquated Windows clients. (Many educational institutes are using openSUSE based Samba domain controller servers, but just few of them are using archaic Windows clients.) If the Samba4 server is manually configured as an AD DC, it can’t start-up. After fixing the Badlock Bug ( http://badlock.org/ ), the compatibility with NT of newer Windows clients are almost gone. Compiling Samba myself is an option for home, but not for full OSS based educational servers, they should get official updates with full functionality. And these partial Samba packages are also limiting the usability of openSUSE in certain environments. Missing components are the “samba.service”, “samba-tool” and many symbols from shared objects. Optionally it should contain a Yast samba-server module for the Samba4 configuration (now this module can only generate configurations for Samba3). I tried instead of the officially Samba packages one of the spins repositories: http://download.opensuse.org/repositories/spins:/invis:/testing:/samba-ad/ this is fully functional, it contains every component to act as an AD DC, it’s only and biggest problem is, the it has an unresolvable conflict with the openldap2 package. With this setup the Windows clients can join the domain, but the LDAP users are gone. -- You are receiving this mail because: You are on the CC list for the bug.