A Samba server is configured to use the LDAP password backend. The root DN for the LDAP directory is defined in slapd.conf. In order to define an alternative account used by the Samba administrator, w

The password for an LDAP-managed Samba administrative account does not need to match the UNIX root password; LDAP authentication is separate from local UNIX authentication.

For any account to be usable by Samba when using an LDAP backend, that account must first exist within the LDAP directory itself, including the new administrative account.

The `ldap admin` parameter in `smb.conf` specifies the Distinguished Name (DN) of the account Samba will use to bind to the LDAP server for administrative operations. It should point to the new alternative administrative account's DN, rather than the LDAP root DN, for security and privilege separation.

Mapping the administrative account to the 'domain administrator' is vague and not a distinct technical step directly involved in defining an alternative Samba administrator account for LDAP backend interaction; the critical steps are creating the LDAP entry, configuring Samba, and setting LDAP permissions.

To ensure the new administrative account has the necessary permissions to manage Samba-related objects in the LDAP directory, the access control lists (ACLs) within `slapd.conf` must be modified to grant appropriate privileges to this specific DN.