Wiki source code of Container
Last modified by Jannis Klein on 2024/08/13 08:28
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{aagon.priorisierung}} | ||
| 2 | 20 | ||
| 3 | {{/aagon.priorisierung}} | ||
| 4 | |||
| 5 | {{aagon.floatingbox/}} | ||
| 6 | |||
| 7 | = General = | ||
| 8 | |||
| 9 | Containers are used to categorise Clients into groups. This allows you to map your corporate structure, for example, or differentiate between mobile and local Clients. You can assign Jobs, Rules, Updates and Client Commands to each grouping of Clients, providing flexible, dynamic support for each Container. Clients can be assigned either statically or dynamically. Assignments are made using pre-defined filters that allow individual settings for each Container. | ||
| 10 | |||
| 11 | {{figure}} | ||
| 12 | (% style="text-align:center" %) | ||
| 13 | [[image:66_Container_Übersicht_1464.png||alt="63_ClientManagement_Container_1699.png"]] | ||
| 14 | |||
| 15 | {{figureCaption}} | ||
| 16 | Container view | ||
| 17 | {{/figureCaption}} | ||
| 18 | {{/figure}} | ||
| 19 | |||
| 20 | Containers also offer continuing features that enable targeted control of the Clients they contain. Firstly, Containers can be sorted according to their [[priorities>>doc:.Container verwalten.Container-Strukturen und Prioritäten anpassen.WebHome]]. This allows you to influence and control the order in which the different Jobs, Client Commands, Updates and Rules are processed. Secondly, you can use the [[network status>>doc:.Container verwalten.Netzwerkstatus.WebHome]] to delay or prevent execution by assigning the Clients to different groupings. | ||
| 21 | |||
| 22 | = Properties of the Container = | ||
| 23 | |||
| 24 | ((( | ||
| 25 | Containers can have different properties: | ||
| 26 | |||
| 27 | |(% style="width:193px" %)**Property**|(% style="width:1170px" %)**Description** | ||
| 28 | |(% style="width:193px" %)[[image:Machine_Browse.ico||alt="Mehrfachvorkommen erlaubt" height="32" width="32"]]|The Container supports multiple ocurrences of Clients | ||
| 29 | |(% style="width:193px" %)[[image:Container_Dynamic.ico||alt="Dynamische Filter vorhanden"]]|The Container has dynamic filters | ||
| 30 | |(% style="width:193px" %)[[image:NetworkDevice.ico||alt="Status LAN"]][[image:Status_Mobile.ico||alt="Status: Mobil"]][[image:Status_Always.ico||alt="Status: Gesamtes Netzwerk"]][[image:Status_None.ico||alt="Status: Kein Netzwerk"]]|(% style="width:1170px" %)Displays the current [[network state>>doc:.Container verwalten.Netzwerkstatus.WebHome]] of the Container | ||
| 31 | |(% style="width:193px" %)[[image:FileRepository.ico||alt="File Repository aktiviert"]][[image:File Repository Vererbung.png||height="32" width="32"]]|Provides information about the type of File Repository inheritance | ||
| 32 | |(% style="width:193px" %)[[image:Mandantenzuweisung Container Icon.png]]|A Tenant is assigned to these Containers. You can see which Tenant is assigned here in the Tenant name column. Global Containers affect all Clients. Containers that are assigned to a specific Tenant also only affect clients from this Tenant. | ||
| 33 | |(% style="width:193px" %)[[image:DefenderManagement_one.svg||alt="Defender" height="32" width="32"]]|A Defender Configuration Profile is assigned to this Container. | ||
| 34 | |(% style="width:193px" %)[[image:BitLocker Icon.png||height="29" width="24"]]|A BitLocker Configuration Profile is assigned to this Container | ||
| 35 | |(% style="width:193px" %)[[image:Testring 1 Icon.png]][[image:Testring 2 Icon.png]]|The Containers are assigned to a Test Ring for Windows Update Management and/or Managed Software (either Test Ring 1 or Test Ring 2) | ||
| 36 | ))) |