Intune IME Logs explanation
Intune Management Extension (IME) is Intune agent, it will installed automatically right after the Device enrolled in Intune.
It extend the Intune capabilities by enabling the advanced management task.-
- Deploying Application.
- Running Script.
- Collecting Device Health data and telemetry.
Prerequisites-
Operating System- Windows 10/11
Enrollment- Device should be enroll in Intune.
Permissions- Local admin right is needed.
Tools required to access logs- CMTrace.exe tool is required to open the logs. logs can be open on notepad also.
Where to access the logs file –
Intune Management Extension logs are available on below path.
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
Intune Management Extension logs list
- AgentExecutor.log- Logs is used to track script execution.
- AppActionProcessor.log- Used for Monitoring app deployment.
- AppWorkload.log- Used to tack Win32 App deployment status.
- ClientCertCheck.log- Used to verify MDM certificate that used for device authentication.
- ClientHealth.log- Used to check IME health status including server status and connectivity issues.
- DeviceHealthMonitoring.log- Tracking the device health status including hardware details and device readiness checks.
- HealthScript.log- Used to track script deployment status.
- IntuneManagementExtension.log- IME is the main log that is used to IME activities like, Service startup and shutdown status, communication with Intune.
- Sensor.log- Used to track device uses data such as a CPU and Memory uses.
- Win32AppInventory.log- Logs is used to track the Win32 App installed inventory.
Read Logs with PowerShell script.
$logPath = “C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log”
$logContent = Get-Content -Path $logPath
$logContent | Select-String -Pattern “error|warning”