AAMEE-generated package being served from an SMB share, so we've put the package on a DMG and using the script referenced here:
https://jamfnation.jamfsoftware.com/article.html?id=161
Everything installs fine as a policy (cache DMG, run script after), so I'm confident that we've done this correctly.
Now, what about installing this at imaging time? I've created a new DMG which puts the installer into /Library/Application Support/JAMF/Waiting Room. That policy runs at initial imaging.
I've duplicated/renamed my installPKGfromDMG.sh script, and configured it to run At Reboot.
What happens at imaging time? The installer is cached HOWEVER the script never runs, and there's no errors in the Casper Imaging logs. Other scripts configured to run At Reboot are running.
Has anyone at JAMF ever tested this? I tried with 8.6x and currently 8.7x. Right now, doing a hack with dummy receipts, then running a policy that checks for the existence of the dummy receipt and runs the script, and that works, but it's extremely "hacky". This is something that Casper Imaging should be able to handle at boot time.
I realize CS5.5 is old, but the client will be updating to CC and AFAIK CCP has the same limitation with packages and SMB shares, so...
