Forum Discussion
Scott Paterson
Jan 07, 2018Copper Contributor
Intune Management Extension not installing
I am testing Intune/EMS on Windows 10 (1709) PCs and trying to get Powershell scripts to run without success. I think the issue is with the Intune Management Extension not installing but cant find mu...
Scott Paterson
Jan 08, 2018Copper Contributor
No this directory ( IntuneManagementExtension ) does not exist....
Jan 15, 2018
Hi Scott,
maybe have a look at my blog post here:
Deep dive Microsoft Intune Management Extension – PowerShell Scripts
I cover inner workings and troubleshooting of the agent to find such particular issues with installing Intune Management Extension.
Two things to check for agent install issues are event viewer and the Agent MSI install log:
Start event viewer > Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin (event id 1924 and others)
MSI install log:
C:\Windows\system32\config\systemprofile\AppData\Local\mdm\ {25212568-E605-43D5-9AA2-7AE8DB2C3D09}.log
best,
Oliver
- Scott PatersonJan 15, 2018Copper Contributor
I should note that as a test I have deployed a few MSI's to my PC ( Notepad++ and 7Zip etc ) and these appear to install ok.
- Jan 28, 2018
Is your problem still existing? Can you share us some details about the event log entries?
ok
- ON2000Feb 06, 2018Brass Contributor
I also noticed the same since approx 2 weeks. This worked absolutely fine in the past (in Dec for example, I built internal docs based on these positive results).
Unfortunately, I did not found any root cause so far : in "devicemanagement" event log, stuff seems to communicate to the Intune backed and no obvious errors. Hitting "Sync button" does not help. The file C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.txt and the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Policies\ are no longer created.
Since that time (coincidence?), I have also problems with devices enrolled with on-prem users coming from "synched AD groups" (from an on-prem infra, and using ADFS), where neither apps, scripts, or profiles are applied, even if "devicemanagement" event log does also not show obvious errors.
I will post here once I will progress in my tests.
- Jan 15, 2018
Okay the way the MSI's gets pushed to the machine is the same how the Intune Agent gets pushed down. So basically it should work.
How is your assignment did you use user assignment? In my tests that was the only functional way.
- Jan 15, 2018
I've checked a few of my test machines, I can't find event entries with ID 822. Can you post a little more detail on your error events?
- Scott PatersonJan 15, 2018Copper Contributor
Oliver, thanks for the update.
If I look in the appdata\local\mdm folder it is empty
In event viewer I have a number of errors with Event ID 822 ( MDM PolicyManager:Acquiring the merge lock.... ), each ending with "cannot find the file specified", and a number of Event ID 454, Command failure status.
Not sure from your guide what this means or where to look next ?
Regards