[cifs-protocol] Group Policy questions
hongweis at microsoft.com
Fri Oct 16 16:46:25 MDT 2009
After testing, I think that I have some information to help you resolve all the problems.
As described in the following link (http://support.microsoft.com/default.aspx?scid=kb;en-us;828760 ) , GPMO will check the consistency between ACLs in GPO in Active Directory and ACLs of policy folders in SYSVOL when a GPO object is clicked in GPMC. The logic is something like the following:
1. Get the security descriptor (SD) for GOP in AD and folders in SYSVOL
2. Check both security descriptors to make sure they are DACL protected (PD bit in Control flag is set). If not, ACL consistency check will fail.
3. For every permission in AD DACL, there should be the same permission in SYSVOL DACL. If all permissions have be checked through in AD ACL and there is still extra permission in SYSVOL ACL, ACLs are not consistent.
Looking at the your attached SSDL of the new policy, it doesn't have PD bit set. (D:PAI means DI bit is set, which is not DACL protected). This will fail the second step of consistency checking.
In GPMO, if the attribute sDRightsEffective of selected GPO object has DACL_SECURITY_INFORMATION bit (0x04) set, users will be prompted for ACL correction if ACLs inconsistency between AD GPO and SYSVOL is detected when a GPO node is selected. You should check the attribute for the GOP object in AD.
This is basically the same logic as in (2). The "Add" and "Remove" buttons in Delegation dialog are enabled only when the attribute sDRightsEffective of selected GPO object has DACL_SECURITY_INFORMATION (0x04) bit set. You should check the attribute for the GOP object in AD.
By the way, you can follow the instruction in this link (http://technet.microsoft.com/en-us/library/cc737379(WS.10).aspx ) to enable GPMC logging, if you want to troubleshoot the issues related to operations in GPMC. For example, the logging will show you in which step the consistency checking fails.
You can look for the text "CGPMGPO::IsAclConsistent()" in the logs generated.
If you need more information, please let us know.
From: Matthieu Patou [mailto:mat+Informatique.Samba at matws.net]
Sent: Sunday, October 11, 2009 6:28 AM
To: Interoperability Documentation Help; pfif at tridgell.net; cifs-protocol at samba.org
Subject: Group Policy questions
We are facing some problems with group policies and I would like to have
more information on the following points.
Currently Samba is not able to set correctly acl on policy folders so
that they are "synchronized" with the acl for the policy object in the AD.
So every time a policy is selected in gpmc.msc we receive the message
indicating that the ACL are not in sync ....
1) What is the algorithm to transform the AD ACL for Group Policy Object
into the ACL for the associated files in \\realm\sysvol ? Lot of us
tried different things without success
2) If I modify the ACL of a the Policy directory on a w2k3 DC, I am
offered with the to opportunity to correct this when I select the GPO in
gpmc. On a S4 server it's not the case but I the ACL for the policy
object are the SAME in S4 and in w2k3 and I am testing with the domain
administrator (ie. default administrator with rid 500). It seems that
the it's not only the SID or the group membership that trigger the right
to adjust the ACL. What can influence one or the other behavior ?
3) In the delegation tab of the GPMC tool I am just offered the
"advanced" button other are grayed (no possiblity to add or remove a
delegation ... I click "advanced" it appear that I can't do much even if
the owner of the object is "Domain admins" and that the Administrator is
a member of it. It seems that there is also here a subtle logic. Can you
explain it ?
For your information the SDDL of the acl of a new policy is the
More information about the cifs-protocol