Forum Discussion
ConfigDeviceHealthMonitoringServiceInstance - Error 404 - The system cannot find the file specified.
ConfigDeviceHealthMonitoringServiceInstance is now officially part of the device heath monitoring CSP and I have a couple of devices that are showing this same error. They are all on either Windows 10 22H2 or Windows 11 22H2 and have the August CU (they had the July CU and were experiencing the same issue last month). Any ideas on how I can get ConfigDeviceHealthMonitoringServiceInstance onto these devices so I can get EPM to install on them?
Yep, i know... But yeah this post is indeed 2 years old 🙂
I also noticed you posted a reply on on blog.
I assume you configured the EPM policy like this right?
Any other update reporting policies configured?
- BrandoCO7373Aug 18, 2023Copper ContributorRudy_Ooms_MVP
No it does not explain why it was missing. I don't know how I missed that blog post in my research, but I really appreciate your help! Thank you very much! - Aug 18, 2023
hehe yeah i know… that remediation was created of one of my blogs about how to trigger the epm install and bypassing the dh stuff :)… but still that doesnt explain why that node csp was missing in the devices (prereq for the linkedenrollment csp)
https://call4cloud.nl/2023/05/the-lord-of-the-epm-the-war-of-the-mmp-c-enrollment/
but giving a bandage while i want to know the cause .. 🙂
- BrandoCO7373Aug 18, 2023Copper ContributorI ended up being able to resolve the issue with this: https://github.com/overlord64/Intune-Scripts/tree/main/Proactive%20Remediation/EPM
- Aug 17, 2023
Mmm... thats kinda weird... let me see what I can find. what happens when doing something probably stupid (aka not supported 🙂 ) and exporting and importing that Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\DeviceHealthMonitoring key from a working device to a non working device?
- BrandoCO7373Aug 14, 2023Copper Contributor
I have it configured slightly differently, requiring user confirmation.
EPM is working fine on the majority of my devices, there are just a handful receiving this error that also don't even have the HKLM\SOFTWARE\Microsoft\PolicyManager\default\DeviceHealthMonitoring\ConfigDeviceHealthMonitoringServiceInstance reg key.
There is also this error in the registry: