We’ve got an action that applies broadly to any Windows computer without a particular piece of software installed. The Execution settings are as follows:
This action will never expire.
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 be reapplied as a policy an unlimited number of times.
If the action fails, it will be retried up to 99 times, waiting until the computer is rebooted between attempts.
The action’s start times will be staggered over 5 minutes to reduce network load.
Most computers are getting the software just fine, but a few seem to be stuck with a Summary of “Waiting to satisfy temporal distribution time constraint.” It’s been a few days and multiple restarts of one particular computer with no change. There’s no mention of the Action in the client logs for this computer. Is there something I can check on the root or relay to find out what the issue is?
I don’t know why this is stuck like this, but if you deployed the action without: “The action’s start times will be staggered over 5 minutes to reduce network load.” this wouldn’t be happening.
I would also check if the client’s clocks are correctly set, maybe that is a factor???
Sigh. No need but can likely replicate if there’s interest. The file in question had updated without my updating the SHA/Size info so was failing the download. I was so honed in on the computer results that I totally missed the overall Action message that the precache failed.
Yikes, that is good to know, but it sounds like we may have a gap there in action status & logging. I think it’s worth filing a bug over.
I’ll do that internally (though it may take me some time to reproduce it). If you consider this pressing then it will have more weight coming in as a customer problem if you open a support case, but I certainly understand if you just want to move on with your day.