Is anyone able to suggest a working solution to deploying a large volume of application updates without having a significant impact on Autopilot deployment?
We tested the suggestion of blocking apps via ESP but that doesn't seem to have any impact on the problem. If we have 40 application updates being deployed it would seem it still runs through the detection method to see whether they are applicable in an uncontrollable order. We end up hitting timeout limits or the process becomes a terrible experience for the user.
Other suggestions such as setting a custom attribute post-enrolment for use in a dynamic group would solve the initial enrolment problem but not work in the event we fresh start the device.
Its the same issue as described here which never really got a resolution but hoping someone can offer a working process as this is really a fundamental feature.
https://patchmypc.com/forum/index.php?topic=6931.0
We tested the suggestion of blocking apps via ESP but that doesn't seem to have any impact on the problem. If we have 40 application updates being deployed it would seem it still runs through the detection method to see whether they are applicable in an uncontrollable order. We end up hitting timeout limits or the process becomes a terrible experience for the user.
Other suggestions such as setting a custom attribute post-enrolment for use in a dynamic group would solve the initial enrolment problem but not work in the event we fresh start the device.
Its the same issue as described here which never really got a resolution but hoping someone can offer a working process as this is really a fundamental feature.
https://patchmypc.com/forum/index.php?topic=6931.0