Let’s discuss the List of Intune Feature Gaps and Targeting Gaps and Targeting Gaps. Daniel Ratliff, a Lead Systems Engineer, specializes in MSIntune, ConfigMgr, OSD, Windows, Browsers, msedge, PowerShell, etc. He keeps an active running list using ConfigMgr and offers valuable insights into these areas.
The Intune gaps highlighted limitations in Microsoft Intune compared to ConfigMgr (SCCM) for specific IT management tasks, especially in large enterprise environments. Targeting gaps refer to limitations in Microsoft Intune’s ability to control which devices or users receive specific configurations, policies, or software deployments.
The Device Inventory feature, expected by the end of the year, should address several of Intune’s current inventory and targeting gaps. With better device inventory, Intune should be able to collect more detailed data on devices, such as software versions, hardware configurations, and system properties.
Do you think Intune lacks features or targets gaps? Let me know your opinion in the comments section below. It highlights the areas where Intune falls short compared to SCCM, such as complex software installations, detailed targeting, and advanced reporting.
Table of Contents
What are the Main Gaps between Intune and SCCM?
Intune has several limitations compared to SCCM, including challenges with complex software installations, specific installation orders, 64-bit IME limitations, custom inventory, advanced targeting, detailed reporting, patching capabilities, software metering, policy check-in intervals, deployment expiration, real-time capabilities, and management of non-persistent VMs.
List of Intune Feature Gaps and Targeting Gaps Vs SCCM via Community
Whether SCCM (Microsoft Configuration Manager) is dying is a topic of significant debate. Despite Microsoft’s growing focus on Intune and cloud-based management solutions, SCCM remains a vital tool for many businesses due to its deep and comprehensive management capabilities.
- In our YouTube video, we explored Microsoft’s plans for SCCM’s future, highlighting that while Intune is becoming increasingly prominent, SCCM is unlikely to be phased out soon.
- The post also includes community insights on how these limitations impact management tasks and what improvements are expected in the future. All the other details are explained below.
Read More – Is SCCM Dying?
- Top 50 Latest SCCM Interview Questions and Answers
- Top 50 Latest Intune Interview Questions And Answers
Intune Feature Gaps
Let’s discuss the gaps in Intune and its targeting capabilities. When discussing the gaps in Microsoft Intune, it’s helpful to consider the general limitations and specific targeting issues. The following table and list provide a detailed overview of these limitations. Intune has specific gaps compared to traditional management tools like SCCM.
| Intune Gaps | Details |
|---|---|
| Software installation – Complex installs like ConfigMgr task sequences | Intune struggles with complex installations like SCCM task sequences that manage multiple applications or dependencies in a specific order. |
| Software installation – Specific/consecutive order | Intune does not support ensuring apps install in a specific sequence, unlike SCCM. |
| IME runs as 32-bit not 64-bit | Intune Management Extension (IME) runs in 32-bit mode, limiting interaction with 64-bit applications. |
| Custom inventory | Intune lacks detailed custom inventory capabilities compared to SCCM. |
| Targeting | Intune’s targeting is less flexible compared to SCCM. Difficulties in targeting specific groups or scenarios, complicating deployments. |
| Reporting/Analytics needs | Intune offers basic reporting, whereas SCCM provides comprehensive, customizable reports. |
| Patching capabilities, only WufB (no maintenance windows) | Intune uses Windows Update for Business (WufB) without maintenance windows, unlike SCCM. |
| Software metering & usage | Challenges in tracking app usage and managing software licenses effectively. |
| 8 hour policy check-in (ConfigRefresh is 90 minutes) | Intune devices check in every 8 hours, while ConfigMgr devices check in every 90 minutes. |
| Expire/disable deployments | Intune lacks easy options to expire or disable deployments for apps, policies, or configurations. |
| Real-time capabilities like CMPivot/Run Scripts | Intune does not have real-time tools like ConfigMgr’s CMPivot or Run Scripts. |
| Non-persistent VMs | Intune struggles with managing non-persistent VMs |
| Platform scripts – 200 max | Intune limits to managing 200 scripts at a time. |
Intune Targeting Gaps
In this, we will look into the Intune targeting gaps that Daniel explained.
- Targeting Based on Installed Software – Intune can not easily target devices based on the installed software.
- Targeting Based on Software Versions—Intune does not allow you to target devices based on the versions of installed software.
- Targeting Based on Registry Keys – Intune does not support targeting based on specific registry keys.
Targeting Based on WMI Properties – Intune cannot target devices based on Windows Management Instrumentation (WMI) properties.
Targeting Based on Management Properties – Intune doesn’t offer targeting based on properties like domain or co-managed workload.
- Targeting Null Data – Intune cannot specifically target devices where specific software is not installed.
- Targeting Based on Policies – Intune cannot target based on policy compliance status (compliant, non-compliant, success, error).
- Targeting Based on User State—Intune does not support targeting based on user-related factors, such as whether a user is logged on or has a primary user set.
- Learn Intune Read – Intune (anoopcnair.com) and 63 Episodes Of Free Intune Training Endpoint Manager For Device Management Admins.
- Learn SCCM Read – SCCM Latest posts and Free SCCM Training 37 Hours of Latest Technical Content.
Is SCCM Dying?
Let’s discuss the following topic: SCCM! Is SCCM dying soon or a bit later, or is there a more extended life ahead for SCCM? This video also helps you show the Future of SCCM ConfigMgr Intune Admin Jobs and Intune vs. SCCM Job Openings and Admin Interest.
Resources
You can follow Daniel’s updates and discussions on Social Media.
Join the Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP from 2015 onwards for 10 consecutive years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is also a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.
I agree Intune has limitations in targeting, but the limitations are really in the dynamic groups of entraID that intune relies upon that’s where the issue needs to be resolved. There is a workaround if you’re using co-management and that is to create your collection in SCCM based on whatever conditions your looking for and then enable cloud sync for the collection so it will sync it to EntraID, which can then be used as a targeting group in Intune.