Wiki source code of Monitore

Last modified by Sabrina V. on 2025/02/28 08:54

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	60
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
24.1	7	In each plug-in, you will find the Monitors tab in the ribbon bar. The various monitors provide you with a quick overview of the status of jobs, clients, server jobs, emails and synchronisations of the file repositories.
1.1	8
24.1	9	= Job Monitor =
1.1	10
24.1	11	The Job Monitor shows you all the jobs that are pending on your clients, have already been successfully run or have failed.
1.1	12
	13	{{figure}}
	14	[[image:64_Monitore_Jobmonitor Übersicht_2112.png]]
	15
	16	{{figureCaption}}
24.1	17	Job Monitor
1.1	18	{{/figureCaption}}
	19	{{/figure}}
	20
24.1	21	In principle, this monitor can be filtered according to three contents:
1.1	22
24.1	23	* Date (All, Today, Yesterday, Last 7 days, Last 14 days, Last 30 days)
	24	* Type of job (kiosk, container, OS installer, pushed, RunCC)
	25	* Content or topic of the respective job (ACMP Agent, ACMP Agent Installation, ACMP Gateway, Client Commands, Defender Management, Intune Action, Job Collection, Managed Software, Manual Agent Job, Rollout, Windows Update, Windows Update Collection).
1.1	26
24.1	27	By default, the results of the last 7 days are filtered.
1.1	28
24.1	29	The individual job executions are listed in the overview. The name of the job and the type are displayed first. The //job status// gives you a direct overview of the current stage of the job and the //container path// to which the job belongs. The exact //date of the last execution//, the number of Clients affected by this job and the number of executions that failed, were successful and are finished are then displayed. The //job type// reflects the content of the job. In addition, the start condition of the job set in the containers, the distribution ring and the number of possible ACMP licenses imported are displayed.
1.1	30
24.1	31	If you double-click on a job in the job listing, you will get more detailed information about the executions.
1.1	32
	33	{{figure}}
	34	[[image:64_Monitore_Jobmonitor Jobebene_2112.png]]
	35
	36	{{figureCaption}}
24.1	37	A specific job execution
1.1	38	{{/figureCaption}}
	39	{{/figure}}
	40
24.1	41	You will see an overview of how the Default Defender job, for example, was executed on the selected Clients that have been assigned to a Container.
1.1	42
24.1	43	There are 6 statuses:
1.1	44
24.1	45	\|Status\|Meaning
	46	\|Awaiting\|The job has been created and execution is scheduled.
	47	\|Received\|The jobs were sent to Clients and received by them.
	48	\|Deplayed\|The job received by Clients was postponed by the user to a later point in time.
	49	\|Started\|The job received by Clients was started in line with the start conditions and is currently being executed.
	50	\|Finished\|The started job has been finished and the results are available.
	51	\|Cancelled\|The started job was aborted during execution due to an error or manually by the user.
1.1	52
	53	{{aagon.infobox}}
24.1	54	Please note that when an Intune action is executed, the status is also //finished// if, for example, the message has not yet arrived at the end device. The //finished// status is displayed in the Job Monitor as soon as the action has been executed by ACMP.
1.1	55	{{/aagon.infobox}}
	56
24.1	57	This order of statuses is also followed during the execution of a job.
1.1	58
24.1	59	An overview of the results of the jobs on the selected Clients is displayed under //Last Results//. There are 4 statuses:
1.1	60
24.1	61	\|Result\|Causes
	62	\|Failed\|The job was executed, but the defined actions could not be completed successfully due to one or more errors.
	63	\|Successful\|The job has been executed and the defined actions have been successfully carried out.
	64	\|Skipped\|The job has been executed and there is no error, but the defined actions have been skipped because the intended target of the action is already present. So it would be possible to carry out the action, but it is not necessary.
	65	\|Without license\|The job was executed, but the defined actions could not be successfully completed because one or more of the actions requires a specific ACMP license that you do not have.
1.1	66
24.1	67	If this job execution has failed, you can click again on the listing to display the log entries with error messages.
1.1	68
	69	{{figure}}
	70	[[image:64_Monitore_Jobmonitor Log_1440.png]]
	71
	72	{{figureCaption}}
24.1	73	Log entries for a failed job
1.1	74	{{/figureCaption}}
	75	{{/figure}}
	76
	77
24.1	78	= Client Monitor =
1.1	79
24.1	80	The Client Monitor allows you to view all or selected clients that are to execute or have already executed jobs from the client's point of view.
1.1	81
	82	{{figure}}
	83	[[image:63_Solution_Clientmonitor Übersicht_2112.png]]
	84
	85	{{figureCaption}}
24.1	86	Client Monitor
1.1	87	{{/figureCaption}}
	88	{{/figure}}
	89
24.1	90	In principle, this monitor can be filtered according to 3 contents:
1.1	91
24.1	92	* Date (All, Today, Yesterday, Last 7 days, Last 14 days, Last 30 days)
	93	* Type of job (Kiosk, Container, OS Installer, Pushed, RunCC)
	94	* Content or subject of the respective job (ACMP Agent, ACMP Agent Installation, ACMP Gateway, Client Commands, Defender Management, Job Collection, Managed Software, Manual Agent Jobs).
1.1	95
24.1	96	By default, the results for the last 7 days are filtered.
1.1	97
24.1	98	Each client is listed in the summary. Firstly, the computer name and the exact date of the last execution on the client are displayed. This is followed by the number of previous executions on the client, including completed, successful and failed. It also shows the type of job that was run on the client, the associated distribution ring in which the job was started and any associated ACMP licence.
1.1	99
24.1	100	Double-clicking on a client in the list will give you an overview of how, for example, the Default Defender job was run on the selected clients.
1.1	101
	102	{{figure}}
	103	[[image:63_Solution_Clientmonitor Clientebene_2111.png]]
	104
	105	{{figureCaption}}
24.1	106	All executions of a single Client
1.1	107	{{/figureCaption}}
	108	{{/figure}}
	109
24.1	110	There are 6 statuses:
1.1	111
24.1	112	\|Status\|Meaning
	113	\|Awaiting\|The job has been created and execution is scheduled.
	114	\|Received\|The jobs were sent to Clients and received by them.
	115	\|Deplayed\|The job received by Clients was postponed by the user to a later point in time.
	116	\|Started\|The job received by Clients was started in line with the start conditions and is currently being executed.
	117	\|Finished\|The started job has been finished and the results are available.
	118	\|Cancelled\|The started job was aborted during execution due to an error or manually by the user.
1.1	119
24.1	120	This order of statuses is also applied during the execution of a job on the client.
1.1	121
24.1	122	An overview of the results of the jobs on the selected clients is displayed under //Last Results//. There are 4 statuses:
1.1	123
24.1	124	\|Result\|Causes
	125	\|Failed\|The job was executed, but the defined actions could not be completed successfully due to one or more errors.
	126	\|Successful\|The job has been executed and the defined actions have been successfully carried out.
	127	\|Skipped\|The job has been executed and there is no error, but the defined actions have been skipped because the intended target of the action is already present. So it would be possible to carry out the action, but it is not necessary.
	128	\|Without license\|The job was executed, but the defined actions could not be successfully completed because one or more of the actions requires a specific ACMP license that you do not have.
1.1	129
24.1	130	If this client execution has failed, you can double-click the entry again in the list to display the log entries with error messages.
1.1	131
	132	{{figure}}
	133	[[image:64_Monitore_Jobmonitor Log_1440.png]]
	134
	135	{{figureCaption}}
24.1	136	Log entries for failed client jobs
1.1	137	{{/figureCaption}}
	138	{{/figure}}
	139
24.1	140	= Server Monitor =
1.1	141
	142	{{aagon.versionierungsbox}}
24.1	143	Please note that the Server Monitor is available in ACMP version 6.4 and higher.
1.1	144	{{/aagon.versionierungsbox}}
	145
24.1	146	The Server Monitor provides you with an overview of the tasks that the server performs in the background.
1.1	147
24.1	148	These server jobs include background processes, e.g. calculations of which Clients are dynamically assigned to which container, cleanup of old WUM logs or updates of MSW packages.
1.1	149
24.1	150	Most of the tasks can be found in the scheduled server tasks; however, some other background processes are also listed that cannot be found and controlled in the settings. Scheduled server tasks can also be executed manually from the server monitor.
1.1	151
	152	{{figure}}
	153	[[image:64_Servermonitor_Übersicht.png]]
	154
	155	{{figureCaption}}
24.1	156	Server Monitor
1.1	157	{{/figureCaption}}
	158	{{/figure}}
	159
24.1	160	In principle, this monitor can be filtered according to three contents:
1.1	161
24.1	162	* Date (All, Today, Yesterday, Last 7 days, Last 14 days, Last 30 days)
	163	* Type of job (All, Planned, Manual)
	164	* Category of the respective server job (General, Defender Management, Client Commands, Helpdesk, Licence Management, Vulnerability Management, Windows Update Management, Managed Software).
1.1	165
24.1	166	By default, the filter shows results from the last 7 days.
1.1	167
24.1	168	The individual job descriptions are listed in the overview. Each job is assigned to a category that corresponds to the categories of the planned server tasks. The type indicates how the job was executed: planned or executed manually. The job status shows you the current status of the execution: running or finished. The last result shows you the result of the last execution, whether the execution was successful or failed. Then the total number of scheduled executions is displayed and how many of them have been successful or failed. The start condition shows you the interval at which the server job is executed.
1.1	169
	170	{{aagon.infobox}}
24.1	171	Please note that the start conditions can only be set in the Scheduled Server Tasks and not in the Server Monitor.
1.1	172	{{/aagon.infobox}}
	173
24.1	174	You can get an overview of the executions of a particular job by double-clicking on a job. In addition to general job information and a status chart, all executions of this job in the last 30 days are displayed.
1.1	175
	176	{{figure}}
	177	[[image:64_Minitore_Servermonitor_Ausführungsebene_2069.png]]
	178
	179	{{figureCaption}}
24.1	180	All executions of a specific Server job
1.1	181	{{/figureCaption}}
	182	{{/figure}}
	183
	184	{{aagon.infobox}}
24.1	185	By default, all executions older than 30 days are deleted from the Server Monitor Log Cleanup scheduled server task. Note that the interval can be changed as required in the Scheduled Server Tasks.
1.1	186	{{/aagon.infobox}}
	187
24.1	188	If an execution fails, you can view the execution log by double-clicking on the execution. The log will contain a more detailed error message explaining why the execution failed.
1.1	189
24.1	190	= Email Monitor =
1.1	191
24.1	192	The Email Monitor displays any emails that the system has yet to send. If emails cannot be sent, for example because the mail server is offline, they will remain in this queue.
1.1	193
24.1	194	You can delete them by selecting the emails and clicking the //Delete Emails //icon.
1.1	195
	196	{{figure}}
	197	[[image:63_Solution_E-Mailmonitor_1736.png]]
	198
	199	{{figureCaption}}
24.1	200	Emails in queue
1.1	201	{{/figureCaption}}
	202	{{/figure}}
	203
	204	{{figure}}
	205	{{figureCaption}}
	206
	207	{{/figureCaption}}
	208	{{/figure}}
	209
24.1	210	= Sync Monitor =
1.1	211
24.1	212	The Sync Monitor provides an overview of all file repositories on the network and the status of data synchronisation.
1.1	213
	214	{{figure}}
	215	[[image:63_Solution_Syncmonitor_1667.png]]
	216
	217	{{figureCaption}}
24.1	218	Sync Monitor
1.1	219	{{/figureCaption}}
	220	{{/figure}}
	221
24.1	222	The file repositories are listed by type (Client Command/Client Update/OS Deployment), with the date and status displayed below each type. The status indicates how far the synchronisation process has progressed.
1.1	223
24.1	224	The data displayed can be updated directly by clicking the //Refresh// button.
1.1	225
24.1	226	The //Start Sync// and //Stop Sync// buttons can be used to pause and resume synchronisation of the selected file repositories. When resuming a paused synchronisation, a dialogue box allows you to specify whether only new data or all data from the first synchronisation should be transferred.