samba - Mar 2016 - samba 4.4 gpupdate /force

Hello everyone!
Whenever replicate the Sysvol need to run the DC command that received 
the data

/opt/samba/bin/samba-tool ntacl sysvolreset

This solves the problem (at least in min).



Em 29-03-2016 08:28, mathias dufresne escreveu:
> Check rights on sysvol (using samba-tool), check rsync process if several
> DC.
>
> 2016-03-29 13:07 GMT+02:00 barış tombul <bbtombul at gmail.com>:
>
>> command prompt >> run as administrator
>>
>> Microsoft Windows [Version 6.1.7601]
>> Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
>>
>> C:\Users\btombul>gpupdate /force
>> Updating Policy...
>>
>> User policy could not be updated successfully. The following errors
were
>> encount
>> ered:
>>
>> The processing of Group Policy failed. Windows could not apply the
>> registry-base
>> d policy settings for the Group Policy object
>> LDAP://CN=User,CN={31B2F340-016D-1
>> 1D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=facility,DC=local.
Group
>> Policy
>> settings will not be resolved until this event is resolved. View the
event
>> detai
>> ls for more information on the file name and path that caused the
failure.
>> The following warnings were encountered during user policy processing:
>>
>> Windows failed to apply the Scripts settings. Scripts settings might
have
>> its ow
>> n log file. Please click on the "More information" link.
>> Computer policy could not be updated successfully. The following errors
>> were enc
>> ountered:
>>
>> The processing of Group Policy failed. Windows could not apply the
>> registry-base
>> d policy settings for the Group Policy object
>> LDAP://CN=Machine,CN={31B2F340-016
>> D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=facility,DC=local.
Group
>> Poli
>> cy settings will not be resolved until this event is resolved. View the
>> event de
>> tails for more information on the file name and path that caused the
>> failure.
>> The following warnings were encountered during computer policy
processing:
>>
>> Windows failed to apply the Scripts settings. Scripts settings might
have
>> its ow
>> n log file. Please click on the "More information" link.
>>
>> To diagnose the failure, review the event log or run GPRESULT /H
>> GPReport.html f
>> rom the command line to access information about Group Policy results.
>>
>> C:\Users\btombul>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>

On Tue, 29 Mar 2016, Carlos A. P. Cunha wrote:
> Hello everyone!
> Whenever replicate the Sysvol need to run the DC command that received the 
> data
>
> /opt/samba/bin/samba-tool ntacl sysvolreset
>
> This solves the problem (at least in min).
I believe the proper fix is to make sure all your DCs have the same GID 
mappings.  See:

https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups

...though this claims it should not be necessary after 4.2?  Also note 
that the rsync -XAa options are important when replicating sysvol:

https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround

Really my user IDs are different, but I can not adjust it.
Using Samba 4.3.3 (Upgrade from 4.2 -> 4.3 -> 4.3.3), I think it has 
something it was initially used with Windows 2003 (no longer usaddo) to 
replicate data
Win 2003 -> Samba.
Today only own Samba (which had to increase Schema)

Em 29-03-2016 10:27, Sketch escreveu:
> On Tue, 29 Mar 2016, Carlos A. P. Cunha wrote:
>
>> Hello everyone!
>> Whenever replicate the Sysvol need to run the DC command that 
>> received the data
>>
>> /opt/samba/bin/samba-tool ntacl sysvolreset
>>
>> This solves the problem (at least in min).
>
> I believe the proper fix is to make sure all your DCs have the same 
> GID mappings.  See:
>
>
https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory#GID_mappings_of_built-in_groups
>
>
> ...though this claims it should not be necessary after 4.2?  Also note 
> that the rsync -XAa options are important when replicating sysvol:
>
> https://wiki.samba.org/index.php/Rsync_based_SysVol_replication_workaround 
>