Forum Discussion
Intune Management Extension not installing
Oliver, thanks for following up on this. Unfortunately I haven't made any progress on this as I have been working on other things. I will get back to it, hopefully sometime this week and let you know how I get on
Cheers
Did you get anywhere with this? I have been struggling to figure out why sometimes I do not get the service and sometimes I do. I have checked logs everywhere on the machine and do not see any relevant errors.
- Feb 06, 2018
In our environments it's working quite well. We had problems due to interrupted network connectivity but this is not a problem of Intune or the agent. Are you targeting the scripts as user assignments? Can you share logs from a machine not getting the service? MDM report, logfiles, eventlogs, Intune Agent logfiles registry (HKLM\Software\Microsoft\EnterpriseDesktopAppManagement)...
- Severin HotzFeb 06, 2018Copper Contributor
I have the same problem. Intune management extension does not get installed.
I created a powershell script and assigned it to a group containing the user.
Any ideas? Or at least a way to troubleshoot the issue?
- Feb 06, 2018
Sounds like problems with the initial MSI Install job via EnterpriseDesktopAppManagement CSP:
see here:
https://docs.microsoft.com/en-us/windows/client-management/mdm/enterprisedesktopappmanagement-csp
MSI/ProductID/Status Status of the application.
In the registry at HKLM\SOFTWARE\Microsoft\EnterpriseDesktopAppManagement\<SID>\<MSI-ProductCode> you can find the Status according to the CSP site above.
Try to figure out this status - Download error or what else and correlate with your machine and environment (may there be a proxy issue?). In the past Intune followed a retry logic. I give an example: try it 3 times with timeout of 10 min and then fail. If failed, Intune tried it again in 7 days (the 7 days setting after fail was fix in the past, maybe this interval is lowered now but I don't now, registry suggests that this is changed). So again the values above are examples based on registry values for the logic! I do not know if this is correct as I do not have documentation for it.
What are the registry values for Enforcement* on that machine. Values are in the same path as described above. There are the Retry, Interval, Timeout, Index and StartTime values... I'm not sure if this is all and how they correlate to each other exactly... But maybe we can extract some information from the retry values. For example it may look like that all retries are failed and the machine is in extended timeout currently....
Other way dealing with MSI install fails in the past, was to change something at the MSI metadata to re-enforce push/install. This is not possible in our case as we have no control over the SideCar agent metadata.
Can someone share the MDM advanced diagnostic report... what is listed there and what about the eventlogs...