We’re just over a month away from Microsoft dropping support for hybrid mobile device management (MDM) via Configmgr 2012 SP1 and ConfigMgr 2012 R2.

What does this mean for customers?

From April 10th 2017, the Intune Connector will no longer connect to Microsoft’s Intune service meaning that managed devices will effectively become unmanaged. Data for ConfigMgr policies, applications etc will not flow up to the service and device data will not flow down until the problem is addressed.

How can I fix the problem?

Simple – update your ConfigMgr site.

What’s the supported state then?

Ideally you  should really be upgrading to ConfigMgr Current Branch (CB). I have a blog post that takes you through the steps to upgrade. The latest baseline release for CB is 1606, so you should install this version and then update to the latest release, which is 1610. The blog post updates to 1511 but is still valid for 1606. Here’s the post. Note that if your site server is running Windows Server 2008 R2 then you must update this as soon as possible when in the Current Branch release, since that OS will not be supported in the next Configmgr update – which will be very soon. Here’s a guide on how to do that. Also check you ConfigMgr SQL install is supported in Current Branch here. Finally, for Current Branch, if you need to update your SQL here’s how.

Alternatively, you could update the latest supported service pack’s for Configuration Manager 2012, these are SP2 or R2 SP1. However I would look at CB as your option. Either update is an in-place upgrade so there’s an easy transition to resolve you MDM dilemma.

 

 

 

 

Advertisements