i enabled co-management for few test machines but now we want to use intune only and dont require co-management anymore.
can i just right click and delete the co-management from sccm or do ineed to follow any additional steps?
Delete co-management
As far as ConfigMgr itself goes, yes, that's it. You need to also remove the ConfigMgr agent from the managed systems as well. Keep in mind that you'll be losing all of the advanced capabilities of ConfigMgr that do not exist in the Intune.
Thanks Jason. Can you please list few of major advanced capabilities of ConfigMgr as client only wants to keep Intune solution.
Also, if i delete the Co-Management from SCCM, is it mandatory to reinstall the SCCM client on those machines.
Hi,
As client only wants to keep Intune solution, it will be unable to deploy Windows OS and hardly to manager Windows Server. Based on my experience, SCCM works best for on-prem infrastructures.
If you still want to manager the devices with SCCM after removing Co-Management, yes, you need to install SCCM client agent. If not, it's no need to install SCCM client agent any more.
Thanks for your time.
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
If you still want to manager the devices with SCCM after removing Co-Management, yes, you need to install SCCM client agent. If not, it's no need to install SCCM client agent any more.
You can't manage a system with both ConfigMgr and Intune without Co-management enabled and configured so the question doesn't make sense.
There are many features and functions in ConfigMgr that don't exist in Intune; e.g., operating system deployment, third-party updates, software metering, customizable inventory, full software inventory, CMPivot, and on-prem (non-peer based) content caching to name just a few. That's in no way to say that Intune can't or shouldn't be used, just that if they are used to the full functionality of ConfigMgr, they may be losing something going to Intune only. This may or may not be something that will impact them.
As for reinstalling the ConfigMgr agent, I don't understand the question. Why would you reinstall it? I thought the intent was to remove co-management and move to Intune which means also removing the device from ConfigMgr management and thus removing the ConfigMgr agent.
Hi,
Just checking in to see if there is any update. May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks and regards,
Simon
What if I want to disable co-management and revert back to Config Manager as the management tool/authority? I added few machines in pilot collection and enabled Software Deployment workload on that collection. Now I have removed all except 1 devices from this collection, but still those machines are showing "Co-managed" in intune.
Correct. There is no defined or designed path for this to my knowledge. Unenrolling the device from Intune is what is needed here and simply removing the client from the collection won't do this. I don't know of a way to automatically unenroll Windows devices from Intune; manual is the only way I know of (other than retiring or wiping them from the console which has other ramifications.
You could also just move all of the workload sliders to ConfigMgr. This isn't exactly the same, but effectively, it is nearly the same.
What's the scenario here?
Yes, this is the scenario and I haven't yet tried unenrolling the device from intune. I will give it a shot:
Unenroll device from intune.
Remove machine from Co-Management pilot collection (already done)
re-enroll device into intune (for conditional access).
Yes, this is the scenario
What is the scenario? IOW, why is this needed/wanted?
Also, why would you do the above instead of just removing the ConfigMgr agent?
3 people are following this question.
