Wiki source code of Agentenplaner

Last modified by Jannis Klein on 2024/08/13 08:19

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	80
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
2.1	7	The Agent Tasks configure all the scanning and maintenance options for working on the ACMP Clients. Here you can define the intervals at which the scanners should run. You can also change the start conditions and enable/disable settings. The Client Actions can also be used to push individual scanners to the Agent independently of the selected start interval.
1.1	8
2.1	9	It is possible to create almost any number of Agent scheduler templates with their own start conditions for groups of computers.
1.1	10
	11	{{figure}}
	12	(% style="text-align:center" %)
2.1	13	[[image:63_ClientManagement_Agentenplaner1351.png]]
1.1	14
	15	{{figureCaption}}
2.1	16	Agent Tasks
1.1	17	{{/figureCaption}}
	18	{{/figure}}
	19
2.1	20	The Agent Scheduler is divided into two sections, Agent Tasks and Maintenance. The Agent Tasks section contains the scanners that read information from the Clients. The Maintenance section contains the scanners that enable Agent configurations. If you have many Clients in use, the settings in the Agent Tasks section are particularly important to avoid overloading the ACMP Server.
1.1	21
	22	{{aagon.infobox}}
2.1	23	The scanners run serially and can only be run one after the other, not simultaneously. Take this into account when working as it may cause delays in execution.
1.1	24	{{/aagon.infobox}}
	25
2.1	26	\|Agent Tasks\|Description\|Special Features
	27	\|Defender Scanner\|Collects Microsoft Defender scan results and status information
	28	\\Examples:
	29	- Quarantine information
	30	- Signature version and signature age
	31	- Event log items of Defender\|The Defender Scanner collects various info about the installed Windows Defender. The Defender Scanner is activated when you go through and exit the First Step Wizard of Defender Management. In addition, you can configure which Event types are to be inventoried. By default, "Information" is disabled because the database would otherwise grow unnecessarily due to the many event messages.
	32	\|File Scanner\|Searches your Clients for files
	33	\\File types:
1.1	34	- .exe
	35	- .dll
	36	- .sys
2.1	37	- .jar\|With the file scanner it is possible to read out software on the Clients that has not been installed in the classical way (e.g. in-house developments). You can then use this, for example, in License Management. You will find configuration options for this under the [[settings>>doc:ACMP.65.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome\|\|anchor="HACMPTask"]].
	38	\|Hyper-V Scanner\|Scans your Clients for Hyper-V Guests\|With the help of the scanner, the guests are read from the Hyper-V host. The difference criterion for unique identification can be made in the settings (Verlinkung). In addition, guests can be excluded via a block list.
	39	\|Managed Software Scanner\|Scans your Clients for Managed Software\|The Managed Software Scanner scans the Managed Software installed on the Client. With the scan function, the ACMP Server determines a possible deficit between the installed version and the available version that the Client has installed.
	40	\|Rule Scanner\|Checks the rules assigned to the Clients\|You can use the Rule Scanner to find specific files, registry keys and values on the Client. Please note that a search of an entire drive may take a long time for the scanner to complete.
	41	\|Security Scanner\|Scans the Windows Security Center\|The data of the Windows Security Center ("Windows Security") is read out and passed on to ACMP. Here you can display the info as to whether the settings, parameters and antivirus solutions are still up to date.
	42	\|Software Scanner\|Scans MSI / setup software and store apps and, if required, user-specific software\|The scanner reads out the installed software listed under "Control Panel and Programs". The scan function gives you exact details about what software is installed on the Clients. You can specify under the [[settings >>doc:ACMP.65.ACMP-Solutions.System.Einstellungen.ACMP Agent.WebHome\|\|anchor="HACMPTask"]]which items are to be ignored by the software scanner. User-specific software can also be read out. Note that Updates and System Components are disabled by default, as this would cause many items to be read out for the Clients.
	43	\|System Scanner\|Scans hardware information of the machine
	44	\\Examples:
	45	- Computer name
	46	- Computer domain
	47	- Hard disk allocation
	48	- Network cards\|This is relevant, for example, if you change the computer name during operation and it has not yet been updated in ACMP. The new name would only be recorded and displayed after the computer scanner has run through.
	49	\|Vulnerability Scanner\|Scans the Client for existing vulnerabilities\|The vulnerability scanner updates the vulnerability definition file. The file is used to check whether vulnerabilities exist on the Client.
	50	\|Windows Updates Scanner\|Scans already installed and pending Windows Updates of the machine\|The Windows Update Scanner scans the Clients for already installed and pending Windows Updates.
	51	\|Maintenance\| \|
	52	\|ACMP Agent Update/installation time frame\|Agents are allowed to install ACMP Updates during this time window.\|The time window can be used to configure when an Update can be installed for the Agent.
	53	\| \| \|
	54
	55	{{aagon.infobox}}
	56	We recommend that you do not change this setting, as the default setting guarantees a 24/7 update/installation window and an incorrect configuration may prevent an update and thus disrupt the communication between the ACMP Server and the ACMP Agent. Please note that the Agent update can also be performed during normal business hours without any problems.
	57	{{/aagon.infobox}}
	58
	59	\|Restart ACMP Agent\|Restarts the ACMP Agent\|This maintenance option allows you to restart the ACMP client service. Also note that this job triggers the start condition "ACMP Agent Start".
	60	\|Settings Watch\|Updates the Client Task Settings for the Client\|Updates the scan intervals of the Agent Tasks and the file repositories. If you change the conditions of the scanners in the Agent Tasks (e.g. the conditions of a point in time), the settings are updated after the defined interval.
	61	\|Update Defender Configuration Profiles\|Sets the settings of the Defender Configuration on the Clients and updates them if necessary.\|The Defender Scanner applies or updates the configurations according to assigned configuration profiles.
	62	\|Update Jobs & Configuration Profiles\|(((
	63	Queries the ACMP Server for the Jobs unassigned to it.
	64	\\Examples:
1.1	65	- Container Jobs
2.1	66	- Pending pushed Jobs
	67	)))\|During the execution of the Job Scanner, all Jobs assigned to the Client and pending are determined. This includes the Jobs that have been linked via a container, but also those that have been pushed to the Client but not yet received. For Clients that are in the home office and cannot be reached by the ACMP Server, we recommend using a short interval. This enables prompt execution of pushed Jobs.
1.1	68
2.1	69	In front of each setting you can see whether it is an active task ([[image:image-20220519131909-1.png]]) or an inactive task ([[image:grafik.png]]).
1.1	70
2.1	71	ACMP comes with a default template. If you do not assign a custom template via the container, the default template will be used. You can create and configure as many templates as you like; the assignments to Clients are made via the Containers. You can also create Client-specific templates that are based on individual Agent Scheduler templates for a single Client. For example, you can use different templates to map the settings and requirements of mobile devices and fixed workspaces on the local network.
1.1	72
2.1	73	To switch between different templates, you can use the pull-down menu and select the required template.
1.1	74
2.1	75	= Manage templaes =
1.1	76
2.1	77	The ribbon bar allows you to add ([[image:image-20220519131940-3.png]]), rename ([[image:clock-edit.png\|\|alt="grafik.png" height="16" width="16"]]) or delete ([[image:image-20220519131940-5.png\|\|height="16" width="16"]]) templates. Settings can be taken from a template to be selected.
1.1	78
	79	{{figure}}
	80	(% style="text-align:center" %)
2.1	81	[[image:ACMP_63_Agentenplaner_Vorlage_erstellen_%971.PNG]]
1.1	82
	83	{{figureCaption}}
2.1	84	Create a new template
1.1	85	{{/figureCaption}}
	86	{{/figure}}
	87
	88
2.1	89	== Configururing templates ==
1.1	90
2.1	91	If you want to change the settings of the different start conditions in the Agent Tasks, double-click on the desired job and a dialogue window opens.
1.1	92
	93	{{figure}}
	94	(% style="text-align:center" %)
2.1	95	[[image:ACMP_63_Agentenplaner_Einstellungen_ändern_%820.PNG]]
1.1	96
	97	{{figureCaption}}
2.1	98	Start condition
1.1	99	{{/figureCaption}}
	100	{{/figure}}
	101
2.1	102	= Start conditions =
1.1	103
2.1	104	First specify whether the task should be active or inactive. Check the //Activated// checkbox if you want to change the start conditions.
1.1	105
2.1	106	In addition to the activated start conditions, you can also define the network connection options. Using the network connection options, you can also define whether the scanner should take metered connections into account and therefore not start the scanner. Next, find the start condition you want the scanner or maintenance to follow.
1.1	107
2.1	108	The start conditions specify when the job is to be executed. For some conditions you can specify specific dates, for others you can define the specific actions while working on the service.
1.1	109
2.1	110	Recurring elements:
1.1	111
2.1	112	* Execute only within the time window: Here you can define a self-specified time window in which the task is to be carried out. The time window allows you to specify both hours and minutes.
1.1	113
	114	{{aagon.versionierungsbox}}
2.1	115	Please note that the checkbox "Execute once" is no longer available in ACMP from version 6.3.
1.1	116	{{/aagon.versionierungsbox}}
	117
2.1	118	\|Start condition\|Explanation
	119	\|ACMP Agent start\|- Executions are executed when the ACMP Agent is started (manually via service management or restarting the machine).
	120	\\- The condition is also executed via the maintenance option "Restart ACMP Agent".(((
	121	* Example: The cumputer is restarted.
1.1	122	)))
2.1	123	\|As soon as possible\|- With the settings, the task is executed as soon as possible.
	124	- Note that this start condition implies a single execution!
	125	\|Date interval\|- Dynamically calculated times can be defined during execution.(((
	126	* Example: The first day of the month.
1.1	127	)))
2.1	128	\|Day of month\|- The condition is executed on all the days you specify in the month. Executions are only executed in months with the selected days.
	129	\|Day of week\|- Executions are started when you specify one or more days of the week. In addition, there is the option that every nth day of a month should be taken into account.
	130	\|Last day of every month (deprecated)\|- The scanner is executed on the last day of each month.
	131	Please note that this is a deprecated start condition. We recommend that you use the "Date inverval" setting instead.
	132	\|Login\|- The condition is executed as soon as a user logs on to the system or terminal server.(((
	133	* Example: The user logs on to the computer.
1.1	134	)))
2.1	135	\|Shut down\|- The start condition is executed when the Client is shut down. For this purpose, the user is first logged off and only then are the Jobs executed.(((
	136	* Special feature: Commands that run in the user context are not executed (e.g. all commands of the category Dialogs, as well as Lock manual input, Unlock manual input, Get idle time, Lock workstation, Get/Set default printer and If user is (not) in group).
1.1	137	)))
2.1	138	\|Specific date\|- You can only run the scanner on a specific date by specifying a date.
	139	\|Specific time\|- The condition is executed daily at a specific time that you can set.
	140	\|Start interval\|- Within the start condition you can define an interval (minutes, hours, days) when the task should always start.
	141	- Note that the start behavior of random time windows is only available with the interval setting "days"
	142	\|Start time\|- Executions begin with the start date, which you can specify. You can also specify a finish date, which means that there is no automatic refresh of the data when the date is reached.
	143	\|Time frame\|- A specific time slot with a start and end time can be set.
1.1	144
2.1	145	Finally, save your changes so that the scanners or maintenance tasks can start under the new start conditions. Note that the start conditions are updated on the Client when the scanner has run through "Update settings".
1.1	146
2.1	147	== Special behaviour of the start conditions ==
1.1	148
	149	{{aagon.infobox}}
2.1	150	Please note a special behaviour for the "Time Window" option. If you use this in combination with the start conditions "Day of week", "Day of month" or "Specific date" and the time window extends beyond one day (e.g. 22:00 - 02:00), the Client Task would only be executed on this specific date. This also applies if the time window still extends into the next day. Therefore, always check the date first and only then the time window. For example, if you want to execute a scanner only in the evening, it would run until 23:59, but not until the actual end of the specified time window.
1.1	151	{{/aagon.infobox}}
	152
	153	{{aagon.infobox}}
2.1	154	In the start conditions "Start interval" and "Time frame" there is the option "Start at a random time within the time window". We recommend that you use this start condition. This ensures that the scan data is sent to the Server at a staggered time. If many scan data are sent at the same time, the import may only be carried out with a time delay.
1.1	155	{{/aagon.infobox}}
	156
	157
2.1	158	= Assigning an Agent Scheduler template from a Container =
1.1	159
2.1	160	If you have already created a container, you can also assign an Agent Scheduler template to it from the details view. You can find the currently assigned Agent Scheduler template via the //Agent Tasks// category of the same name. This can be changed using either the ribbon buttons or the context menu.
1.1	161
2.1	162	Note that priority determines which template is used by the Client. If the Client is in more than one Container, the template from the Container with the highest priority will always be used. This has to be taken into account when assigning and, if necessary, adjusted in the priority of the container.
1.1	163
	164	{{figure}}
	165	(% style="text-align:center" %)
2.1	166	[[image:ACMP_63_Agentenplaner_Container_%.PNG]]
1.1	167
	168	{{figureCaption}}
2.1	169	Unassigned Agent Planner Template
1.1	170	{{/figureCaption}}
	171	{{/figure}}
	172
	173	{{aagon.infobox}}
2.1	174	When Multi-Tenancy is enabled, the Global Containers have a higher weighting than the Client Containers.
1.1	175	{{/aagon.infobox}}
	176
2.1	177	= Individual Agent Planer Template via the Client Details =
1.1	178
2.1	179	Via the Client Details, you can enable an individual agent template that specifically applies only to the selected Client. The template has the highest priority and takes effect before assignments via containers. Navigate to the //Software// > //Computer// > //Agent// //Tasks// menu item under the Client Details and check the Enable //Client-Specific Template// checkbox to make individual changes to the template.
1.1	180
2.1	181	Once you have enabled the template and configured it appropriately, save the changes and the agent will reflect the custom agent scheduler template after the "Update Settings" scanner is executed.
1.1	182
	183	{{figure}}
	184	(% style="text-align:center" %)
2.1	185	[[image:ACMP_63_Agentenplaner_Client_Details_%.PNG]]
1.1	186
	187	{{figureCaption}}
2.1	188	Client specific template
1.1	189	{{/figureCaption}}
	190	{{/figure}}
	191
2.1	192	= Ability to check Executions =
1.1	193
2.1	194	Using the "ACMP Agent Statuses" Query, you can check when a scanner last ran and whether the inventoried data has been updated.
1.1	195
	196	{{figure}}
	197	(% style="text-align:center" %)
2.1	198	[[image:ACMP Agent Statuses.PNG]]
1.1	199
	200	{{figureCaption}}
	201	ACMP Agent Statuses
	202	{{/figureCaption}}
	203	{{/figure}}
	204
2.1	205	= Customize System Settings for Agent Tasks =
1.1	206
2.1	207	In the System Settings you can adjust the settings for the software and file scanner for the Agent Tasks. To do this, navigate in the ACMP Console to //System// > //Settings// > //ACMP// //Agent// > //Agent// //Task//.
1.1	208
	209	{{figure}}
	210	(% style="text-align:center" %)
	211	[[image:63_SystemEinstellungen_ACMPTask_Scanner_748.png]]
	212
	213	{{figureCaption}}
2.1	214	Scanner settings
1.1	215	{{/figureCaption}}
	216	{{/figure}}
	217
	218	{{aagon.infobox}}
2.1	219	Please note that Updates and System Components create many items in the database. Unless this information is needed, we recommend that you leave the default configurations set.
1.1	220	{{/aagon.infobox}}
	221
	222	{{aagon.infobox}}
2.1	223	You can customize the hard disk usage to allow the computer to continue working during the scan.
1.1	224	{{/aagon.infobox}}