I am trying to deploy a powershell script that will run spread out of the course of 24 hours.
I set the action start time to be staggered over 1440 minutes as the powershell script involves some server overhead I wanted to really spread out.
I started the action at 5:07 PM Friday night, and as of 5:16 PM Monday it is just over 53% complete.
Can anyone weigh in on where I went wrong with my logic? 24 hours in a day * 60 minutes is 1440 minutes in a day, so that’s what I used.
I had a similar task set for another site and used 2880 minutes and its just over 27% complete now. Did I quadruple my minutes somehow?
See the following for the details on the first distribution. The task it self is small and quick and take only a moment to run.
Does the action End date come into play at all?
53.05% Completed (174 of 328 applicable computers)
No user interface will be shown before running this action.
No message will be shown while running this action.
This action will run independently of user presence.
User interface will be shown to all users.
This action ends 9/22/2017 5:07:47 PM client local time.
It will run at any time of day, on any day of the week.
If the action becomes relevant after it has successfully executed, the action will not be reapplied.
If the action fails, it will not be retried.
The action’s start times will be staggered over 1440 minutes to reduce network load.
No operations will occur after the action completes.