here's my scenario.

our baseline image had adobe reader 7.0. recently we deployed adobe reader 8 in locked down envir. so there use couldnt open a PDF in the browser. this created too many problems so we had to create a new package to remove the locked down setting, remove the locked down reader 8, and reinstall a new, non-locked down reader 8.

recently though, after deploying reader 8 to lots of machines, users have been reporting that their adobe 7 standard and pro are missing. it looks to me like the reader 8 automatically did this, even though its not supposed to.

so we are trying to repush the adobe pro 7 to machines that had it removed. the package is dying out. the adobe 7 pro package we have is a slipstreamed adobe 7 pro with the 7.09 patches. the package works fine. But when attempting to reinstall it on one of these machines that no longer has it, the MSI encountered 1406 errors all through the registry.

if you tell the msi to retry, it will get stuck and wont install. the fix is to manually find each key it has a problem with, take ownership of the key and then set permissions to full control for the administrators. for some reason the admins are either not on the ACL or only have read rights.

our deployment method is with tivoli, so all packages are silently installed. any errors encountered cancel the install. I want to know how I can set the MSI to ignore 1406 errors. if I can do this, the install completes and adobe works fine.

anyone else had problems with reader 8 uninstalling an existing pro?
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity