Tech Community Live: Endpoint Manager edition
Jul 21 2022, 08:00 AM - 12:00 PM (PDT)

Co-Management and Compliance

%3CLINGO-SUB%20id%3D%22lingo-sub-2657508%22%20slang%3D%22en-US%22%3ECo-Management%20and%20Compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2657508%22%20slang%3D%22en-US%22%3E%3CP%3EHi!%20I%20installed%20Endpoint%20Config%20Manager%20mainly%20to%20practice%20for%20the%20Modern%20Desktop%20cert%20and%20also%20to%20give%20try%20out%20Device%20Analytics.%3C%2FP%3E%3CP%3EDuring%20my%20configuration%2C%20I%20noticed%20one%20of%20my%20Intune%20windows%20VMs%20was%20marked%20under%20%3CSTRONG%3ECompliance%3C%2FSTRONG%3E%20as%20%22Co-Managed%22%20and%20CfgManager%20as%20the%20compliance%20source%2C%20even%20before%20completing%20the%20co-management%20config%2C%20I%20assumed%20I%20may%20have%20made%20a%20mistake%20in%20the%20configuration%20order%2Fsteps%20and%20didnt%20give%20it%20much%20thought.%3C%2FP%3E%3CP%3ENow%20afer%20taking%20my%20test%2C%20I%20am%20trying%20to%20put%20that%20machine%20back%20into%20Intune%20management%20but%20for%20nothing%20under%20the%20influence%20of%20the%20mighty%20Providence%20I%20can%20manage%20to%20make%20that%20machine%20to%20report%20compliance%20by%20Intune.%3C%2FP%3E%3CP%3EI%20have%20tried%3A%26nbsp%3B%3C%2FP%3E%3CP%3E-%20removing%20the%20machine%20from%20the%20Co-Management%20scoped%20collection%3C%2FP%3E%3CP%3E-%20manually%20uninstalling%20the%20SCCM%20client%3C%2FP%3E%3CP%3E-%20Manually%20removing%20the%20management%20authority%20registry%20key%3C%2FP%3E%3CP%3E-%20Reconfiguring%20the%20management%20scope%20in%20ConfigMgr%20to%20intune%20for%20all%20workloads%3C%2FP%3E%3CP%3E-%20other%20even%20more%20esoteric%20stuff%20that%20I%20dont%20even%20remember%20now%3C%2FP%3E%3CP%3EAny%20ideas%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2657508%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%20current%20branch%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%20and%20Compliance%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2783925%22%20slang%3D%22en-US%22%3ERe%3A%20Co-Management%20and%20Compliance%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2783925%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3EYou%20can%20try%20this%20%3A%3CBR%20%2F%3E1.%20Unenroll%20the%20machine%20from%20Intune%3CBR%20%2F%3E2.%20Remove%20the%20machine%20from%20scope%20in%20ConfigMgr%3CBR%20%2F%3E3.%20Uninstall%20ConfigMgr%20agent%3CBR%20%2F%3E4%20Re-enroll%20in%20Intune%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi! I installed Endpoint Config Manager mainly to practice for the Modern Desktop cert and also to give try out Device Analytics.

During my configuration, I noticed one of my Intune windows VMs was marked under Compliance as "Co-Managed" and CfgManager as the compliance source, even before completing the co-management config, I assumed I may have made a mistake in the configuration order/steps and didnt give it much thought.

Now afer taking my test, I am trying to put that machine back into Intune management but for nothing under the influence of the mighty Providence I can manage to make that machine to report compliance by Intune.

I have tried: 

- removing the machine from the Co-Management scoped collection

- manually uninstalling the SCCM client

- Manually removing the management authority registry key

- Reconfiguring the management scope in ConfigMgr to intune for all workloads

- other even more esoteric stuff that I dont even remember now

Any ideas?

2 Replies
Hi,
You can try this :
1. Unenroll the machine from Intune
2. Remove the machine from scope in ConfigMgr
3. Uninstall ConfigMgr agent
4 Re-enroll in Intune