Closed PrinceMarkieD closed 5 years ago
Thanks @PrinceMarkieD for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:
I'm closing this issue as there's nothing actionable for docs at this time.
Note: Version 1806 + hotfix or 1810 should not have this issue.
Thank you, we are on 1810 and still see the issue with the Piloting client. Maybe on 1902 we will not. we are going 1902 tonight. Thanks.
If you're still seeing the issue, please file a frown or open a case with support.
We pre-provision devices with SCCM and then enroll them in Intune manually. How can we stop ConfigMgr from making itself the MDM in the registry of a device that just completed a task sequence. The ConfigMgr client has to be scrubbed and the DeviceManageabilityCSP registry key deleted, or the enrolled devices show up as "See/ConfigMgr" in Intune, and are not manageable. We do not do co-management or hybrid join. Is there a way to stop SCCM from making itself the MDM Authority even though we have no connector setup, and no co-management.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.