Share via

CloudSync Issue

Matt Dillon 1,211 Reputation points
2022-11-09T14:58:05.743+00:00

So I recently converted my environment to a co-managed environment. I have a collection in SCCM with 20 laptops that are my test group for patching each month. As I am ready to flip the workload switch to Intune for patching, I wanted to use the same collections I have in SCCM as the Intune patching groups. I enabled CloudSync for the patching collection to go to group in AAD. It works great except I have a single PC that will sync to the AAD side no matter what I do. Things I have tried include:

  • Manually uninstalling the SCCM client and using Client Push to reinstall.
  • Created a new Collection in SCCM and a new Group in AAD. Same PC refuses to sync.
  • Deleted the laptop from SCCM, did a system discovery, and let it clean itself up.

All the CollectionAADGroupSyncWorker.log tells me is this: Error occurred: 'Resource 'ed636368-0aa9-41dc-ae14-53a31776349e' does not exist or one of its queried reference-property objects are not present.' in request 0

Not sure what the next steps are except to delete from Intune and AAD completely and start over. Laptop is overseas so I really do not want to do that. Thoughts or path to try?

Microsoft Configuration Manager

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Simon Ren-MSFT 32,221 Reputation points Microsoft Vendor
    2022-11-10T08:44:49.913+00:00

    Hi,

    Here are some good troubleshooting guides for your reference:
    Troubleshooting: Endpoint Configuration Manager Device Collection Membership Synchronization
    Troubleshooting ConfigMgr Enhanced HTTP and Azure Directory Group Sync
    (Please Note: Since the website is not hosted by Microsoft, just for your reference.)

    Thanks for your time. Have a nice day!

    Best regards,
    Simon

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments