I am packaging with recent Adobe Acrobat Pro 9.3 update using the Wise packaging tool for distribution via SCCM to my Windows XP SP2 machines.

Prior to this update, everything was working fine. I am trying to apply this patch using the following:
Msiexec /i acropro.msi TRANSFORMS=acropro.mst /qn REBOOT=ReallySuppress /l* c:\applog\Adobe_Pro_93_Install.log
Msiexec /p AcroProStdUpd910_T1T2_incr.msp /qn /l* c:\applog \AcroProStdUpd910_T1T2_incr_Install.log
Msiexec /p AcrobatUpd911_all_incr.msp /qn /l* c:\applog\AcrobatUpd911_all_incr.msp_Install.log
Msiexec /p AcrobatUpd912_all_incr.msp /qn /l* c:\applog\AcrobatUpd912_all_incr.msp_Install.log
Msiexec /p AcrobatUpd913_all_incr.msp /qn /l* c:\applog\AcrobatUpd913_all_incr.msp_Install.log
Msiexec /p AcrobatUpd920_all_incr.msp /qn /l* c:\applog\AcrobatUpd920_all_incr.msp_Install.log
Msiexec /p AcrobatUpd930_all_incr.msp /qn /l* c:\applog\AcrobatUpd930_all_incr.msp_Install.log

During the silent installation, a message is popping-up with a warning about a printer not passing the Windows Logo Testing. This is preventing the silent install from continuing without user intervention which defeats the purpose.

Adobe support has pointed me back to Microsoft?!

Does anybody have any experience with this and a workaround?

As always, thanks for your help!

0 Comments   [ - ] Hide Comments


Please log in to comment

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



You would be better off creating an Admin Install Point and then patching that (there are numerous posts on AppDeploy detailing this for Adobe products).

Once you have the AIP you would use the 'Adobe Customization Wizard 9' to create your MST from the patched installation files.

I don't know what's causing the Windows Logo Testing thing, but the above method is the best way to do what you're attempting and you may find that the error is no longer present.

Hope this helps,

Answered 01/27/2010 by: dunnpy
Red Belt

Please log in to comment
The printer driver that is about to be installed is not proper (or at all) signed.
Answered 01/28/2010 by: AngelD
Red Belt

Please log in to comment