Last modified by Sabrina V. on 2025/03/04 12:26
Show last authors
1 {{aagon.priorisierung}}
2 160
3 {{/aagon.priorisierung}}
4
5 It may be the case that all full Defender scans created and started via the Scan Collections in Defender Management cause too much CPU usage, resulting in many side processes coming to a near or complete standstill.
6
7 This problem can be solved in ACMP using the //Scheduled System Scan// in the Defender configuration profile settings. In addition to using a maximum CPU utilisation during the system scan, you can also make continuing settings that define the scan. You can avoid the problem by removing all previously created scheduled scans from the Scan Collections and only creating new scheduled scans using the configuration profile settings.
8
9 To do this, proceed as follows:
10
11 1. Go to //Security > Defender Management// and select the //Configuration Profiles// tab.
12 1. Select a configuration profile and double click it. The configuration profile settings will open.
13 1. In these settings, go to the //Scheduled Scans// tab. Remove all system scans from here. The quick scans can be retained.
14 1. Go back to the Settings tab and select //Scan Settings// > //Scheduled System Scan//.
15 1. This is where you create new system scans. In addition to scheduling the day of the week, time and maximum CPU usage during a scan, you can define some other settings that affect this system scan.
16 1. Click //Save//.
17
18 (((
19
20 )))
21
22 {{figure}}
23 [[image:geplanter System-Scan.PNG]]
24
25 {{figureCaption}}
26 Settings for a scheduled system scan
27 {{/figureCaption}}
28 {{/figure}}
29
30 With the scheduled full system scan, you can set when and how the scan should run, so that it can be customised to all other processes on the Clients. This helps to avoid an almost full CPU load and thus the restriction of other tasks.
© Aagon GmbH 2025
Besuchen Sie unsere neue Aagon-Community