"The script does not exist in the Scripts folder." error at imaging time

[donmontalvo]

We're using the "flushPolicyHistory.sh" script at imaging time (set to "After"). The script has the right permissions, and exists in all distribution points. Including the one in the imaging area.

Every time we image a computer we see the same error:

Running flushPolicyHistory.sh... The script does not exist in the Scripts folder.

JSS is at 7.31 and image is 10.6.4.

Is anyone else seeing this?

Thanks,
Don

[#2]

Hi Don,

I'm not certain about the exact error you're getting, but if you're
running the script as part of imaging I think you want to run the flush
policy history as an "at reboot", not an "after". We had a similar set up
and the script was trying to flush the policy history on our netboot
image. Setting it to run at reboot will run the script against the
computer that's just been imaged. Just be careful that the timing doesn't
interfere with any policies you run at startup (we didn't see any ill
effects).

Cheers,
Charlie

-------------------------------------
Charlie Smith
Desktop Engineer
Information Services Department (ISD)
MIT Lincoln Laboratory
244 Wood St. Lexington, MA 02420
Phone: 781.981.0854
E-mail: charlie.smith at ll.mit.edu
-------------------------------------

[donmontalvo]

Hi Charlie,

Makes sense! I'll move it to "after" and will check in Casper Imaging when the script will kick in. Like you alluded to, hoping it runs before the "at reboot" installs kick in. :)

Thanks!
Don

[tlarkin]

before and after refer to pre and post flight scripts and will run during the imaging process. Reboot means it will run at first boot. The difference is that before and after, if running as if it were on a local machine will actually run on your NBI and not the client that is netbooted to the machine. Therefore, you schedule it to run at first boot.

For example my post image shell script I run, if I run it after it would try to create local accounts on the netboot installer image instead of on the client. However, if it runs at reboot, it runs on the client and all settings get applied to said client.