I'm having post image script issues with 9.62 as well in our test environment, but not exactly the same. We have one .pkg that installs at reboot (so I have the adobe account logging in as well), then I have 5 post image scripts, for some reason the final script never starts to run. It is copied to the PostInstall folder with the others. If I reboot the client, it runs through all of the post image scripts again, and again never runs the 5th final script.

I put a ticket in this morning

I've completed enough testing to convince myself that I need to have the killall jamfHelper. Probably just good practice at the end of any of my scripts.

It was the 8th of 8 scripts that wasn't completing when I first started digging into it. The 8th script's function was ```

!/bin/sh

softwareupdate -ia
```
Currently there aren't any updates available so I've removed that script from my 10.10.1 configuration. The 7th script has a killall jamfHelper at the end of it.

Is that command in your script? Could it be that process doesn't complete?

No I don't have that command in my scripts. Most of my scripts are install xyz software packages which all seem to install fine. I will try, though, taking out the prior script to see if that changes anything. Maybe it is causing some hang. Thanks for replying.

That seems to be my problem for well. My script causing the issue is a script to set firmware password, if one is already set (last years) it provides that old password.

If I remove that script from the workflow, imaging completes (computer runs last script and reboots).

That script doesn't cause a holdup in 9.32 though. If it has a firmware password properly set already, it just produces an error in the jamf.log and moves on. Not anymore... Were you getting an error in the jamf.log at all?

Looks like 9.63 doesn't fix this issue ether which is preventing me from upgrading from 9.6.

Anyone found a work around so far?

See this thread - I haven't tested out because it's not an out of the box replacement for my usage (I call jamfHelper as part of a script before policies and the message is in the parameters) but this might work for your usage....

https://jamfnation.jamfsoftware.com/discussion.html?id=12793

Hi everyone,

I believe this is being looked under D-008244, highlight it to your rep as important as for us it's preventing us from upgrading from 9.6 as we also display a message at logout for patching before updates get applied which is now paused until the message is closed down. I hope they address this in 9.64.

Hi guys,

Same issue in 9.64 in testing for me.

I've completed enough testing to convince myself that I need to have the killall jamfHelper. Probably just good practice at the end of any of my scripts. It was the 8th of 8 scripts that wasn't completing when I first started digging into it. The 8th script's function was #!/bin/sh softwareupdate -ia Currently there aren't any updates available so I've removed that script from my 10.10.1 configuration. The 7th script has a killall jamfHelper at the end of it. Is that command in your script? Could it be that process doesn't complete?

@jhalvorson

I ran into this issue the other day. The 'softwareupdate -ia' command was hanging during the first boot scripts on 10.10. Turns out that the softwareupdate command will not run in Yosemite if the user account is not completely logged in, because the first boot scripts run under the adobeinstall account the iCloud popup was appearing (but hiding behind the JamfHelper screen) and not completing the login. I changed the order of my first boot scripts to have the User Template plists updated to hide the iCloud prompt and now the softwareupdate command works without hanging the system.

I myself have tried to get any scripts at all work within imaging yet I cant. I just install Base applications and then use casper policies to apply scripts after enrolment.

Hi guys, scripts in general work fine for me it's only the ones which have /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper in them that display a message that pause the whole process when the message is displayed on screen stoping the policy / script from doing the next task.

I don't see D-008244 listed among the 9.65 release notes. Can anybody confirm whether this is fixed?

Confirmed, not fixed. It is on schedule to be fixed with the next (9.66) release support tells me.