What you are probably seeing is that you have the "ignore conflicting process" box unchecked. I had the same issue with CS5 packaged deployed with JAMF when users would have Safari or some other application open. The install times I find vary widely depending on the hardware. SSD models obviously install much faster than platter drives. The estimated times are also way off. Most of my JAMF SS installs of CS6DP take around 15 minutes.

I had the same problem which was fixed by checking the "ignore conflicting process" box.  The new package installed at the first attempt.

To continue on w/ the original question/problem, I've been having issues, too.  After making my package, I see 2 types of failures.  One has the installer pausing at about 1/8 or so in the progress and the time remaining increases.  This never clears out and you have to force quit the installer.  I've let it sit there and have it climb it to over an hour w/o the progress bar moving.  The other problem involves the failed install which will happen within about 7-10 seconds.  It will go through the progress bar quickly and finish w/ a failed install message.  My packages do have the  "Ignore conflicting process" box checked. 

One thing I noticed that helped me get around this 7-10 second failed install this morning did not make sense to me.  I did 3 machines w/ the Photoshop CS6 package I created by copying the package over ARD to the desktop of the machine and running it.  The 4th machine I copied the same package off of a local server and it would repeatedly fail during the installation (7-10 second failure).  Finally when I copied it via ARD and running it, it did work.  Anybody ever see this?  I'm not doing the ARD Install package feature.  Just a copy.

Also, any clue on my first type of failure w/ stuck installer?

Thanks!

Yes, I ran into a simular problem. Made the Photoshop CS6 package used ARD and it ran for quite some time. Added the unix command and it finally completed, checked the machine and the Photoshop CS6 package never installed. Now i am trying the "Client Imaging for CS6" shown in the video. Having problems with the serialization, Terminal giving me a Return Code = 19.

We put the PKG in a DMG, mount the DMG and trigger it from there. No problems, whether doing this in Finder or automating using Casper.

SMB mounts can corrupt AAMEE packages (even the new AAMEE 3.1):

https://jamfnation.jamfsoftware.com/article.html?id=161

Wrapping the PKG in a DMG protects it from corruption. Not sure what is corrupting but has to do with SMB...

Don

If you follow the first URL above, it points you to a script...

Here's another thread...

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

I caught up with Jody at JNUC 2012, his team are constantly working to improve AAMEE. Unfortunately some of the required changes take time to implement.