Tenant Attach Issue “Not able to perform Sync actions/Greyed out” Co-managed devices

Question

Tenant attach 1 - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Tenant Attach Issue "Not able to perform Sync actions/Greyed out" Co-managed devices Tenant attach error - HTMD Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Tenant Attach Issue "Not able to perform Sync actions/Greyed out" Co-managed devices

I have successfully configured Tenant attach, but having trouble under devices which are co-managed.

  1. Onboarded all the devices to Microsoft Endpoint Manager admin center through tenant attach.
  2. Device which is co-managed, under which I am not able to perform tenant attach actions like sync policy etc. Those options are greyed out and seeing this when I move the cursor on those ” Device is blocked or unapproved in Microsoft Endpoint Configuration Manager”
  3. Not able to see client details options on co-managed devices.
  4. Devices which are not co-managed and managed by Configmgr. I can see the sync and client details information and can perform policy sync and other actions.

Did I miss anything, why is the tenant attach features are not showing under co-managed devices and other sync actions.

Appreciate your help. Thanks.

 

in progress 0
Kirankr31 2022-04-15T21:18:22+05:30 1 Answer 23 views Beginner 0

Answer ( 1 )

  1. I think I have seen this behavior with co-managed devices in my lab 1 year back or something. I just checked the co-managed device now and I see the same behavior as yours.

    https://www.anoopcnair.com/what-is-new-in-sccm-cloud-attach-tenant-attach/

    But one other device shows all the client actions enabled from Intune portal.

    The only difference I could see is client shows as ACTIVE in the SCCM console and it’s installed with the 2203 client version. But I don’t think this is anything to do with the SCCM client version.

    I think it’s worth doing some more digging on your side to understand the exact issue.

    SCCM Tenant Attach Troubleshooting Issues via Logs | ConfigMgr https://www.anoopcnair.com/sccm-tenant-attach-troubleshooting-issues-via-logs-configmgr/

Leave an answer

Sorry, you do not have a permission to answer to this question .