Forum Discussion
MECM co-management enrollment not working
- Jan 09, 2023
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.
are you problem resolved? what needed to be done? I've the same problem as you seems to have.
Kind regards
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.
- David AlexanderApr 15, 2024Copper Contributor
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
- Le_MichelMar 29, 2023Brass ContributorI recommend opening a MS case to solve this. I would not make changes in the configmgr database without guidance from MS.
- Ricardo_MouraMar 28, 2023Copper ContributorHi,
I am having the same problem.
Can you explain how did you delete the policies from the DB?
Thanks