Event banner
Windows Office Hours: June 15, 2023
Event Ended
Thursday, Jun 15, 2023, 08:00 AM PDTEvent details
Get answers to your questions about adopting Windows 11 and managing the Windows devices used by remote, onsite, and hybrid workers across your organization. Get tips on keeping devices up to date ef...
Heather_Poulsen
Updated Jun 15, 2023
jnardiello
Jun 15, 2023Copper Contributor
We are currently evaluating Windows 11 for deployment but have a CMG related question. We have had internet-based client management (IBCM) in place for several years, and currently have co-managed devices with MECM/Intune.
To assist in our ROI evaluation to move to CMG, can you provide any information as it pertains to the following?
1. Co-managed endpoints with IBCM (Current State) - i.e., enhanced policy configuration
2. Cloud-native endpoints in Intune (Future State)
SteveThomas
Microsoft
Jun 15, 2023With relation to costs, we've laid out all of the cost factors in this reference here: https://learn.microsoft.com/en-us/mem/configmgr/core/clients/manage/cmg/cost
- and Danny lays out some of the ROI with CMG and tenant Attach here: aka.ms/bigthree I would love for you to bring this question to the next episode of Unpacking Endpoint Management as we will be discussing this very topic. aka.ms/UEM
- Jason_SandysJun 15, 2023
Microsoft
Co-management is unrelated to either IBCM or the CMG so there's not much to provide there. Co-management is about dual management of device using both Intune and ConfigMgr in a coordinated fashion. Co-management is *not* about remote management of devices. While this is certainly provided by Intune, with co-management and remote devices, you still need IBCM or CMG to enable ConfigMgr management of those devices. You also must choose whether you use ConfigMgr or Intune for configuration as having both of them attempt to apply configuration would be painful at best. As for cloud native endpoints, we wrote a great set of docs on this subject: https://aka.ms/cloudnativeendpoints.