[Samba] Samba as AD-Controller: unable to update policies and call start scripts

Rowland penny rpenny at samba.org
Fri Apr 8 06:50:31 UTC 2016

On 08/04/16 06:18, Luca Bertoncello wrote:
> Rowland penny <rpenny at samba.org> schrieb:
>> I think you will find this is the sharepath of the sysvol directory on
>> the DC, i.e. on a self compiled Samba it will be:
>> [sysvol]
>>           path = /usr/local/samba/var/locks/sysvol
>>           read only = No
>> What I think you are un-aware of is, the sysvol dir is not synced
>> between DCs, so your sysvol on your second DC may only contain the
>> default GPOs, see here for more info:
> I just have ONE DC...

Sorry, mis-read what you wrote, I thought you were trying to join another DC

> Any other idea?
> Maybe is it possible that my tries with Samba as AD (this is my first
> installation of Samba 4 as AD controller) damages the AD-data?

Well if it works for one PC and not another, it is probably a problem 
with the second PC.

> How can I drop all and restart without reinstalling the Server?

You could try restarting Samba on the DC as a first step. If that 
doesn't work, you will need to backup the required files, Samba comes 
with a script to do this 'samba-backup' though you may have to alter the 
paths in it.
You could then re-install Samba and re-install your backup.

It may help if you could tell us how you installed Samba, did you follow 
a webpage and if so which one ?

> Thanks
> Luca Bertoncello
> (lucabert at lucabert.de)

More information about the samba mailing list