Changes for page Container

Summary

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

Details

Page properties

Content

...	...	@@ -1,36 +5,41 @@
1		-{{aagon.priorisierung}}
2		-20
3		-{{/aagon.priorisierung}}
4		-
5	5	{{aagon.floatingbox/}}
6	6
7		-= General =
	3	+(% class="wikigeneratedid" id="HGeneral" %)
	4	+Containers are used to organize clients into groups. This allows you to map the company structure or differentiate between mobile and local clients, for example. You can assign jobs, rules, updates, and Client Commands to each client grouping, enabling flexible, dynamically adaptable support for the respective containers. Clients can be assigned either statically or dynamically. The assignment is made using predefined filters that allow individual settings for each container.
8	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.
	6	+[[Übersicht über die Container>>image:68_Container Übersicht.png||alt="Übersicht Container"]]
10	10
11		-{{figure}}
12		-(% style="text-align:center" %)
13		-[[image:66_Container_Übersicht_1464.png||alt="63_ClientManagement_Container_1699.png"]]
	8	+Containers also offer additional features that enable targeted control of the clients they contain. On the one hand, containers can be sorted according to their [[priority>>doc:.Container verwalten.Container-Strukturen und Prioritäten anpassen.WebHome]]. This allows you to influence and control the order in which the various jobs, client commands, updates, and rules are processed. On the other hand, you can use the [[network status>>doc:.Container verwalten.Netzwerkstatus.WebHome]] to delay or prevent execution by assigning clients to different groupings.
14	14
15		-{{figureCaption}}
16		-Container view
17		-{{/figureCaption}}
18		-{{/figure}}
	10	+= Windows Clients and Unix Clients =
19	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.
	12	+Starting with ACMP version 6.8, Unix Clients with Linux and macOS can now be managed via containers in addition to Windows Clients. To do this, the containers must be assigned to the appropriate OS family when they are created. For more information on creating and using containers for managing Unix Clients, see the sections [[Managing Containers>>doc:.Container verwalten.WebHome]] and [[Working with Clients>>doc:.Umgang mit Clients.WebHome]].
21	21
22		-= Properties of the Container =
	14	+= Properties of the container =
23	23
24		-(((
25	25	Containers can have different properties:
26	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)
	18	+
	19	+(((
	20	+|(% style="width:193px" %)**Eigenschaft**|(% style="width:1170px" %)**Beschreibung**
	21	+|(% style="width:193px" %)[[image:Machine_Browse.ico||alt="Mehrfachvorkommen erlaubt" height="32" width="32"]]|(% style="width:1170px" %)(((
	22	+The container supports multiple occurrences of Clients.
36	36	)))
	24	+|(% style="width:193px" %)[[image:Container_Dynamic.ico||alt="Dynamische Filter vorhanden"]]|(% style="width:1170px" %)(((
	25	+The container has dynamic filters
	26	+)))
	27	+|(% 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" %)(((
	28	+Displays the current [[network status>>doc:.Container verwalten.Netzwerkstatus.WebHome]] of the container
	29	+)))
	30	+|(% style="width:193px" %)[[image:FileRepository.ico||alt="File Repository aktiviert"]][[image:File Repository Vererbung.png||height="32" width="32"]]|(% style="width:1170px" %)(((
	31	+Provides information about the type of file repository inheritance.
	32	+)))
	33	+|(% style="width:193px" %)[[image:Mandantenzuweisung Container Icon.png]]|(% style="width:1170px" %)(((
	34	+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 only affect clients from that tenant.
	35	+)))
	36	+|(% style="width:193px" %)[[image:DefenderManagement_one.svg||alt="Defender" height="32" width="32"]]|(% style="width:1170px" %)A Defender Configuration Profile is assigned to this container.
	37	+|(% style="width:193px" %)[[image:BitLocker Icon.png||height="29" width="24"]]|(% style="width:1170px" %)A BitLocker Configuration Profile is assigned to this container.
	38	+|(% style="width:193px" %)[[image:Testring 1 Icon.png]][[image:Testring 2 Icon.png]]|(% style="width:1170px" %)The containers are assigned to a test ring for Windows Update Management and/or Managed Software (either Test Ring 1 or Test Ring 2).
	39	+|(% style="width:193px" %)[[image:ACMP.63.ACMP-Solutions.Client-Management.Abfrageverwaltung.Abfragen auswerten.WebHome@platform_windows.png||alt="Windows"]]|(% style="width:1170px" %)The containers are assigned //Windows //as the operating system family. Accordingly, only Windows Clients can be managed via these containers.
	40	+|(% style="width:193px" %)[[image:ACMP.68.ACMP-Solutions.Desktop Automation.Unix Scripts.WebHome@Ico_UnixClient.png||alt="Unix-Icon" height="32" width="32"]]|(% style="width:1170px" %)The containers are assigned //Unix //as the operating system family. Accordingly, only Unix Clients can be managed via these containers.
	41	+)))