Bug 11880 - Can't write on the sysvol directory
Summary: Can't write on the sysvol directory
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: x64 Linux
: P5 major (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-29 16:10 UTC by Jefzo
Modified: 2022-02-04 16:21 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jefzo 2016-04-29 16:10:41 UTC 
Hello All,

I'm new user of samba (intership project)
I have to migrate windows server 2003 AD to samba 4.
I meet some issues can't resolved by myself.

First Issue :

If I join samba 4.4.2 to the old DC with a user in the group BUILTIN\administrators who joined well, after joined and start samba I can't write on the sysvol directory. I have to use for join to the old DC, the user BUILTIN\administrator who is also in the group BUILTIN\administrators... And if I do that I can write and fix the acl by add administrators group via the Microsoft Windows Management.



Second Issue :

As I join with Bind_DLZ.
Samba_dlz do not configured all writable zone existing !
Google research say its because it's a zone generate by server Wins.
But I can't fix it



Sorry for my English
And thank you in advance for your help

Jeff
Comment 1 Björn Jacke 2022-02-04 16:21:25 UTC 
Sorry for the delayed reply. First of all reporting 2 different problems in one bug report is not a good idea. Each bug report should contain a single problem with a detailed description and if possible a descriptions how to reproduce the problem.
Apart of that, for now, what you describe doesn't really look like bugs. I suggest you discuss your issues on the samba mailing list and ask for help there. If it turns out that there is actually a bug, then you should file a detailed bug report for that.