Hey,

OK I have a strange issue that has happened upgrading a handful of machines (40/4000) from Adobe Reader X to Adobe Reader XI using SCCM 2012.

Now the initial report states install has failed however from a users perspective they now have two versions of Adobe Reader installed that both work fine...cool eh who doesn't want that!

SCCM reports back failure so I attempt to clean up the machine, uninstall both versions then let SCCM trigger off the install of Adobe Reader XI again...once again SCCM reports back as failing but application appears fine from a user perspective and logs suggest all ok. The main issue is that we use SCUP to deploy Reader updates and the updates are now not evaluating on the machine as being required...I assume for the same reason that SCCM is failing to detect the reader install as being installed.

The GUID exists in the "uninstall" registry key so I thought this is what SCCM detects....I can also confirm the GUID IS correct in the SCCM detection method.

I've tried tidying up using MSIZAP for both X and XI guids but this has not helped...

Any Thoughts? Apart from rebuilding...

1 Comment   [ + ] Show Comment

Comments

  • Have you used the Adobe Customization Wizard to customize your Adobe Reader XI package? I know there is an option to remove prior versions of the software.
Please log in to comment

Community Chosen Answer

1
If you are concerned about those failed machines then use msicuu2.exe

Microsoft’s Windows Installer CleanUp Utility, MSICUU2.exe, was a tool one used to remove failed installations and information for programs, that were installed using Windows Installer

Microsoft now no longer supports the use of this tool.


Note: Be aware that Windows Installer CleanUp Utility will not remove the actual program from your computer. However, it will remove the installation files so that you can start the installation, upgrade, or uninstall over. Do not use this utility with 2007 Office system products.


Answered 07/25/2015 by: jagadeish
Red Belt

  • I'll give it a go, but how does it compare to MSIZAP?
    • Same thing.
Please log in to comment

Answers

0
1. SCCM is pretty dumb in that it judges success or failure by using the return value from the script or EXE.

2. Add verbose logging to your command line. Without a log, diagnosis is going to be pure guesswork, for us & you.
Answered 07/26/2015 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share