Network state
Using the network status, you can delay or prevent the execution of Agent Tasks, jobs, and rules for specific containers. This can be helpful in certain situations, such as when clients—who work as field staff or primarily from home and can only access the company network via VPN on an occasional basis—should be assigned pending tasks at specific times.
To use the network status, the corresponding networks must be defined. Based on these networks, ACMP calculates which network the client belongs to. This allows a client to access a local (LAN) or external (mobile) network. The tasks (Agent Tasks, Jobs, and rules) are then applied based on a container’s network status:
| Status | Description |
| LAN | Containers with this network status apply the tasks to all Clients within the container that are on the internal network. |
| Mobil
| All containers located on the external network (e.g., via the VPN) forward the tasks to all Clients stored within them. |
| All | All Clients located in a container with the network status All are assigned the tasks. |
| Non
| If a container has the status None, no client will be assigned to it. |
You can change the network status either directly via the ribbon bar for the respective container or by editing it in the container properties. You can also edit the network status under the General tab.