When upgrading from Samba 2 to Samba 3, which of the following points should be considered when user information is stored in a LDAP server? (Select TWO correct answers.)

Running the Samba 3 server before its LDAP configuration is complete can lead to the server initializing with a local backend, causing inconsistencies or data loss when later attempting to switch to the intended LDAP backend.

While password encryption methods changed in Samba 3, converting *all* passwords in LDAP is not always a mandatory initial step before running the server; Samba 3 can often be configured to handle older hashes or integrate with existing LDAP schema without an immediate mass conversion.

Setting the Samba 3 domain SID to match the Samba 2 domain SID using the `net setlocalsid` command is essential to ensure that existing clients and trusts from the Samba 2 domain continue to function seamlessly with the upgraded Samba 3 server.

Dumping and restoring all data files from Samba 2 to fix ACLs is generally not the correct or primary approach for migrating user information specifically stored in an LDAP server, as ACLs are usually associated with file shares and not directly managed by LDAP for user accounts.

Changing file permissions to match group permissions is a general file management task and not a specific, critical consideration unique to upgrading Samba's LDAP-backed user information from version 2 to 3.