If you are using Kafka, Wake On LAN, DMZ Servers, you can use zman qes and optimize your zenworks server to either perform only critical tasks or exclude servers from performing such tasks that require specific environments.
Use Case:
Excluding a few servers from running a specific Queue Action: If you have two ZENworks servers in the zone in two different networks - one in DMZ and the other in the Intranet, and Server_1 being the DMZ server cannot reach the Managed Devices in the Intranet - if this server will perform Wake-on-LAN, then the action fails; whereas the Server_2 can reach the Managed Devices in the network and can perform Wake-on-LAN. In this case, we can exclude the Server_1 from running WOL_QUICK_ACTION_TYPE (Wake on LAN queue action), using the following command:
zman qes WOL_QUICK_ACTION_TYPE -g server_guid1
RUN_ASSIGNED_TASKS_ONLY: If Kafka is configured in the zone, and as Kafka is heavy on Input/Output, to avoid the ZENworks server from performing other non-mandatory, regular queue actions and ONLY perform the mandatory queue actions related to Remint, System Update, Kafka; use the following command:
zman qes RUN_ASSIGNED_TASKS_ONLY -g server_guid
NOTE:
If a Primary Server is deleted from the zone or if a Primary Server is excluded from performing specific queue actions, the list of Primary Servers in the zone or the exclusion list might not get updated immediately, it might take around 30 minutes for the update to reflect. In between those 30 minutes, if any queue action gets assigned to the deleted server, it might fail; and if any queue action gets assigned to the Primary Server which was excluded, it might let the same Primary Server run the queue action, until it gets updated.
If a Primary Server has been excluded from running a specific queue action for example: WOL_QUICK_ACTION_TYPE and the same Primary Server is set to run only directly assigned (mandatory) queue actions using RUN_ASSIGNED_TASKS_ONLY, in that case, specific queue action: WOL_QUICK_ACTION_TYPE gets priority over RUN_ASSIGNED_TASKS_ONLY.
Multicast servers are the servers with specific roles for example: MDM servers. If all the Multicast servers are set to run only directly assigned (mandatory) queue actions using RUN_ASSIGNED_TASKS_ONLY, then the exclusion list is NOT honored. As if a queue action has to be run by a multicast server, and if all such servers are configured to run only directly assigned tasks, then no multicast server would be available to run these server-role specific queue actions and these queue actions will fail, for that reason, in this scenario, the excluded servers would NOT be honored.