Forum Discussion
Intune Confusion
- Sep 14, 2025
Hy,
Intune Management Extension:
IME is responsible for running PowerShell scripts and Win32 app deployments, so a device will first become the IME after a proper app or script assignment.
The IME Service only runs when device configuration policies, Win32 app or Scripts deployments are targeted to the device
So it could be possible, that the system with IME running has received a policy or app assignment which triggers it, while the others have not yet triggered IME because no applicable policies or apps are assigned (or successfully targeted) to them yet.
Device Only licensing:
these are intended for devices that are not user-affiliated, such as shared devices, kiosks, or hotdesks.
MDMURL blank:
dsregcmd output can mean the device is only enrolled in device management mode (device-only enrollment) without full MDM configuration profile or user MDM enrollment.
Questions:
Can you try to make an app deployment to those devices?
Check the Events under Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
Good luck!
Hy,
Intune Management Extension:
IME is responsible for running PowerShell scripts and Win32 app deployments, so a device will first become the IME after a proper app or script assignment.
The IME Service only runs when device configuration policies, Win32 app or Scripts deployments are targeted to the device
So it could be possible, that the system with IME running has received a policy or app assignment which triggers it, while the others have not yet triggered IME because no applicable policies or apps are assigned (or successfully targeted) to them yet.
Device Only licensing:
these are intended for devices that are not user-affiliated, such as shared devices, kiosks, or hotdesks.
MDMURL blank:
dsregcmd output can mean the device is only enrolled in device management mode (device-only enrollment) without full MDM configuration profile or user MDM enrollment.
Questions:
Can you try to make an app deployment to those devices?
Check the Events under Event Viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostic-Provider
Good luck!
Hey Bogan,
I hope that you are well today! I greatly appreciate your response.
My test workstations are all now receiving deployed packages and as you point out, the IME service is being 'enforced' / installed upon the devices once a package is deployed to said workstations (just takes a while - sometimes a long while).
I've also created a PPKG file that I've placed upon a USB drive that executes AAD join and Intune enrollment (auto-enrollment enabled) within the workstation OOBE. The new system that downloads / installs all corporate software there afterwards - so actually quite happy with how this is now setup.
Can't really use autopilot as we are small(ish) business that does not purchase directly from the workstation manufacturer (thus cannot get the hardware harsh pre-deployment) but the USB PPKG approach will definitely suffice and is considerably better than what we are doing at the moment.
With regards to licensing, I understand that device only is intended only for hotdesks et al, but in terms of our requirements, I'm not (currently) seeing anything that device-only is not providing for us that a user license will; software deployment, update deployment, easier workstation deployment, configuration / compliance policies, workstation performance insights etc. Am I being short-sighted here?
Cheers.
- Bogdan_GuineaSep 25, 2025Iron Contributor
Hy,
Sorry for the late response.
You are correct that Microsoft's deployments currently focus on user-driven scenarios. For these deployments to work—especially when using Autopilot or Device Preparation—you need user licenses.
Currently, they have a preview feature under Device Preparation called "Automatic," which, as I understand, is not user-driven. You could try testing this option.
I believe you only need to upload a CSV file with your devices under Windows > Enrollment > Corporate Device Identifier to test this, and you might not need the USB method anymore.Good luck!