[Samba] samba 4.4 gpupdate /force

[Carlos A. P. Cunha]

Cool, how good it was my tip useful, your problem and mine should be the 
same.

Goodbye

Em 29-03-2016 12:51, barış tombul escreveu:
> my problem solved :) Fix the  ""samba-tool ntacl sysvolreset""
>  Thank you very much to everyone...
>
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
>
> C:\Users\btombul>gpupdate /force
> Updating Policy...
>
> User Policy update has completed successfully.
> Computer Policy update has completed successfully.
>
>
> C:\Users\btombul>
>
> 2016-03-29 17:15 GMT+03:00 Carlos A. P. Cunha <carlos.hollow at gmail.com 
> <mailto:carlos.hollow at gmail.com>>:
>
>     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
>
>
>
>