Forum Discussion
AAD COnnect object not in metaverse
- Dec 25, 2019
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?
It can simply be filtered by one of the default (or custom) rules. You should see which of those affect the object when you run the preview/commit. And do force a Full sync as some changes might not be reflected upon delta.
VasilMichev When I click Generate Preview...all it says is successful. Then I click on the source object details...it shows whole bunch of stuff on the "NEW VALUE" column and "OLD VALUE" is empty...which is to be expected since this is not syncing yet. And that's all I see...I don't see rules or anything
- VasilMichevDec 19, 2019MVP
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
- ch0wd0wnDec 25, 2019Copper Contributor
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?
- ch0wd0wnDec 25, 2019Copper ContributorTurns out this account was the BUILT-IN Administrator account that has been renamed!!!!!
- ch0wd0wnDec 25, 2019Copper ContributorHi Vasil
Also in the article it is stating the following -
"Go to the CS Import attribute list and check which filter is blocking the object from moving to the MV. The Connector Space attribute list will show only non-null and non-empty attributes. For example, if isCriticalSystemObject doesn't show up in the list, the value of this attribute is null or empty."
But I click on the link to the CS Import page and it still doesn't show HOW TO LOOK for which filter is blocking... it just goes into explaining the import and lineage tabs. Sorry I am just not getting this.
Can you just tell me where exactly would it show what is blocking this object from being in the MV? - ch0wd0wnDec 25, 2019Copper ContributorGosh 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.