I've reread the documentation of the smbldap-useradd command and found, that the behaviour I reported as a bug is intentional, since sambaSamAccount is normally added by samba when the machine is joined to the domain.
My problem araises only when someone wants to migrate a machine account from another server or authentication backend (tdb or smbpasswd). I modify my suggestion according to my recent findings: Update the documentation of smbldap-useradd with the following sentence: "When migrating an existing machine account, you also have to invoke smbldap-useradd -a computername$ after creating the account in order to allow storing of encrypted password into the sambaNTPassword entry." Or something similar. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
