![]() ![]() This is particularly problematic when permissions set on plist entries or files prevent the successful installation of new installs and/or updates. While most installs, uninstalls, and updates operations happen without incident, there are cases where a user may not be able to complete such tasks due to some registry or file conflict on the machine. ![]() The Adobe Reader and Acrobat Cleaner Tool removes a standalone installation of Reader or Acrobat, including any leftover preferences and settings remaining after a standard program uninstall. Always uninstall products via standard, supported methods. Adobe provides the utility as a least resort to repair machines after a failed or partial uninstall. I've tried tidying up using MSIZAP for both X and XI guids but this has not helped.The AcroCleaner is not an uninstaller and should NOT be used as such. 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. 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. 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. 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 ol eh who doesn't want that! 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |