From 2590c98f02dd2a47f5770bc4b4dda0723a8d53f3 Mon Sep 17 00:00:00 2001 From: dbyrdaquent Date: Fri, 26 Jun 2020 12:58:20 -0600 Subject: [PATCH] Update mac-support-install.md --- .../microsoft-defender-atp/mac-support-install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/mac-support-install.md b/windows/security/threat-protection/microsoft-defender-atp/mac-support-install.md index d6656e4eac..4e380f4e2a 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/mac-support-install.md +++ b/windows/security/threat-protection/microsoft-defender-atp/mac-support-install.md @@ -42,7 +42,7 @@ preinstall com.microsoft.wdav end [2020-03-11 13:08:49 -0700] 804 => 1 In this example, the actual reason is prefixed with `[ERROR]`. The installation failed because a downgrade between these versions is not supported. -## MDATP install log fails to record installation +## MDATP install log missing or not updated In rare cases, installation leaves no trace in MDATP's /Library/Logs/Microsoft/mdatp/install.log file. You can verify that an installation happened and analyze possible errors by querying macOS logs (this is helpful in case of MDM deployment, when there is no client UI). We recommend that you use a narrow time window to run a query, and that you filter by the logging process name, as there will be a huge amount of information.