I use the Adobe Exceptions Deployer to package and deploy Adobe Help, while using the AAMEE build for packaging and deploying the remaining CS6 (non Air ) Apps. Since I install when no user is logged in, I append this to the command per Adobe recommendations <sudo launchctl bsexec `ps auwwx |grep [l]oginwindow | awk '{ print $2 }'`>
I have used the exact same package, exceptions and scripts to push my CS6 apps to a 10.6.8 machine with no problems, but when I try to push to a 10.8.4 machine, the script to run the exceptions deployer just hangs in the Casper Remote window indefinitely. I eventually have to stop the process. If i try to install when a user is logged in, I get this error
Exceptions deployer command Script result: Starting the ExceptionDeployer...
ExceptionDeployer exiting with Return Code (1)
launchctl bsexec failed: No such file or directory
Addendum Tuesday June 11th: I was able to successfully install the exceptions via a policy triggered by logout. So whats different about logout policy versus using casper remote when no one is logged in?
