wdavconfig.py => mdatp --health

This commit is contained in:
Max Velitchko
2019-05-08 15:22:55 -07:00
parent ed83d70393
commit cbc377b547
2 changed files with 15 additions and 15 deletions

View File

@ -90,9 +90,7 @@ The installation will proceed.
The client machine is not associated with orgId. Note that the orgid is blank. The client machine is not associated with orgId. Note that the orgid is blank.
```bash ```bash
mavel-mojave:wdavconfig testuser$ sudo /Library/Extensions/wdavkext.kext/Contents/Resources/Tools/wdavconfig.py mavel-mojave:wdavconfig testuser$ mdatp --health orgId
uuid : 69EDB575-22E1-53E1-83B8-2E1AB1E410A6
orgid :
``` ```
2. Install the configuration file on a client machine: 2. Install the configuration file on a client machine:
@ -105,9 +103,8 @@ The installation will proceed.
3. Verify that the machine is now associated with orgId: 3. Verify that the machine is now associated with orgId:
```bash ```bash
mavel-mojave:wdavconfig testuser$ sudo /Library/Extensions/wdavkext.kext/Contents/Resources/Tools/wdavconfig.py mavel-mojave:wdavconfig testuser$ mdatp --health orgId
uuid : 69EDB575-22E1-53E1-83B8-2E1AB1E410A6 E6875323-A6C0-4C60-87AD-114BBE7439B8
orgid : E6875323-A6C0-4C60-87AD-114BBE7439B8
``` ```
After installation, you'll see the Microsoft Defender icon in the macOS status bar in the top-right corner. After installation, you'll see the Microsoft Defender icon in the macOS status bar in the top-right corner.

View File

@ -178,26 +178,29 @@ Thu Feb 21 11:17:23 mavel-mojave jamf[8051]: No patch policies were found.
You can also check the onboarding status: You can also check the onboarding status:
```bash ```bash
mavel-mojave:~ testuser$ sudo /Library/Extensions/wdavkext.kext/Contents/Resources/Tools/wdavconfig.py mavel-mojave:~ testuser$ mdatp --health
uuid : 69EDB575-22E1-53E1-83B8-2E1AB1E410A6 ...
orgid : 79109c9d-83bb-4f3e-9152-8d75ee59ae22 licensed : true
orgid managed : 79109c9d-83bb-4f3e-9152-8d75ee59ae22 orgId : "4751b7d4-ea75-4e8f-a1f5-6d640c65bc45"
orgid effective : 79109c9d-83bb-4f3e-9152-8d75ee59ae22 ...
``` ```
- **orgid/orgid managed**: This is the Microsoft Defender ATP org id specified in the configuration profile. If this value is blank, then the Configuration Profile was not properly set. - **licensed**: This is a confirmation that the machine is licensed for ATP.
- **orgid effective**: This is the Microsoft Defender ATP org id currently in use. If it does not match the value in the Configuration Profile, then the configuration has not been refreshed. - **orgid**: Your ATP org id, it will be the same for your organization.
## Check onboarding status ## Check onboarding status
You can check that machines are correctly onboarded by creating a script. For example, the following script checks that enrolled machines are onboarded: You can check that machines are correctly onboarded by creating a script. For example, the following script checks that enrolled machines are onboarded:
```bash ```bash
sudo /Library/Extensions/wdavkext.kext/Contents/Resources/Tools/wdavconfig.py | grep -E 'orgid effective : [-a-zA-Z0-9]+' mdatp --health healthy
``` ```
This script returns 0 if Microsoft Defender ATP is registered with the Windows Defender ATP service, and another exit code if it is not installed or registered. This script returns:
- 0 if Microsoft Defender ATP is registered with the Windows Defender ATP service
- 1 if the machine is not onboarded
- 3 if the connection to the daemon cannot be established (daemon is not running)
## Test alert ## Test alert