From a9d4c5d76f1c7214a8c9f0cd3b3e6ce7dd911b44 Mon Sep 17 00:00:00 2001 From: Joey Caparas Date: Tue, 12 Jul 2016 21:08:50 +1000 Subject: [PATCH] minor edits to clarify topic --- ...ng-windows-defender-advanced-threat-protection.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md index e75d5fd42a..dfa7a61e35 100644 --- a/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md +++ b/windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md @@ -333,9 +333,15 @@ If the verification fails and your environment is using a proxy to connect to th ## Troubleshoot onboarding issues with Microsoft Intune You can use Microsoft Intune to check error codes and attempt to troubleshoot the cause of the issue. -Use the following tables to understand the possible causes of issues while onboarding. +Use the following tables to understand the possible causes of issues while onboarding: -Microsoft Intune error codes and OMA-URIs: +- Microsoft Intune error codes and OMA-URIs table +- Known issues with non-compliance table +- Mobile Device Management (MDM) event logs table + +If none of the event logs and troubleshooting steps work, download and run the Local script from the **Endpoint Management** section on the **Navigation pane** of the portal on the endpoint. + +**Microsoft Intune error codes and OMA-URIs**: Error Code Hex | Error Code Dec | Error Description | OMA-URI | Possible cause and troubleshooting steps :---|:---|:---|:---|:--- @@ -373,7 +379,7 @@ ID | Severity | Event description | Description 1820 | Information | Windows Defender Advanced Threat Protection CSP: Set Nod's Value complete. NodeId: (%1), TokenName: (%2), Result: (%3). | Windows Defender ATP has completed to get specific node's value.
TokenName: Contains node name
Result: Error details or succeeded. -If none of the event logs and troubleshooting steps work, download and run the Local script from the **Endpoint Management** section on the **Navigation pane** of the portal on the endpoint. +