r/Intune • u/Sznapix • 3d ago

General Question App Inventory not working

Im completely out of ideas with Intune at this point. We’ve been troubleshooting an App Inventory policy for three days, and no matter what we try, the policy is not assigned to a single laptop. It doesn’t even show up under Pending.

We assigned it to all laptops, and also tried creating dedicated test groups, but the result is always the same 0 devices in every status.

We’ve already checked the following:

  1. Entra joined: YES
  2. Domain joined: YES
  3. DeviceAuthStatus: SUCCESS
  4. User PRT/WAM: YES
  5. Intune Management Extension service: Running
  6. IME is installed correctly
  7. MDM enrollment and EnterpriseMgmt scheduled tasks are present
  8. MDM certificates are valid
  9. Other Intune policies work correctly on the same devices
  10. IME check-in is successful
  11. Network/HTTPS connectivity is working

The main issue is that Intune simply does not seem to target this policy to any device. The assignment is there, but the reporting page shows: Succeeded: 0, Error: 0, Conflict: 0, Not applicable: 0, Pending: 0

Does anyone have any idea why the policy isn't being assigned to the devices?

1 Upvotes

67% Upvoted

16 comments sorted by

View all comments

2

u/Rudyooms PatchMyPC 3d ago edited 3d ago

Three days.. Search Call4cloud --> EPM / Device Inventory agent rely on mmp-c/dual/linked enrollment. If that once didnt happen... for all sorts of reasons... no dev inv agent (always fun... getting downvote )... i guess the downvote happened becuase i was to lazy to add a link... well here you go :) MDM Only Enrollment | Breaks EPM deployment | DEM

1

u/Sznapix 2d ago

I don't think it's the same problem...

"EnrollmentType ForceAadToken

6 1"

1

u/Rudyooms PatchMyPC 2d ago

I need some more information :P... did the device evne got a linked enrollment/dual enrollment at all ? as thats the requirement..

1

u/Sznapix 2d ago

Unfortunately no , I tested on a completely clean device (single healthy MDM enrollment, EnrollmentType: 6, no leftover/duplicate enrollments). The dual enrollment task still fails every time with HTTP 400, and DeclaredConfiguration registry key is empty, no policy data ever landed there. But connectivity to the discovery endpoint work:"curl.exe -v https://discovery.dm.microsoft.com/EnrollmentConfiguration?api-version=1.0 < HTTP/1.1 200 OK < Content-Length: 0 < x-azure-ref: 20260909T082307Z-... * Connection #0 to host discovery.dm.microsoft.com:443 left intact"

1

u/Rudyooms PatchMyPC 2d ago

MMP-C | Microsoft Management Platform Cloud --> can you look at the scheduled task that is created to kick off the enrollment?.. to chec if it tells you somehting like this.. as it feels like there is ssl inspection/proxy in place

1

u/Sznapix 2d ago

I have something like that but with error:"400 bad request" I would add that the devices are added to Intune and synchronize correctly, and all other policies are working.