deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-17 15:57:23 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Update mac-support-kext.md

Browse Source 
removed $ prompts in command-line snippets
This commit is contained in:
schmurky 2020-08-03 16:01:47 +08:00
parent b320168fa5
commit f4b64befaa
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/security/threat-protection/microsoft-defender-atp/mac-support-kext.md
View File

@ -34,7 +34,7 @@ If you did not approve the kernel extension during the deployment / installation
You can also run ```mdatp --health```. It reports if real-time protection is enabled but not available. This is an indication that the kernel extension is not approved to run on your device. You can also run ```mdatp --health```. It reports if real-time protection is enabled but not available. This is an indication that the kernel extension is not approved to run on your device.
```bash ```bash
$ mdatp --health mdatp --health
... ...
realTimeProtectionAvailable : false realTimeProtectionAvailable : false
realTimeProtectionEnabled : true realTimeProtectionEnabled : true
@ -63,7 +63,7 @@ In this case, you need to perform the following steps to trigger the approval fl
1. In Terminal, attempt to install the driver. The following operation will fail, because the kernel extension was not approved to run on the device, however it will trigger the approval flow again. 1. In Terminal, attempt to install the driver. The following operation will fail, because the kernel extension was not approved to run on the device, however it will trigger the approval flow again.
```bash ```bash
$ sudo kextutil /Library/Extensions/wdavkext.kext sudo kextutil /Library/Extensions/wdavkext.kext
Kext rejected due to system policy: <OSKext 0x7fc34d528390 [0x7fffa74aa8e0]> { URL = "file:///Library/StagedExtensions/Library/Extensions/wdavkext.kext/", ID = "com.microsoft.wdavkext" } Kext rejected due to system policy: <OSKext 0x7fc34d528390 [0x7fffa74aa8e0]> { URL = "file:///Library/StagedExtensions/Library/Extensions/wdavkext.kext/", ID = "com.microsoft.wdavkext" }
Kext rejected due to system policy: <OSKext 0x7fc34d528390 [0x7fffa74aa8e0]> { URL = "file:///Library/StagedExtensions/Library/Extensions/wdavkext.kext/", ID = "com.microsoft.wdavkext" } Kext rejected due to system policy: <OSKext 0x7fc34d528390 [0x7fffa74aa8e0]> { URL = "file:///Library/StagedExtensions/Library/Extensions/wdavkext.kext/", ID = "com.microsoft.wdavkext" }
Diagnostics for /Library/Extensions/wdavkext.kext: Diagnostics for /Library/Extensions/wdavkext.kext:
@ -76,13 +76,13 @@ In this case, you need to perform the following steps to trigger the approval fl
4. In Terminal, install the driver again. This time the operation will succeed: 4. In Terminal, install the driver again. This time the operation will succeed:
```bash ```bash
$ sudo kextutil /Library/Extensions/wdavkext.kext sudo kextutil /Library/Extensions/wdavkext.kext
``` ```
The banner should disappear from the Defender application, and ```mdatp --health``` should now report that real-time protection is both enabled and available: The banner should disappear from the Defender application, and ```mdatp --health``` should now report that real-time protection is both enabled and available:
```bash ```bash
$ mdatp --health mdatp --health
... ...
realTimeProtectionAvailable : true realTimeProtectionAvailable : true
realTimeProtectionEnabled : true realTimeProtectionEnabled : true