Skip to main content
Answer

Policy not marked as complete

  • May 14, 2012
  • 3 replies
  • 15 views
A
Forum|alt.badge.img+18

All:

I am running a script via a policy that creates a file on the filesystem and then reboots the computer into netboot. This works fine. The problem is that the policy is not marked as complete in the policy logs, so the job runs again when the computer is booted.

Is there an easy way to tell the JSS that the script has run, so that it doesn't run again? Maybe via the jamf binary? I know about the <result> stuff for extension attributes, but I am not clear on the mechanism that the JSS uses to determine whether a policy has run.

Any advice appreciated!

--Andy

Best answer by stevewood

Are you restarting the machine from the script, or from the policy? If you are restarting from the script, then the policy is never truly completing, or at least the JSS doesn't know that it is completing.

Make sense?

    3 replies

    mm2270
    Forum|alt.badge.img+24
    • mm2270
    • Legendary Contributor
    • May 14, 2012

    I would think the Once Per Computer or Once Per User setting in the policy would tell it not to run again. Is it set up as Ongoing?
    Or is this an odd case because you are rebooting into Netboot and it somehow doesn't register to the JSS that the policy ran?

    stevewood
    Forum|alt.badge.img+38
    • stevewood
    • Hall of Fame
    • Answer
    • May 14, 2012

    Are you restarting the machine from the script, or from the policy? If you are restarting from the script, then the policy is never truly completing, or at least the JSS doesn't know that it is completing.

    Make sense?

    A
    Forum|alt.badge.img+18
    • andyinindy
    • Author
    • Valued Contributor
    • May 14, 2012

    Steve:

    Yep, that makes sense. I was rebooting via the script. I am now rebooting via the policy. We'll see how well this works.

    Thanks!

    --Andy

    Terms & ConditionsCookie settingsAccessibility statement