Hi Andreas, Both Debian and Ubuntu like to install services with a working default > configuration, and it is expected that a service is running after it is > installed. That's why winbind is started right after it is installed. I have three concerns with apt interfering with services- - systems theory suggests package and service managers have different functions. - Mission critical systems design expects this. - The pillar of Reactive Systems theory demands *non-blocking* communication between subsystems - no polling! The expectation "a service is running after it is installed" is not in question - it is principle of least surprise. I dislike fact apt is moving into user space daemon management space. If a user space daemon fails - who cares! If a system management technology breaks - everyone cares - it is a devastating event. Regarding the specific Bug I will gather the information you requested. Here the context is an Infrastructure-as-code ( https://github.com/saltstack-formulas/samba-formula) installation which is heavily automated but joining the domain, for security reasons, is not automated. Please let me know if anything jumps out. I will try to retest when I get time. thanks Noel -- --- ... automate dns ... automate chrony ... automate nss ... automate kerberos ... etc.. apt install -y samba systemctl start samba cp smb.conf.custom /etc/samba/smb.conf systemctl start samba apt-get install -y samba-client apt install -y samba-winbind apt install -y libpam-winbind smbldap-tools cifs-utils cp winbind.conf.custom /etc/samba/winbind.conf systemctl start winbind *fails on 16.04 but I have control and package manager is not broken* systemctl start nmb systemctl start samba systemctl start nmb systemctl start winbind *never works* --- --- net ads join EXAMPLE.COM -U domainadmin kinit -k HOST\$@EXAMPLE.COM systemctl restart winbind *always works* --- --- automate Active Directory pam/nss automate Citrix Linux VDA --- --- On Thu, Mar 7, 2019 at 8:20 PM Andreas Hasenack