Skip to content

Commit b77be66

Browse files
Merge pull request #24007 from MicrosoftDocs/main
Publish 01/16, 3:30 PM IST
2 parents 8046040 + f15f487 commit b77be66

4 files changed

Lines changed: 13 additions & 23 deletions

File tree

microsoft-365/security/defender-endpoint/configure-server-endpoints.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -156,9 +156,8 @@ You'll need to download both the **installation** and **onboarding** packages fr
156156

157157
The **installation package** contains an MSI file that installs the Microsoft Defender for Endpoint agent.
158158

159-
The **onboarding package** contains the following files:
159+
The **onboarding package** contains the following file:
160160

161-
- `OptionalParamsPolicy` - contains the setting that enables sample collection
162161
- `WindowsDefenderATPOnboardingScript.cmd` - contains the onboarding script
163162

164163
Follow these steps to download the packages:

microsoft-365/security/defender-endpoint/linux-support-ebpf.md

Lines changed: 10 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,6 @@ In case you want to manually disable eBPF then you can run the following command
7777
```bash
7878
sudo mdatp config ebpf-supplementary-event-provider --value [enabled/disabled]
7979
```
80-
8180
You can also update the mdatp_managed.json file:
8281

8382
```JSON
@@ -87,9 +86,7 @@ You can also update the mdatp_managed.json file:
8786
}
8887
}
8988
```
90-
91-
Refer to [Set preferences for Microsoft Defender for Endpoint on Linux](linux-preferences.md) for detailed sample json file.
92-
89+
Refer to the link for detailed sample json file - [Set preferences for Microsoft Defender for Endpoint on Linux](linux-preferences.md)
9390
> [!IMPORTANT]
9491
> If you disable eBPF, the supplementary event provider switches back to auditd.
9592
> In the event eBPF doesn't become enabled or is not supported on any specific kernel, it will automatically switch back to auditd and retain all auditd custom rules.
@@ -116,12 +113,12 @@ You can check the agent health status by running the **mdatp** health command. M
116113
```bash
117114
uname -a
118115
```
116+
Using Oracle Linux 8.8 with kernel version **5.15.0-0.30.20.el8uek.x86_64, 5.15.0-0.30.20.1.el8uek.x86_64** might result into kernel hang issues.
119117

120-
Using Oracle Linux 8.8 with kernel version **5.15.0-0.30.20.el8uek.x86_64, 5.15.0-0.30.20.1.el8uek.x86_64** might result into kernel hang issues.
118+
Following steps can be taken to mitigate this issue:
121119

122-
The following steps can be taken to mitigate this issue:
120+
1. Use a kernal version higher or lower than **5.15.0-0.30.20.el8uek.x86_64, 5.15.0-0.30.20.1.el8uek.x86_64** on Oracle Linux 8.8, if you want to use eBPF as supplementary subsystem provider. Please note, min kernel version for Oracle Linux is RHCK 3.10.0 and Oracle Linux UEK is 5.4.
123121

124-
1. Use a kernal version higher or lower than **5.15.0-0.30.20.el8uek.x86_64, 5.15.0-0.30.20.1.el8uek.x86_64** on Oracle Linux 8.8, if you want to use eBPF as supplementary subsystem provider. Note the min kernel version for Oracle Linux is RHCK 3.10.0 and Oracle Linux UEK is 5.4.
125122
2. Switch to auditd mode if customer needs to use the same kernel version
126123

127124
```bash
@@ -136,12 +133,11 @@ The following two sets of data help analyze potential issues and determine the m
136133

137134
#### Troubleshooting performance issues
138135

139-
If you see a hike in resource consumption by Microsoft Defender on your endpoints, it's important to identify the process/mount-point/files that is consuming most CPU/Memory utilization and then apply necessary exclusions. After applying possible AV exclusions, if wdavdaemon (parent process) is still consuming the resources, then use the ebpf-statistics command to obtain the top system call count:
136+
If you see a hike in resource consumption by Microsoft Defender on your endpoints, it is important to identify the process/mount-point/files that is consuming most CPU/Memory utilization and then apply necessary exclusions. After applying possible AV exclusions, if wdavdaemon (parent process) is still consuming the resources, then use the ebpf-statistics command to obtain the top system call count:
140137

141138
```Bash
142139
sudo mdatp diagnostic ebpf-statistics
143140
```
144-
145141
```Output
146142
Output
147143
Monitor 20 seconds
@@ -156,18 +152,19 @@ Top file paths:
156152
/home/gargank/tmp-stress-ng-rename-13550-31/stress-ng-rename-13550-31-374985 : 1
157153
/home/gargank/tmp-stress-ng-rename-13550-31/stress-ng-rename-13550-31-374983 : 1
158154
/home/gargank/tmp-stress-ng-rename-13550-31/stress-ng-rename-13550-31-374981 : 1
155+
159156
Top initiator paths:
160157
/usr/bin/stress-ng : 50000
161158
/opt/microsoft/mdatp/sbin/wdavdaemon : 13
159+
162160
Top syscall ids:
163161
82 : 1699333
164162
90 : 10
165163
87 : 3
166-
```
167-
168-
In the above output, it can be seen that stress-ng is the top process, generating large number of events, and might result in performance issues. Most likely stress-ng is generating the system call with ID 82. You can create a ticket with Microsoft to get this process excluded. In future, as part of upcoming enhancements, you will have more control to apply such exclusions yourself.
164+
```
165+
In the above output, it can be seen that stress-ng is the top process generating large number of events and might result into performance issues. Most likely stress-ng is generating the system call with ID 82. You can create a ticket with Microsoft to get this process excluded. In future as part of upcoming enhancements, you will have more control to apply such exclusions at your end.
169166

170-
Exclusions applied to auditd can not be migrated or copied to eBPF. Common concerns such as noisy logs, kernel panic, and noisy syscalls are already taken care of by eBPF internally. In case you want to add any further exclusions, then reach out to Microsoft to get the necessary exclusions applied.
167+
Exclusions applied to auditd cannot be migrated or copied to eBPF. Common concerns such as noisy logs, kernel panic, noisy syscalls are already taken care of by eBPF internally. In case you want to add any further exclusions, then reach out to Microsoft to get the necessary exclusions applied.
171168

172169
## See also
173170

microsoft-365/security/defender-endpoint/microsoft-defender-antivirus-production-ring-deployment-group-policy-wsus.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ If you encounter problems with your deployment, create or append your Microsoft
167167

168168
:::image type="content" source="images/microsoft-defender-antivirus-deploy-ring-group-policy-wsus-gp-management-console.png" alt-text="Screenshot that shows a screen capture of the Group Policy Management console, initiating a forced update." lightbox="images/microsoft-defender-antivirus-deploy-ring-group-policy-wsus-gp-management-console.png":::
169169

170-
1. After the issue is resolved, set the **Signature Update Fallback Order** back to the original setting. `InternalDefinitionUpdateServder|MicrosoftUpdateServer|MMPC|FileShare`.
170+
1. After the issue is resolved, set the **Signature Update Fallback Order** back to the original setting. `InternalDefinitionUpdateServer|MicrosoftUpdateServer|MMPC|FileShare`.
171171

172172
See also:
173173

microsoft-365/security/defender-endpoint/onboard-downlevel.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -164,13 +164,7 @@ Verify that Microsoft Defender Antivirus and Microsoft Defender for Endpoint are
164164

165165
For information on how to use Group Policy to configure and manage Microsoft Defender Antivirus on your Windows servers, see [Use Group Policy settings to configure and manage Microsoft Defender Antivirus](use-group-policy-microsoft-defender-antivirus.md).
166166

167-
2. Run the following command to verify that Microsoft Defender for Endpoint is running:
168-
169-
```dos
170-
sc.exe query sense
171-
```
172-
173-
The result should show it is running. If you encounter issues with onboarding, see [Troubleshoot onboarding](troubleshoot-onboarding.md).
167+
If you encounter issues with onboarding, see [Troubleshoot onboarding](troubleshoot-onboarding.md).
174168

175169
## Run a detection test
176170

0 commit comments

Comments
 (0)