Forum Discussion

ch0wd0wn's avatar
ch0wd0wn
Copper Contributor
Dec 18, 2019

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 NOT found in the metaverse search

4. User has correct UPN suffix

5. in the CS I'm able to bring up the properties of the user and generated a full sync preview and even committed it successfully.

 

So when I force a delta sync... I see nothing at all … no new object add or changes in the logs... 

 

I looked at this article but can't really understand regarding the scoping filters.  Everything is default, there should be no filters.

 

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-object-not-syncing

 

Please help with some more detailed troubleshooting?  Seems like this user is being skipped for some weird reason....

 

  • ch0wd0wn's avatar
    ch0wd0wn
    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?

Resources