Sure, hope my smb.conf is helpful:
[global] workgroup = CORP realm = CORP.EXAMPLE.COM netbios name = SERVERNAME server role = active directory domain controller dns forwarder = 192.168.0.1 guest account = nobody load printers = no printing = bsd printcap name = /dev/null disable spoolss = yes panic action = /bin/sleep 99999999 [netlogon] path = /usr/local/samba/var/locks/sysvol/corp.example.com/scripts read only = No [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [homes] path = /home/CORP read only = No browseable = No [dropbox] path = /srv/samba/dropbox read only = No browseable = Yes create mask = 664 directory mask = 775 guest ok = Yes On Sat, May 25, 2013 at 12:08 PM, Ulrich Schneider <m...@ulrichschneider.de>wrote: > Could you please post your smb.conf? > That would be great. > Thanks > > Am 25.05.13 16:29, schrieb Nick Semenkovich: > >> Not sure about documentation -- is there a particular feature you're >> looking for? >> >> >> I've been running Samba4 as an AD DC for a few months now with ~20 >> Windows 8 clients & users. >> >> Minus one big issue (crashing bug 9822 which was patched quickly), >> it's been incredibly stable and easy to use. >> >> Samba4 is running with mapped home directories & lots of group >> policies, perfectly fine. >> >> >> >> The only issues I have are relatively minor. They're: >> >> * A few rare crashes in smbd, which I see every week or two. >> ** >> https://bugzilla.samba.org/**show_bug.cgi?id=9853<https://bugzilla.samba.org/show_bug.cgi?id=9853> >> ** >> https://bugzilla.samba.org/**show_bug.cgi?id=9873<https://bugzilla.samba.org/show_bug.cgi?id=9873> >> Though these sound bad, they just crash one thread. The clients seem >> to work fine (worst case, one client will stall during a user logon, >> but is fine after restarting the client). >> >> * DNS updates w/ DHCP-assigned IPs don't work: >> ** >> https://bugzilla.samba.org/**show_bug.cgi?id=9559<https://bugzilla.samba.org/show_bug.cgi?id=9559> >> Looks like this is being worked on now. >> >> * Winbind crashes a lot: >> ** Repeatable crashes with ls -lha: >> https://bugzilla.samba.org/**show_bug.cgi?id=9820<https://bugzilla.samba.org/show_bug.cgi?id=9820> >> ** Repeatable crashes with getfacl: >> https://bugzilla.samba.org/**show_bug.cgi?id=9842<https://bugzilla.samba.org/show_bug.cgi?id=9842> >> >> * Samba has a few random errors in the log, which I'm not sure how to >> interpret >> ** Failed to modify SPNs: https://bugzilla.samba.org/** >> show_bug.cgi?id=9848 <https://bugzilla.samba.org/show_bug.cgi?id=9848> >> >> All those issues are pretty rare or minor. >> >> Samba4 has been working great as an AD DC! Plus, the dev team is super >> responsive if you have a real, significant bug. >> >> >> - Nick >> >> >> >> On Sat, May 25, 2013 at 9:09 AM, Ulrich Schneider >> <m...@ulrichschneider.de> wrote: >> >>> Hi everybody, >>> >>> I read about the development state ... samba as an ad domain controller >>> and >>> that many functions / group policies have been implemented. Still, there >>> is >>> some work in progress. >>> >>> Is there a documentation where I can look up the functions not >>> implemented >>> yet? >>> >>> Regards, >>> Ulrich Schneider >>> -- >>> To unsubscribe from this list go to the following URL and read the >>> instructions: >>> https://lists.samba.org/**mailman/options/samba<https://lists.samba.org/mailman/options/samba> >>> >> >> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba