I understand that there have been many posts on this topic, but I’m trying to nail down the flow of what actually happens in the back end, as I’m not getting the warm feeling that this is working correctly.
As I’m hoping is rather common, we use this option when deploying a monthly baseline of Windows Patches. We kick off the action a few days prior to the Start on date. The expectation is that relevant patches will download to the endpoints and when the Start date is reached, they immediately start installing.
Upon viewing the client logs a while ago, it seemed that each was being downloaded a second time (I didn’t keep the log but will verify again).
In addition, there is a very long delay between the time the person clicks “Take Action” and the “Display message while running action” pop-up appearing. Probably because downloads are happening?
All endpoints have these settings:
I know there is a flow of a file being downloaded, placed in a directory, its SHA scanned, it copying it to another directory using its friendly file name, and then finally executing. I think I need to understand that better to troubleshoot.
Questions I have:
- When using the Download Before Constraints option, are files in their ready state or will they have to be “processed” when the Action starts?
- Based on my cache settings above, if the endpoint is rebooted before the Action is executed, are the files deleted?
- Does also enabling the “Stagger action downloads” option affect execution if files are already downloaded?
I’ll try and get a log posted soon.