07-24-2019 03:16 AM
07-24-2019 03:16 AM
I installed and configured Azure AD Connect like a few times before but now Computer objects are not synchronizing. They are included in filtering but there is not export to Azure AD, no error or warning, nothing.
Azure AD Connect Troubleshooter just saying "Object is not available in AAD Connector Space" (everything else is green/ok).
I just reinstalled it but without success.
07-24-2019 05:40 AM
When you mention Objects, do you mean
1. Objects in a specific OU not syncing
2. All Objects in your AD ?
07-24-2019 05:45 AM
07-24-2019 06:35 AM
1. Computer Account Objects - Were they syncing before
2. What version of Windows ( Windows 10 or Windows 7/8) ? Older Versions than Windows 10 are not supported.
3. Have you configured filtering to check OU of the Workstaion where your Computer Objects are residing in Local AD. Refer - https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-configure-filteri...
Refer for hybrid Identity Join - https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-managed-domains
Do let me know if it works, Pls make a note that there is a separate licensing requirement for Hybrid AD join , and if you dont wish to do a Hybrid AD join on your Workstation, there is no point or use of syncing your Workstation Objects to Azure AD via Azure AD Connect :)
07-24-2019 06:59 AM
07-24-2019 10:07 AM
If they are shown as "filtered", most likely some sync rule is to blame. Best go to the Metaverse tab, list all Device objects there and check their properties. More specifically, on the Connectors tab you should see at least two entries, and you can also run a Preview sync to get a list of all rules that play a role in the process.
07-24-2019 02:36 PM
@Patrick B Additionally, cam you confirm if in your configuration Computer Objects are selected to be Synced to Azure
To check this - Connectors < LOcal AD Connector < Right CLick < Properties < Select Object Types.
Can you confirm Computer is checked,
if it is not already your issue lies there , check and wait for next sync to finish.
07-25-2019 12:42 AM
07-25-2019 10:51 AM
I mean generic "filtered", but setting the cloudFiltered attribute is one of the ways this can happen, yes. You can see the rule that's setting this value, so check if any modifications have been made to it, and why it fires on those objects.
08-05-2019 03:29 AMSolution
I resolved it by configuring proxy-exceptions :)
The reason for not synchronizing the computer-objects was that the computers were not able to contact Azure AD connection-points what is necessary to change attributes (usercertificate) so that Azure AD Connect will synchronize it to AAD.