LFCS · Question #662
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.)
The correct answer is A. Never run the Samba 3 server before the configuration to use the LDAP server is complete. C. Set the domain SID of Samba 3 to the same value of Samba 2 with the net setlocalsid command. When upgrading Samba 2 to Samba 3 with LDAP for user information, it's critical to configure the Samba 3 server for LDAP before running it and to maintain the same domain SID as Samba 2 for compatibility.
Question
Options
- ANever run the Samba 3 server before the configuration to use the LDAP server is complete.
- BConvert all passwords in the LDAP server to the new encryption method.
- CSet the domain SID of Samba 3 to the same value of Samba 2 with the net setlocalsid command.
- DDump all data files created by Samba 2, and restore them with Samba 3 to fix the ACLs.
- EChange the permissions of the files created by Samba 2 to match the group permissions in Samba 3.
How the community answered
(55 responses)- A76% (42)
- B4% (2)
- D13% (7)
- E7% (4)
Why each option
When upgrading Samba 2 to Samba 3 with LDAP for user information, it's critical to configure the Samba 3 server for LDAP before running it and to maintain the same domain SID as Samba 2 for compatibility.
It is essential to fully configure Samba 3 to use the LDAP server before starting the service to prevent inconsistencies or the creation of local user information that would conflict with the LDAP backend.
Samba 3 often supports backward compatibility for password encryption methods used by Samba 2, and a full conversion of all passwords in LDAP is not always a mandatory or primary consideration during the initial upgrade.
Setting the Samba 3 domain SID to match the Samba 2 value using `net setlocalsid` is crucial for preserving domain trust relationships and ensuring clients do not need to rejoin the domain.
While data migration is part of an upgrade, simply dumping and restoring data files is not the direct method for fixing ACLs in the context of an LDAP backend upgrade, which typically handles user and group mapping differently.
Changing file permissions to match group permissions is a generic administrative task, not a specific, primary consideration for an LDAP-backed Samba 2 to Samba 3 upgrade, as permissions are managed via the OS and Samba's user/group mapping to LDAP.
Concept tested: Samba server upgrade considerations with LDAP backend
Source: https://www.samba.org/samba/docs/old/Samba3-HOWTO/upgrading.html
Topics
Community Discussion
No community discussion yet for this question.