Policy fails because computer sleeps during execution.

[forrestbeck]

This doesn't happen often, but it adds a some uncertainty in running policies. I noticed that if a computer sleeps, or is disconnected from the network while a policy is running the policy will fail.

For example:
Our distribution point is setup through http and we have some policies that update software on faculty laptops. Sometimes a faculty member will open the laptop long enough to just check email, during which jamf does a recurring check in. If a policy is set to run that updates/installs a large package (like AdobeCS6), then the jamf binary begins to download the package. If the computer is then put to sleep while the package is downloaded, the policy fails.

Is there any way to have jamf automatically handle errors like this? Or is it up to us to manually go through all policies and look for error logs to flush?

[CasperSally]

Create a smartgroup like "Faculty Without CS6" looking for machines you want to have it without the casper receipt for the cs6 package

Then create a policy to install to "faculty without CS6" to that smartgroup and set it to ongoing. If it fails, it'll try again at next checkin.

edit: make sure in your policy to select "update inventory"

[mm2270]

Setting policies to to Ongoing as @CasperSally mentions is one approach. We do that for some items that we need to ensure always get installed.
But, http share points are supposed to support resumable downloads. Are you seeing a lot of cases of downloads not continuing after the Mac is put to sleep? Because that shouldn't be the case most of the time. If that happens regularly, you may want to dig further into why, or talk to your JAMF support rep about it.

[RWitt]

Why not select a couple different triggers rather than just at the 15-min check in that way you are sure to catch it.

[frozenarse]

Can you tell exactly where in the process the policy is getting pinched off?

Is it during the download of the package or during the installation?

[Caitlin_H]

What we did when we deployed CS6 was cache it via HTTP and then have a second policy kick off the actual install. We still had some errors but they were minimal and this helped because if disconnected or the computer goes to sleep in theory it should restart the download where it left off when it is reconnected to the network.