Casper 9 imaging log gets deleted after jamf flushPolicyHistory command

You no longer need to run jamf flushPolicyHistory in your imaging workflow. This is done automatically now and your Casper Imaging logs won't be wiped out.

@cbrewer][/url
Can you please confirm this;

In v8.62 it runs jamf flushPolicyHistory at imaging workflow as well but we have seen that the policies scoped to login, startup, etc.. kick in at the last part of the Imaging step where "adobeinstall" user logs in.
We don't want in to happen. If I scope a policy to happen at login it should happen at the very first real user logs in, not when the "adobeinstall" user logs in as it might cause some issues with dependencies.

Do you see this happening in v9?

Welcome to my world - I have been working with JAMF on this for the last few days. I am still using Casper Imaging 8.73 because of this. In the enroll.sh file created by Casper Imaging to run on first boot, there is a line that calls a startup script which process all of the JSS startup policies. With 8.73 and older this was broken (which turned out to be a good thing). Now with 9 this startup script is working (not good in my opinion). As a result you end up with JSS startup policies running at the same time that the postinstall.sh script is still applying software and scripts from your imaging configuration.

@cbrewer][/url
Thanks for the info.
Do you have the defect number?

I don't think it's a good idea to run at the same time it runs postinstall.sh script.

Even if it works as they described I don't understand why it is clearing Imaging log after "jamf flushPolicyHistory" command.

In my test environment it seems like remote screen sharing logs are also being wiped with the imaging logs with the flush command.

@amanda.wulff
Can you find if this is identified as a defect? or the development team working on it?

@Kumarasinghe

I checked on the defect that @cbrewer mentioned ( D-006185 ), and it appears that it’s not a defect and is expected behavior in 9.

Even though the enroll script called startup.sh in the 8.x series, the startup.sh either did not get triggered or did not successfully run in 8. In 9, that script is triggered by the enroll script and does actually run as it was always intended to.

Development has confirmed that this is expected and intended behavior for imaging workflows. Essentially, the actual defect behavior was what we saw in 8, not what we’re seeing in 9.

If you have additional questions on that, it would be best to get in contact with your Technical Account Manager.

Thanks!
Amanda Wulff
JAMF Software Support

@amanda.wulff

Thanks Amanda.
I'm talking about the Imaging Log gets deleted after "jamf flushPolicyHistory" issue.

@Kumarasinghe

Ah, sorry for the confusion there; I didn't find a defect specifically mentioning imaging logs.

That may be one that you'll want to get in touch with your Technical Account Manager about, they'll be able to gather more information and dig a bit deeper into it.

Thanks!

Amanda Wulff
JAMF Software Support