search for: cc727302

...t; LDAP://CN=Machine,cn={E2BC0255-64C8-42CF-A27A-59A7D3DCD2DC},cn > =policies,cn= > system,DC=my,DC=example,DC=com. Group Policy settings will > not be resolved until this event is resolved. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc727302(v=ws.10)?redirectedfrom=MSDN So here they say, delete and recreate, i dont think thats needed.. I think your solution is in this link. https://docs.microsoft.com/nl-nl/troubleshoot/windows-server/group-policy/permissions-this-gpo-inconsistent > > After running sysvolreset the systems up...

...ok, well, reboot the compter after the join, 2 times. After 1st reboot clear all logs, you will see things quicker. And not all policies are applied when your logged in. > > > > https://docs.microsoft.com/en-us/previous-versions/windows/it- > pro/windows-server-2008-R2-and-2008/cc727302(v=ws.10)?redirect > edfrom=MSDN > > So here they say, delete and recreate, i dont think thats needed.. > Just sysvolreset was all that was needed, if it was corrupt then > changing the perms shouldn't matter. > > > I think your solution is in this link. > > >...

> It's needed after every GPO addition and edit. There must be a root > cause to hunt down somewhere. Or is it a bug in 4.13.0 ? Yes, and no. Yes, its a bug. No, in my opionion its an old setting thats just needs some updating. Try this. samba-tool ntacl set "O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01