Forum Discussion
MECM co-management enrollment not working
yannick_sierro Yes, it's solved.
All co-management policies were duplicated in the SCCM database. And the client received the corrupted policies.
The cause is that the first time we tried to activate the cloud attach, the operation did not complete due to lack of permissions on azure. Some uncomplete policies were left in the database.
We removed the cloud attach, deleted policies from the DB with help of the escalation engineer and recreated the cloud attach.
The cause is that the first time we tried to activate the cloud attach, the operation did not complete due to lack of permissions on azure. Some uncomplete policies were left in the database.
Next week, we will work with the escalation engineer again to remove the cloud attach, delete policies from the DB and recreate the cloud attach.
Where in the SCCM Database were you seeing if the policies were duplicated?
I would like to check to see if this is the same scenario we are facing.
Thanks,
David
- we would like to see in client devices which is Co-Management is enabled
please help me on this.
if you want i will send co-management handler logs in CCM setup also i will send to you - Hello @Le Michel can you please help me regarding the below problem please
1. We want to run our infra on Co-Manage (Intune and SCCM) Hybrid model.
2. Currently Microsoft Entra Joined and Microsoft Entra Registered Workgroup devices successfully enrolled in Intune and we can manage the device compliance, Windows updates and remote deployment of Managed Apps successfully.
3. Challenge with On-Prem Active Directory registered devices not enrolled in Intune, but those devices showing in Intune dashboard managed by Config Mgr (SCCM) instead of Co-managed.
4. In ConfigMgr systems --> control panel --> Configuration Manager Properties --> Co-Management option shows Disabled. Below images are for your reference. - I recommend opening a MS case to solve this. I would not make changes in the configmgr database without guidance from MS.
- Hi,
I am having the same problem.
Can you explain how did you delete the policies from the DB?
Thanks yannick_sierro Yes, it's solved.
All co-management policies were duplicated in the SCCM database. And the client received the corrupted policies.
The cause is that the first time we tried to activate the cloud attach, the operation did not complete due to lack of permissions on azure. Some uncomplete policies were left in the database.
We removed the cloud attach, deleted policies from the DB with help of the escalation engineer and recreated the cloud attach.- Hi,
are you problem resolved? what needed to be done? I've the same problem as you seems to have.
Kind regards
