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.

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. 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 to delay or prevent execution by assigning clients to different groupings.

Windows Clients and Unix Clients

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 and Working with Clients.

Properties of the container

Containers can have different properties:

Eigenschaft	Beschreibung
	The container supports multiple occurrences of Clients.
	The container has dynamic filters
	Displays the current network status of the container
	Provides information about the type of file repository inheritance.
	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.
	A Defender Configuration Profile is assigned to this container.
	A BitLocker Configuration Profile is assigned to this container.
	The containers are assigned to a test ring for Windows Update Management and/or Managed Software (either Test Ring 1 or Test Ring 2).
	The containers are assigned Windows as the operating system family. Accordingly, only Windows Clients can be managed via these containers.
	The containers are assigned Unix as the operating system family. Accordingly, only Unix Clients can be managed via these containers.