From d56559456a721ed5021d568104ac9ea32ecd3a06 Mon Sep 17 00:00:00 2001 From: dbyrdaquent Date: Fri, 12 Jun 2020 16:21:50 -0600 Subject: [PATCH 1/3] Update mac-support-install.md Light copy edit --- .../microsoft-defender-atp/mac-support-install.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) 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 564bfecdbd..115ca811c0 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 @@ -25,9 +25,9 @@ ms.topic: conceptual ## Installation failed -For manual installation, it is Summary page of the installation wizard that says "An error occurred during installation. The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance". For MDM deployments it would be exposed as a generic installation failure as well. +For manual installation, the Summary page of the installation wizard says, "An error occurred during installation. The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance." For MDM deployments, it displays as a generic installation failure as well. -While we do not expose exact error to the end user, we keep a log file with installation progress in `/Library/Logs/Microsoft/mdatp/install.log`. Each installation session appends to this log file, you can use `sed` to output the last installation session only: +While we do not display an exact error to the end user, we keep a log file with installation progress in `/Library/Logs/Microsoft/mdatp/install.log`. Each installation session appends to this log file. You can use `sed` to output the last installation session only: ```bash $ sed -n 'H; /^preinstall com.microsoft.wdav begin/h; ${g;p;}' /Library/Logs/Microsoft/mdatp/install.log @@ -39,13 +39,13 @@ correlation id=CB509765-70FC-4679-866D-8A14AD3F13CC preinstall com.microsoft.wdav end [2020-03-11 13:08:49 -0700] 804 => 1 ``` -In the example above the actual reason is prefixed with `[ERROR]`. +In the this example, the actual reason is prefixed with `[ERROR]`. The installation failed because a downgrade between these versions is not supported. -## No MDATP's install log +## MDATP install log fails to record installation -In rare cases installation leaves no trace in MDATP's /Library/Logs/Microsoft/mdatp/install.log file. -You can verify that installation happened and analyze possible errors by querying macOS logs (this can be helpful in case of MDM deployment, when there is no client UI). It is recommended to have a narrow time window to query and filter by the logging process name, as there will be huge amount of information; +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. ```bash grep '^2020-03-11 13:08' /var/log/install.log From f1a0a708e9990e76b7455ce6962f57aee1d45bf9 Mon Sep 17 00:00:00 2001 From: dbyrdaquent Date: Thu, 25 Jun 2020 20:47:41 -0600 Subject: [PATCH 2/3] 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 115ca811c0..d6656e4eac 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 @@ -39,7 +39,7 @@ correlation id=CB509765-70FC-4679-866D-8A14AD3F13CC preinstall com.microsoft.wdav end [2020-03-11 13:08:49 -0700] 804 => 1 ``` -In the this example, the actual reason is prefixed with `[ERROR]`. +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 From 2590c98f02dd2a47f5770bc4b4dda0723a8d53f3 Mon Sep 17 00:00:00 2001 From: dbyrdaquent Date: Fri, 26 Jun 2020 12:58:20 -0600 Subject: [PATCH 3/3] 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.