We created a customized installer for Acrobat 11 using the Adobe Customization Wizard for Macintosh. The resulting .pkg installer installed successfully on three Macs (two on 10.8.2 and one on 10.7.5) but the installer fails on the fourth machine, which is running 10.8.2. It appears that Acrobat installs into the Applications folder, but when I try to run it, a prompt pops up to register with an Adobe ID. This shouldn't be happening, given the settings for the installer:
•Accept End User License Agreement
•Disable Registration
•Grant Offline Exception (we have a volume serial number)
The three machines that we ran the installer successfully on have had no problems...Acrobat launches without any request for registration.
The console logs show the following info for the last two times we have tried to run the installer...
10/24/12 14:52:36:952 | [INFO] | | | | | | | AAM URI protocol handler registered.
10/24/12 14:52:37:040 | [ERROR] | | | | | | | AAM URI: Error in deleting file /Applications/Adobe Application Manager. Error = Error Domain=NSCocoaErrorDomain Code=4 "“Adobe Application Manager” couldn’t be removed." UserInfo=0x1834a60 {NSUnderlyingError=0x1834970 "The operation couldn’t be completed. No such file or directory", NSFilePath=/Applications/Adobe Application Manager, NSUserStringVariant=(
Remove
)}
10/24/12 14:52:37:040 | [INFO] | | | | | | | AAM URI Handler: Could not get env var DISABLE_CCM_DESKTOPSHORTCUT
10/24/12 14:52:37:055 | [INFO] | | | | | | | Adobe Application Manager shortcut created at /Applications/
10/24/12 15:36:11:867 | [INFO] | | | | | | | AAM URI protocol handler registered.
10/24/12 15:36:11:867 | [INFO] | | | | | | | AAM URI: Adobe Application Manager shortcut deleted from /Applications.
10/24/12 15:36:11:867 | [INFO] | | | | | | | AAM URI Handler: Could not get env var DISABLE_CCM_DESKTOPSHORTCUT
10/24/12 15:36:11:886 | [INFO] | | | | | | | Adobe Application Manager shortcut created at /Applications/
Any suggestions what the problem could be or what the fix is? Running the standard installer is not an ideal solution, since we intend to push Acrobat 11 out to over 300 machines.
