On Casper Admin, when you look at the properties of the pkg, under option, are you checking the "This package must be installed to the boot volume at imaging time" option?

Yep, there is no change in the way the package is being installed other then using one version of Casper Imaging over another.

So using Casper Imaging 8.63 all works as expected, all software installed and working including CS6.

Using Casper Imaging 8.64 everything is installed like above except for CS6, its missing from the Applications folder.

Part of my testing the Imaging process with both version of Casper Imaging. I had them both run through the imaging process but did not have them restart to finish the post install packages. Checked the "First Run" folder for JAMF and all the packages where there. There is a minor change with the "postinstall.sh" script that Imaging builds from version 8.63 and 8.64

The "Delete the temporary user and restore the original files for autologin" section has moved above the "Run any scripts that were specified to be run after reboot here" section. In 8.43 the order is reversed, don't think that would cause the issue I am seeing.

Yeah, that's super strange - out of curiosity, does your CS6 pgk works fine if you deploy it through Casper Remote 8.6.x?

SMB?

(I know, it's a shot in the dark)

Also seeing this with Adobe CS5, built with AAMEE. Works fine with 8.63

Just upgraded to 8.64 this weekend and we are now having the same issue with CS5.5 and CS6.

in my experiences, i have had about 70-90% success letting casper do it, i now wrap adobe CS and all my stuff that needs to install on a live system, and install it with a launch daemon when the user logs in the first time.

So in further testing.

Pushing the package with Casper Remote 8.64 worked like it should. Software installed and working.

So it looks like its an issue the JAMF Casper Imaging 8.64.

I got the same issues with 5, 5.5 and 6 being part of the install at reboot imaging process.

Not sure if this is the same but looks like I am caught in a loop of reboots since I have a script that happens after imaging to reboot the machine after all installs are complete.
After the reboot it keeps trying do the 1st run scripts all over again. Keeps trying CS6 over and over. (Im using 8.64 as well).
I let it run 3 times so far.
So its not remembering whats being completed.

Gabe Shackney
Princeton Public Schools

@gshackney

Casper FirstRun policy has a Reboot so please remove your reboot line in the script. Otherwise your Mac will reboot in a loop thinking it hasn't finished the imaging process.

Do not put any reboot lines in post image scripts.

Removed that reboot script and the cs6 image still fails to deploy.

Worked with jamf on this and they provided me a test fix package to install at stage 1 during imaging that fixes the cs6 failing issue.
Love their quick response. I would ask your rep for this pkg file to see if it fixes yours as well. Has to do with the way a user get created to install the adobe pkg apparently.

Gabe Shackney
Princeton Public Schools

@gshackney
We are still on 8.62 and we don't have any issues with deploying CS6.
I don't want to hijack this discussion so If you need anything else regarding your CS6 please create a new discussion as this is all about Casper 8.64 and JSS.

Kuma,
JAMF fixed this issue that this thread is discussing (imaging 8.64 and cs6) with a special pkg as I stated above. Watch your responses; they come off much differently then I'm sure you intend them.
Thanks again for the tip.
2nd thread with similar issue:
https://jamfnation.jamfsoftware.com/discussion.html?id=7003

Gabe Shackney

Watch your responses; they come off much differently then I'm sure you intend them.

@gshackney Your comments are relevant and on topic. We are on 8.64, and our AAMEE packages are wrapped in DMG and deployed with a script, with no dependency on having a user (temp or otherwise) logged into these. No issues deploying both the main package and the exceptions package. So far 100% success with no errors, although we target logged off Macs only.

For anyone seeing an issue with Adobe packages not installing properly with 8.64 in the FirstRun process, we are aware of this issue, and have created a defect on our side. For your reference this defect can be tracked with the defect ID of D-003696.

If you contact your account manager and reference the Defect ID they will be able to supply you with the needed information for the workaround.

Please let us know if there is anything else we can help out with here.

Thanks,
Derek

Please search jamfnation "managing cs6" myself and others covered this months ago!

cant the fix be made in to a kb or posted here please.?

I noticed this a while back but got around the problem via the mounting a dmg and install command.

like others for primary dp is afp and only reverted to other methods because this isnt working.

Also like other might be i would like this working asap as shouldnt need to log a call for a fix on a known defect!

Hi tkimption,

The defect that this discussion is tied to is based on an issue that we found specifically in 8.64. This is an issue that is only seen when installing an Adobe PKG at imaging time with-in the FirstRun script.

From what I am seeing in the other post, we may be running into other issues on other versions of Casper Imaging.

One thing I have tested in the past that has cleared up some issues is to verify that all permissions in the PKG are correct and haven't been changed.

As a test we can run a command like the following to set permissions on the package on the share it is being downloaded from:

sudo chmod -R 755 /path/to/Adobe.pkg

Next we can push out our Adobe package via Remote and or Imaging to see if either one works.

If we are seeing issues that are not tied to this defect please let you account manager know and they can work with you more closely to resolve them.

Please let us know if there is anything else we can help with.

Derek

...so lemme get this straight. So Adobe is the hero here, having fixed a JAMF bug by giving us cr@ppy installers that have to be encapsulated in DMG for delivery. Adobe duct tape...priceless. :)

gshackney wrote;

Watch your responses; they come off much differently then I'm sure you intend them.

I'm extremely sorry about that. I thought you were referring to the reboot loop caused by the reboot line in your script.
My mistake. Sorry.

@Kumarasinghe with all the value and assistance you've provide on this list, you're allowed to kick someone in the teeth once in a while. Figuratively speaking, of course. LOL

(Just kidding!)

...so lemme get this straight. So Adobe is the hero here, having fixed a JAMF bug by giving us cr@ppy installers that have to be encapsulated in DMG for delivery. Adobe duct tape...priceless. :)

lol Don you crack me up again :)

@Kuma,
No worries, I got a good dental plan. ;)
Hard to be as clear in my text as I think I am in my head, if that even makes sense.

Gabe Shackney
Princeton Public Schools

@derek.brost wrote:

One thing I have tested in the past that has cleared up some issues is to verify that all permissions in the PKG are correct and haven't been changed.

As a test we can run a command like the following to set permissions on the package on the share it is being downloaded from:

sudo chmod -R 755 /path/to/Adobe.pkg

Hi Derek,

What about those of us who are using Windows/EMC/etc. shares for our Distribution Points?

Is there a specific set of permissions that should be set (recursively and persistent)?

This way we can provide guidelines to our datacenter team.

Many thanks,
Don