This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 80%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Hello,
We currently installed Azure AD Sync connect and everything seems to be synching well except for a 8344 "Insufficient access rights to perform the operation". We did a custom install where it only syncs a specific OU / group.
-We are doing only PW Hash Synchronization
-Users are getting their pws synced for the few that we are doing, pw changes, take effect too,
-During AD Forest account we selected create a new ad account
-We used users are represented only once across all directories
-Let azure manage the source anchor was selected
Again all the passwords are synching good but when I open Synchronization service manager I get the above error. When I click on the user error I see it has a change under "ms-ds-consistencyGuid" which I believe is the change it is having issue writing back to our active directory. Is there an easy way to fix this?
EDIT:
Finally it is fixed! After I started checking the security permissions for the root domain I noticed the OU for our users didn't have the security permissions for the MSOL service account at all.
The users OU had inheritance disabled. After I enabled inheritance for that particular OU, the permissions instantly appeared for the service account and the problem was fixed.
Did you also give the AADConnect account:
Replicate Directory Changes
Replicate Directory Changes All
at the root for the Password Hash Sync requirement?
If you add the account to Domain Admins as a test, I assume it works yes?
I did the command and unfortunately still having the permission issue. I'm not sure what else to try.
Do you see the account and permissions it has via ADUC?
and by that I mean , if you open up ADUC and look at the security tab, do you see the account and the permissions it has in the forest?
Per that article:
Allow AD DS Connector Account Read/Write property Descendant User objects
If not, you can always add manually at the forest/domain/OU root and give it those permissions.
Make sure you arent blocking inheritance at the OU level as well.
Also, lets go back to your command above that you say wasn't working:
Try this:
Line by Line in Powershell
this is the account that will be used by Azure AD Connect Sync to manage objects in the directory.
$accountName = "DOMAINNAME\USERNAME"
$ForestDN = "DC=DOMAINNAME,DC=com"
$cmd = "dsacls '$ForestDN' /I:S /G '`"$accountName`":WP;ms-ds-consistencyGuid;user'"
Invoke-Expression $cmd
Yes I can see the security permissions it has on the forest.
I was also able to add the write permission using powershell successfully but still having the permission issue.
-I also reset the MSOL_ pw and reinstalled the client to match the new pw.
-The Microsoft Azure AD Sync service was changed to logon as the MSOL_ service account
-Added the MSOL_ account locally to administrators group and ADSyncAdmins where AD connect is installed.
-Temporarily turned off windows firewall to test
After all those changes I still keep getting the permission issue when its trying to export back to our AD and add the ms-ds-consistencyguid attribute.
Yes that account has Replicate directory changes and replicate directory changes all. I don't understand the part about "At the root of Password Hash Sync requirement"?
Yes if I add the service account to domain admin it will clear the permission errors.
Root meaning "Forest Root"
Ok, so that is good then. At least we know its's working and the perms are really the issue.
So no blocked inheritance on any OU or any account itself? If you create a new account, does the problem continue or if you give the AADConnect account specific permissions on an AD Account?
Is this a single domain forest?