restart failed tasks
In larger rollouts it is very likely, that 5-10% of the devices will be offline and will not receive, e.g. the new app. These devices show up as failed tasks in the task list. Unfortunately, a restart of the task requires a manual selection of all the devices and reassignment of the app or task bundle.
Please provide a way to either restart the tasks for the failed devices or at least find all devices, which deviate from the defined configuration
William de Vos - IMPROVES B.V. commented
Got several customers running into this issue. Users that are on holidays for example and are not using their enrolled mobile fail to receive the configuration changes. This creates an unmanagable scenario.
There is an article describing the timeouts, old article, can the customer change the timeouts in the latest version (both on-prem as central) and if they cant... why?