AAMEE package and Casper Imaging

[dpertschi]

Following JAMF's own whitepaper on the subject, I created my first CS5.5 Design Suite deployment package with AAMEE v2 (man that's fast!), uploaded it to Casper, sync'd distros, but the software just will NOT install in an Imaging workflow.

I've tried it right after the image lays down, and as a first run install but the apps never show up; though progress indicators appears to take a while. The Imaging logs show that it installed, and I can't find anything useful in the jamf.log on the client to suggest a point of failure.

The software package WILL install correctly when pushed via Casper Remote, with or without being logged in.

Suggestions?

thanks,
Darrin

[donmontalvo]

Hi Darren

Did you exclude AIR? If not you might see "Adobe Setup" errors in jamf.log.

Also, we find AAMEE generated packages work best when you force AFP...HTTP seems to break things.

Don

[dpertschi]

Ryan, I might have to send you a miniature giraffe as payment in kind! It's working...

I rebuilt my package, but that did not alone seem to solve the problem. Then I used JSS Util to fix permissions on the share, and the next go around it DID work.

Not sure that alone was the fix though as my other AAMEE package is still failing. I'll rebuild that one tonight.

Closer, thank you.

Darrin

[Jak]

Sure I've had it as first run and working , for standard and master.

Will check again and report back

[martin]

You really should check the Adobe installation log file:
/Library/Logs/Adobe/Installers

The log file tells you what went wrong. Also note that some processes may
cause the installation to fail.

Martin

[dpertschi]

Thanks for the responses. I did omit AIR, disabled http on the distro point, and there is no Adobe log.

What I did find, that I did not notice before was a log entry:
"Error: The package (CS5_5_Design_Standard_Install.pkg) could not be found."

I had this happen with a .pkg before (from only one of 8 distribution points), called JAMF support and the resolution was to create that package as a .dmg.

Converting everything to dmg's is not what I had in mind, sigh. I thought this seemed too easy...

thanks as always.
Darrin

[bentoms]

So this works from 7 other distribution points?

Are you sure that the problem 1 is replicating correcty?

Regards,

Ben.

[dpertschi]

Replication is fine, I see everything where it should be, and permissions appear correct.

This new Adobe package is failing that way on two distros that I've tested from at this point, during imaging. (works fine pushing out with Remote).

Couple weeks ago, I had a small .pkg that I made with Composer, pushed via Policy, and it deployed successfully to several hundred users from 7 distribution points, and failed from one. That distro, is not one of the two I'm testing my Adobe package from.

Grrrr!

[donmontalvo]

Interesting...we do run into issues with replication. So for the big PKG installers (like AAMEE stuff) we copy manually to each share, then we sync to be sure.

This is going to be a bigger thorn in our side since we are in the process of migrating our DP to NAS. Our datacenter team won't help us with replication. They say the EMC Replicator application is riddled withbissues. I hate to say it but having to use a GUI to mount two shares to sync seems so....well....amateurish.

Don

** Sent from my iPhone **

[noah_swanson]

I went through this battle awhile ago. Our biggest issue was the Adobe Air prompting to get past our proxy (and would inevitably hang). I hacked out the updater and AIR using AAMEE. Currently I have this working with remote and imaging, all I had to do to fix the "file not found" error was to make sure to check the box that says "This package must be installed to the boot volume at imaging time".

Thanks,
--Noah

[talkingmoose]

That would make perfect sense. Although AAMEE does create an Apple
On 9/21/11 9:04 AM, "Swanson Noah" <SwansonNoah at JohnDeere.com> wrote:
Installer package, it simply runs the Adobe scripts to call their own app
installer inside it. The AAMEE package cannot be deployed to a volume
other than the current boot volume. It must be run at reboot when imaging
a machine.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[ryanhollitz]

Hey Guys-

We, at JWT, have found that the AAMEE packages have some built in permissions that break the replication. So after the pkg is uploaded to the repository, the permissions must be fixed in order for things to work smoothly.

Just my 2cents. ;)

ryan

[donmontalvo]

Hi Ryan,

Interesting...are you recursively setting to root:wheel?

Thanks,
Don

[ryanhollitz]

Hello-

I was having trouble like Darrin was describing. The other packages that were set to install on reboot worked, but then when it got to the AAMEE package it fails. Once I fixed the permissions with the JSS Setup Utility, all the installs seem to be working. I didn't change the permissions in the command line, just push the button in JSS Setup Utility. Seems to resolve it. :)

Cheers,
ryan

[bentoms]

Which version of the JSS are you running?

Regards,

Ben.

[ryanhollitz]

8.1, we haven't had a chance to upgrade to 8.22 yet. Though, our staging environment is 8.22 and has the same issue.

[jafuller]

8.21 drops the JSS Utility. Keep that in mind.

--
James Fuller | Starbucks

[martin]

We always run Fix Permission with the JSS Setup Utility because of
installation problems. Since 8.21 we can not use it anymore but also we do
not need it any more. Seems this has been fixed.

Kind Regards,

Martin van Diemen

t +31 (0)205677744

---

G-Star Raw C.V.
www.g-star.com