Forum Discussion
AAD COnnect object not in metaverse
I have AAD Connect running and cannot sync this one user. Here are some facts 1. User is in an OU that's configured to Sync 2. User is found in the Connector Space for on prem AD 3. User is NO...
VasilMichev Thanks for the article.
I'm really trying to follow this but the verbiage is confusing:
" In the following scoping filter, if the isCriticalSystemObject value is null or FALSE or empty, it's in scope."When I look at the "In from AD - User Join" and the scoping filter shows isCriticalSystemObject has a value of "TRUE" … so according to the statement above this rule is NOT in scope? the double negative is confusing me, also because User Join sounds like its something that SHOULD be in scope right?
Check the documentation for more guidance, including screenshots: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-object-not-syncing#connector-space-object-properties
Gosh sorry to keep bugging you just wanted to give you an update...
I found that this user object has isCriticalSystemObject set to "TRUE" which after reading 1000s I understand that because of this, he's not being sync'd. Conversely I looked at this attribute for other syncing users and its "NOT SET". So I am sure I found the issue... however I'm unable to modify this due to some SAM error, that may be another issue.
I found that this user object has isCriticalSystemObject set to "TRUE" which after reading 1000s I understand that because of this, he's not being sync'd. Conversely I looked at this attribute for other syncing users and its "NOT SET". So I am sure I found the issue... however I'm unable to modify this due to some SAM error, that may be another issue.
