I just stated with a new organization and we recently [successfully] deployed Adobe Acrobat X Pro (10.1.0.534). However, we're receiving reports (from users and IT staff alike) that when launching the application, it runs for 30 seconds or so, quits then prompts the user to accept the Adobe Software License Agreement before they can actually use the application. Having just walked into the door, I can't confirm it was packaged with the Customization Wizard, but that is looking less & less likely.
So, having deployed this to about 2000 clients, how can we go about suppressing (read: accepting) this Acrobat Software License Agreement at an enterprise level? (We'll figure out how, I just want to know what setting needs to be in place to eliminate this prompt.)
In the past (e.g.: Acrobat 7, 8 & I think 9) we were able to suppress this via a registry like:
- reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\VERSION\AdobeViewer" /v Registered /t REG_DWORD /d 00000002 /f >>!_BatchLog! 2>>&1
- reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\VERSION\AdobeViewer" /v EULA /t reg_dword /d 00000001 /f >>!_BatchLog! 2>>&1
- reg add "HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\VERSION\AdobeViewer" /v EULA /t reg_dword /d 00000001 /f >>!_BatchLog! 2>>&1
But I believe either in 9 or X (10.x) EULA changed to EULAAcceptedForBrowser and with this being a 64-bit version of Windows 7, I figured it would be in one of a few places:
- HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\10.0
- HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\10.0
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\10.0
I'm seeing EULAAcceptedForBrowser in the AdobeViewer key in locations 1 & 3 above so I exported both AdobeViewer keys & imported it elsewhere, but its still prompting.
So, on a whim, I added the three bulleted keys above and when launched, it worked fine. Yay!
After about 30 seconds or so, it behaves exactly as I described above: The application launches, you can work in it, but after at most 30 seconds, the application closes and launches the licensing agreement (PDApp.exe) again. What. The. Heck.
So, experts out there, what are we missing? How can we get this resolved without doing in place reinstalls or uninstalling/installing? We have to keep user interruption and fatigue to a minimum, and another 'deployment' is just not an option.