- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2022 09:59 AM
Hi! Hoping I can get some advice on this topic please. We are using SAMP, have SCCM plug-in implemented and will be moving to SCCM SG within the next few weeks.
Since SAMP implementation, we continue to battle with getting Windows PC details showing up in SCCM and being pushed to ServiceNow in a timely fashion. This is strictly due to how SCCM works to get new PC data, how long the user PC is connected to the network at any point in time, etc. This is especially a problem with regard to completing new hire requests for software through our software catalog. (The device is not yet in ServiceNow so device based licensing can't be allocated and therefore fulfillment/ordering process can't be completed, delays impact productivity, etc.)
Our client PC team that manages SCCM & Intune tells me that we could get initial PC w/assigned to user data pushed to us much faster through Intune. Everything I read about the Intune SG focuses a lot on mobile devices with some limited references to PC/Computer data.
Is the Intune SG robust enough in the PC/Computer space to do the same/similar function as SCCM SG? What limitations exist?
Is it possible to consider running both Intune to get initial data more quickly and SCCM to capture and update more detailed data? (without ending up with multiple/duplicate records for the same device, etc)
What is the best practice recommendation? What are others doing?
Many thanks in advance for any insight!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 08:29 AM
Hi Jen,
We work closely with the Microsoft Intune product team on this use case. A couple of important items to note:
- Intune does not collect usage or last used date. If SCCM is not used to capture this data, you could be limited from a reclamation use case perspective.
- Intune returns a single string for software installs (publisher/product/version/edition). There is inconsistency between installs so the data cannot be parsed leading to lower normalization. Microsoft has stated that this is on their near term roadmap to fix.
Intune does provide benefits as you mentioned above, however these would be the main drawbacks from a SAM perspective.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2022 08:29 AM
Hi Jen,
We work closely with the Microsoft Intune product team on this use case. A couple of important items to note:
- Intune does not collect usage or last used date. If SCCM is not used to capture this data, you could be limited from a reclamation use case perspective.
- Intune returns a single string for software installs (publisher/product/version/edition). There is inconsistency between installs so the data cannot be parsed leading to lower normalization. Microsoft has stated that this is on their near term roadmap to fix.
Intune does provide benefits as you mentioned above, however these would be the main drawbacks from a SAM perspective.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2022 07:18 AM
Julian - thanks so much this is really helpful!
Is it possible for both to be implemented where Intune is used to provide/maintain a limited set of details with enough information that SCCM can then identify the appropriate computer to update it?
Thanks!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2022 07:15 AM
Hi Julian,
Do you know if the first point above (the fact that Intune doesn't collect usage or last used date) is also on Microsoft's roadmap to fix/address?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2024 11:24 PM
Julian do we know if Microsoft have now introduced this feature to collect usage or last used date ?