Forum Discussion
Endpoint privilege management, deployment unsuccessful with "device health monitoring" error
-----------------
PS C:\Windows\system32> Send-localmdmrequest -OmaUri ./Vendor/MSFT/DMClient/Provider/MS%20DM%20Server/LinkedEnrollment
CmdId : 4
Cmd : Get
Status : 200
OmaUri : ./Vendor/MSFT/DMClient/Provider/MS%20DM%20Server/LinkedEnrollment
Data : Enroll/Unenroll/Priority/LastError/EnrollStatus
PS C:\Windows\system32> $test3 = @"
>> <SyncBody>
>> <Replace>
>> <CmdID>2</CmdID>
>> <Item>
>> <Target>
>> <LocURI> ./Vendor/MSFT/DMClient/Provider/MS%20DM%20Server/LinkedEnrollment/DiscoveryEndpoint</LocURI>
>> </Target>
>> <Data>https://discovery.dm.microsoft.com/EnrollmentConfiguration?api-version=1.0</Data>
>> </Item>
>> </Replace>
>> </SyncBody>
>> "@
PS C:\Windows\system32> send-localmdmrequest -SyncML $test3
CmdId : 5
Cmd : Replace
Status : 405
OmaUri : ./Vendor/MSFT/DMClient/Provider/MS%20DM%20Server/LinkedEnrollment/DiscoveryEndpoint
Data :
- Dec 23, 2023
i would rather configure it with a csp in intune to be 100% sure it will be targetted at the proper enrollment instead of the localmdm one:
OMAURI: ./Device/Vendor/MSFT/DMClient/Provider/MS%20DM%20SERVER/LinkedEnrollment/DiscoveryEndpoint
Type: string
Value:
https://discovery.dm.microsoft.com/EnrollmentConfiguration?api-version=1.0">https://discovery.dm.microsoft.com/EnrollmentConfiguration?api-version=1.0But looking at the response you got 405... this discovery URL shouldn't be the main issue.
Your best option is to install fiddler just like i did,to find out what error it gets when it reaches out to the service
Because the error you got, was exactly the same as the k12 schools got.. so that's why i am wondering about the actual domain name (as that domain name is sent over in the request)
MMP-C Discovery failed | No valid Endpoint | EPM (call4cloud.nl)
IF you don't know how send me a pm (teams /x) to set it up