1 Reply Latest reply on Sep 24, 2009 12:15 AM by Jared Barneck

    Q: Is there a way to stop/cancel a Policy-supported push (Install at next login distribution)?


      Our problem: A task was sent using standard Delivery method “Push”- Bandwidth-aware distribution. Then, since many machines failed due to being off at that time, the task was changed to use Delivery method “ Policy-supported push” – Install at next login distribution. The results were that after the next login of the user, all devices changed to active and then into Pending with Status “Delayed” and Result “Task will be performed at the next login.

      1. Why did the change did not just applied to the machines under Failed status?

      2. Is there a way to stop this policy on the machines so it will not run twice?