LX0-104 · Question #588
When migrating files from a Windows server A to a Samba server B with the command 'net rpc share migrate files -S A -destination=B -acls -attrs -U administrator', some files that originally belong onl
The correct answer is C. force unknown acl user = yes. The force unknown acl user = yes option in smb.conf resolves migration errors for files with ACLs assigned only to Windows groups by mapping unresolvable Windows SIDs to a valid Unix identity.
Question
Options
- Ause acl = yes
- Bmap group acls = yes
- Cforce unknown acl user = yes
- Dinherit acls = no
How the community answered
(31 responses)- A13% (4)
- B10% (3)
- C74% (23)
- D3% (1)
Why each option
The `force unknown acl user = yes` option in `smb.conf` resolves migration errors for files with ACLs assigned only to Windows groups by mapping unresolvable Windows SIDs to a valid Unix identity.
`use acl = yes` enables general ACL support but does not specifically address the issue of mapping *unknown* Windows SIDs to Unix identities during file migration.
`map group acls = yes` is not a standard Samba parameter used for this specific problem; other ACL-related parameters exist but not this exact one.
The `force unknown acl user = yes` parameter in `smb.conf` is specifically designed to handle scenarios where Windows ACLs contain SIDs (Security Identifiers) that do not have a corresponding Unix user or group mapping. Setting this to `yes` forces Samba to map these unknown SIDs to a default or valid Unix identity, preventing errors during migration.
`inherit acls = no` controls whether newly created files or directories inherit ACLs from their parent, which is unrelated to resolving unmapped SIDs during a file migration.
Concept tested: Samba ACL migration unknown SIDs
Source: https://www.samba.org/samba/docs/current/manpages/smb.conf.5.html
Topics
Community Discussion
No community discussion yet for this question.