Wiki source code of Konfigurationsprofile

Last modified by Jannis Klein on 2024/08/13 07:31

version	line-number	content
1.1	1	{{aagon.priorisierung}}
	2	10
	3	{{/aagon.priorisierung}}
	4
	5	{{aagon.floatingbox/}}
	6
2.1	7	Configuration Profiles allow you to set Defender settings on the client, such as controlling update and scan behaviour or defining the user interface.
	8	The ACMP contains default configuration profiles. These are not assigned to any Client by default and can be assigned in a number of ways.
	9	If you want to set different settings from the default profile, you can edit it or create a completely new configuration profile.
1.1	10
	11	{{aagon.infobox}}
2.1	12	Note that the configuration profile provided is a default profile defined by Microsoft for Defender Management.
1.1	13	{{/aagon.infobox}}
	14
2.1	15	= Working with Configuration Profiles =
1.1	16
2.1	17	== Assigning Configuration Profiles to Clients ==
1.1	18
	19	{{aagon.infobox}}
2.1	20	Please note that query actions in Defender Management, such as antivirus scans or initiating an update scan, can only be performed if a Configuration Profile is assigned to the Client!
1.1	21	{{/aagon.infobox}}
	22
2.1	23	There are 2 ways to assign Configuration Profiles to your Clients.
1.1	24
2.1	25	~1. By explicit assignment
	26	This assignment is done via a query. To do this, select the required Clients, click on the Defender icon in the query actions bar and go to //Assign Defender Configuration Profile//. A dialogue will open allowing you to select the required configuration profile. By default, the configuration profile assignment can be overridden by a container. If this is not desired, you can deselect this option.
	27	Click //Execute //to complete the assignment. The Job Monitor displays the status of the association.
1.1	28
2.1	29	2. Via an automatic container association
	30	In the Container plug-in, select a container or create a new one, then switch to the //Defender Management// tab. Either click //Assign// in the ribbon bar or the link //Click to assign a Configuration Profile//. Any Client assigned to a Container with a Configuration Profile assignment will automatically receive the Configuration Profile.
1.1	31
	32	{{aagon.infobox}}
2.1	33	Please note that only one Configuration Profile can be assigned to each Client! If a Client is assigned to more than one Container, the Client will receive the Configuration Profile from the Container with the highest priority. If you are also using Multi-Tenancy, the Global Containers are assigned above the Client Containers.
1.1	34	{{/aagon.infobox}}
	35
2.1	36	== Behaviour in the Container ==
1.1	37
2.1	38	You can see whether a Configuration Profile has been assigned to a Container, and to which Container, by looking at the Defender icon. To do this, go to the //Container// plug-in. You will see a list of all existing Containers. A Defender icon will appear in the //Properties// column if a configuration profile has been assigned to that container.
1.1	39
2.1	40	The Defender icon can be displayed in two colours:
1.1	41
2.1	42	~1. As a blue icon:
	43	The Container is directly associated with a Configuration Profile.
1.1	44
2.1	45	2. As a grey icon:
	46	The container has an inherited association. This means that all child containers inherit the configuration profile of the parent container.
1.1	47
2.1	48	You have the option of overriding this inheritance if necessary. To do this, click //Cancel// in the ribbon bar. If you wish to undo this action, click //Revert//.