Changes for page Container verwalten

Last modified by Sabrina V. on 2025/08/04 09:52

From 1.1 to 2.1

From version 2.1

edited by Sabrina V.
on 2024/10/23 05:41

Change comment: There is no comment for this version

To version 4.1

edited by Sabrina V.
on 2025/08/04 09:52

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,93 +5,130 @@
--{{aagon.priorisierung}}
--10
--{{/aagon.priorisierung}}
--
  {{aagon.floatingbox/}}
--= Manage Containers =
++(% class="wikigeneratedid" id="HContainerverwalten" %)
++The ribbon bar allows you to add containers ([[image:Container hinzufügen Icon.png]]), edit them ([[image:Container bearbeiten Icon.png||height="“18”" width="18"]]), delete ([[image:Container löschen Icon.png||alt="image:Container löschen Icon.png"]]) or duplicate ([[image:Container duplizieren Icon.png]]) existing containers.
++
--You can use the ribbon bar to add Containers  ([[image:Container hinzufügen Icon.png]]), edit them ([[image:Container bearbeiten Icon.png||height="18" width="18"]]), delete them ([[image:Container löschen Icon.png]]) or duplicate existing Containers ([[image:Container duplizieren Icon.png]]). Proceed as follows:
++[[Manage containers>>image:68_Container verwalten_.png||alt="“Manage"]]
--== Creating a Container ==
++= Create container =
--A wizard will open where you must first select the output directory where the new Container will be stored. Then give it a name and select a network status. The network status determines whether the linked Jobs will be executed on the Client. For this to happen, the network status of the Container must match that of the Client. Select the //Allow multiple occurrences of the same Client in sub-Containers// checkbox if you want to allow a Client to occur more than once in this Container and its sub-Containers.
++To create a new container, you must select the corresponding button in the ribbon bar ([[image:Container hinzufügen Icon.png]]). Please note that starting with ACMP 6.8, you must select which operating system family the container should support when creating containers. A wizard opens to guide you through the creation of the container.
--Multiple occurrences also determine the Use Case of the Container:
++=== General ===
--(% style="width:1135px" %)
--|**Example**|**Description**|(% style="width:124px" %)**Enable option**
--|Scan Templates|If you are creating a Container structure to check which Clients have logged on to your Server locally or mobile, you must not enable this option. A Client cannot be both mobile and local at the same time, so multiple occurrences in the Containers will be incorrect.|(% style="width:124px" %)No
--|Software maintenance|If you want to manage the software via the Containers, it is advisable to allow multiple occurrences. This allows a Client to be assigned to multiple Containers with different software jobs.|(% style="width:124px" %)Yes
--|Site structure|If you have multiple sites and want to map the structure of the company using the Containers, this option must not be selected. A Client cannot be in two different locations at the same time.|(% style="width:124px" %)No
--|Updates|If you want to distribute Updates (e.g. Windows, Microsoft or Office Update) you should enable this option as all Clients may receive different updates. In this case it is advisable to allow multiple occurrences in the Containers.|(% style="width:124px" %)Yes
++1. Select the output directory where the new container should be stored.
++1. Assign a name to the container.
++1. Select the //Allow multiple occurrences of the same client in subordinate containers// checkbox if you want to allow a client to appear more than once in this container and in the subcontainer.{{aagon.infobox}}Please refer to the example use cases for multiple occurrences in the table below.{{/aagon.infobox}}
++1. Under //Operating system family//, specify whether the container is to be used for managing Windows Clients or Unix Clients (Linux & macOS).{{aagon.warnungsbox}}The operating system family can only be specified once. It cannot be changed after the container has been created.{{/aagon.warnungsbox}}
++1. Under //Client restrictions//, specify whether only clients of the selected operating system family can be linked to the container or whether all clients should be allowed to be linked.
++1. Under //Distribution ring//, specify the distribution ring in which jobs linked to the container should be executed.
++1. Finally, select a network status. The network status determines whether linked container settings are applied to clients if the network status of the container does not match the network status of the clients.
--{{aagon.warnungsbox}}
--The //Allow multiple occurrences of the same Clients in child Containers// option cannot be changed retrospectively. If you have forgotten to enable this setting, you will need to create a new Container, take this option into account, and delete the old Container.
--{{/aagon.warnungsbox}}
++[[Create container - General>>image:68_Container erstellen.png]]
--You can also specify which Distribution Ring should be used to deploy the Managed Software and/or Windows Update Management to the Clients within the Container. To do this, select the distribution ring to be used (Test Ring 1 and Test Ring 2).
++The //Multiple occurrences// option additionally determines the use case of the container:
--Optionally, you can select an icon for the Container. To do this, click //Assign// and find a suitable icon. Continue working through the wizard and click //Next >// to move to the next page.
++(% style="width:1096px" %)
++|**Example**|(% style="width:818px" %)**Description**|(% style="width:151px" %)**Enable option**
++|Scan templates|(% style="width:818px" %)If you create a container structure with which you want to check which Clients have logged on to your Server locally or via mobile, you must not enable this option. A Client cannot log back in locally and via mobile at the same time, which means that multiple occurrences in the containers are incorrect.|(% style="width:151px" %)
++No
++|Software maintenance|(% style="width:818px" %)If you want to manage the software via the containers, it is advisable to allow multiple occurrences. This allows a client to be assigned to several containers with different software jobs.|(% style="width:151px" %)Yes
++|Location structure|(% style="width:818px" %)If you have multiple locations and want to use containers to map the structure of your company, this option must not be activated. A client cannot be at two different locations at the same time.|(% style="width:151px" %)No
++|Updates|(% style="width:818px" %)If you want to distribute updates (e.g. Windows, Microsoft or Office Update), you should enable this option, as all clients may receive different updates. In this case, it is advisable to allow multiple occurrences in the containers.|(% style="width:151px" %)Yes
--{{aagon.infobox}}
--If multi-tenancy is enabled and you want to create the Container at root level, you can now specify whether it is a global Container. Otherwise you can skip this page.
++{{aagon.warnungsbox}}
++The option Allow multiple occurrences of the same client in subordinate containers cannot be changed later. If you forget to enable this setting, you will have to create a new container, enable this option, and delete the old container.
++{{/aagon.warnungsbox}}
--**The Container is Global**: All Clients listed in the Container can be associated with the Container.
--**There is a Container-Client relationship**: You can specify which Clients should be associated with the Container.
--{{/aagon.infobox}}
++Click //Next >// to proceed to the next page. // //
--{{figure}}
--[[image:66_Container hinzufügen_Allgemein_907.png||data-xwiki-image-style-alignment="center"]]
++=== Optional information ===
--{{figureCaption}}
--Container Details
--{{/figureCaption}}
--{{/figure}}
++1. Enter a description if required
++1. Optionally, select an icon for the container. To do this, click //Assign //and find a suitable icon.
--In the next step of the wizard, you define the rules for the dynamic Client links. Here you use filters to determine (search) criteria according to which the Clients are dynamically linked to Containers. You can find continuing info on setting up filters in the [[Set up filters>>doc:ACMP.67.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.Filteroptionen anwenden.WebHome]] section.
++Click //Next >// to proceed to the next page. // //
--The basis of the dynamic Client links are the different [[filter modes>>doc:.Arbeiten mit den Filtertypen.WebHome]] that you can select. For example, you can create an advanced SQL query (Advanced SQL Filter) (Verlinkung), display the results according to the Tree Filter (Note: this view is deprecated), or create a Container to include only Clients with specific vulnerabilities (Vulnerability Filter). Select the appropriate mode and [[create a query>>doc:ACMP.67.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.WebHome]] according to your criteria and click //Next >//.
++=== Dynamic client link ===
++In the next step of the wizard, you define the rules for the dynamic client links.
++
  {{aagon.infobox}}
--If you are using a static Container, you do not need to make any settings here and can skip this step in the wizard.
++If you want to use a static container, you do not need to make any settings here and can skip this step in the wizard.
  {{/aagon.infobox}}
--{{figure}}
--[[image:66_Container_Dynamische Clientverknüpfung_993.png||data-xwiki-image-style-alignment="center"]]
++Here you use filters to define specific (search) criteria according to which the clients are dynamically linked to containers. For more information on setting up filters, see the section [[Setting up filters>>doc:ACMP.67.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.Filteroptionen anwenden.WebHome]].
--{{figureCaption}}
--Dynamic Client assignment
--{{/figureCaption}}
--{{/figure}}
++{{aagon.warnungsbox}}
++The dynamic links are overwritten by the client restrictions from the first configuration page “General”. Depending on the client restriction settings, clients of the unselected operating system family may therefore not be linked.
++{{/aagon.warnungsbox}}
--In the final step of the wizard you will be shown a preview of the results of the query you have created. When you click //Finish//, the Container is created. Further settings can be made in the detail view (including adding static Cients).
++[[Create container - Dynamic client link>>image:68_Dynamische Clientverknüpfung.png]]
++The dynamic client link is based on the different [[Filter modes>>doc:.Arbeiten mit den Filtertypen.WebHome]], which you can select. For example, it is possible to create an advanced SQL query ([[Advanced SQL filter)>>doc:ACMP.68.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.Erweiterte Abfragen erstellen.WebHome]], display the results according to the tree filter (Attention: This view is deprecated) or to build a container in which only Clients with certain vulnerabilities are to be considered (vulnerability filter). Select the appropriate mode and [[create a query>>doc:ACMP.68.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen erstellen.WebHome]] according to your criteria.
++
++Click //Continue >// to proceed to the next page. // //
++
++=== Result preview ===
++
++In the last step of the wizard, a result preview of your previously created query is displayed. If you now click //Finish //, the container is created. Continuing settings can be made in the detail view (including adding static Clients).
++
  {{aagon.infobox}}
  Read the chapter [[//Working with filter types//>>doc:.Arbeiten mit den Filtertypen.WebHome]] for the basics of creating filters, where you will also find application examples for constellations of different filters.
  {{/aagon.infobox}}
--== Edit, delete and duplicate Containers ==
++= Manage containers =
--All actions related to Containers can be started from the ribbon bar or from the context menu. To do this, click on the appropriate action button and follow the on-screen instructions.
++All actions related to containers can be started from the ribbon bar or the context menu. To do this, click on the corresponding button for the action and follow the further instructions.
--To edit a Container, select it and click on the //Edit// button [[image:Container bearbeiten Icon.png||height="18" width="18"]] in the ribbon bar. This will open the same dialogue as when creating a Container, but the existing values are already entered and can be changed as required.
++To edit a container, select it and click on the [[image:Container bearbeiten Icon.png||height="“18”" width="18"]]// Edit// button in the ribbon bar. The same dialog as when creating a container opens, but the existing values are already entered and can be changed as desired.
  {{aagon.infobox}}
--Please note that the// Allow multiple occurrences of the same Client in the Containers below //setting cannot be changed at a later date. If you have forgotten to enable this option, you will need to create a new Container.
++Please note that the setting Allow multiple occurrences of the same client in subordinate containers cannot be changed later. If you forgot to enable this option, you will have to create a new container.
  {{/aagon.infobox}}
--If you want to delete a Container, you must confirm a security message which will remove the (sub)Containers. To do this, click on the //Delete// [[image:Container löschen Icon.png||height="18" width="18"]] button.
++If you want to delete a container, you must confirm a security message, which will remove the (sub)containers. To do this, click on the [[image:Container löschen Icon.png||height="“18”" width="18"]] //Delete //button.
--WIf you want to duplicate a Container, you can copy it either from the context menu or from the ribbon bar ([[image:Container duplizieren Icon.png||height="18" width="18"]]). When duplicating a Container, the following contents of the selected Container are suggested:
++If you want to duplicate a container, you can copy it either via the context menu or via the ribbon bar ([[image:Container duplizieren Icon.png||height="“18”" width="18"]]). When duplicating a container, the following contents from the selected container are suggested:
  * Output directory
  * Network status
--* Container icon
--* Dynamic Client assignment
++* Icon of the container
++* Dynamic client link
--The following content is ignored during inheritance:
++The following contents are not taken into account during inheritance:
  * Jobs
--* BitLocker and Defender Management Configuration Profiles
--* Agent Tasks template
++* Configuration profiles for BitLocker and Defender Management
++* Agent scheduler templates
  * Rules
++
++== Container recalculation ==
++
++The container recalculation indicates the time required to calculate which container a client falls into. The display can only be found in the lower area of the Container plugin if you have clicked the //Show status //button in the ribbon bar.
++The information is divided into four areas: Container recalculation, end of last recalculation, duration and progress.
++
++
++|(((
++Container recalculation
++)))|(((
++The container recalculation returns either ‘no error’ as the result or a defined number of errors found during the recalculation. If an error has occurred, you can click on the error and a new window will open showing where the container generated an error (including the path). Errors are, for example, incorrect functions in the script of an advanced SQL filter or if a filter has not achieved a valid result.
++)))
++|(((
++End of last recalculation
++)))|(((
++The end of the last recalculation indicates when the server task or the manually started recalculation last ran. The successful result is displayed with a date and time.
++During operation, the display will change if you have configured the scheduled server task accordingly.
++)))
++|(((
++Duration
++)))|(((
++Specifies the duration in seconds that the recalculation took.
++)))
++|(((
++Progress
++)))|(((
++The display indicates how far the loading bar has progressed.
++)))
++
++You can trigger the container recalculation either manually (Container tab in the ribbon bar > //Recalculate//) or via the [[scheduled server task>>doc:ACMP.68.ACMP-Solutions.System.Einstellungen.ACMP Server.WebHome||anchor="HGeplanteServeraufgaben"]] (Group clients dynamically in containers).