I`ve configured an "application" in SCCM 2012 for Adobe Acrobat XI.  It has a dependency of Visual C++ 2010.  The installation works fine but after it`s installed, the button for uninstallation is grayed out.  After removing the dependency from the "application" the button is active.

How can i get around this ?  When i need to uninstall Acrobat, i don`t really need to uninstall Visual C++ but need to leave it as a dependency because if a target machine does not have it, Acrobat won`t install.

Answer Summary:
Cancel
1 Comment   [ + ] Show Comment

Comments

  • I would have liked the user to have the option to perform an uninstall by themselves by using the button but if it`s not possible i`ll have to live with it. Don`t get me wrong...i do not want to uninstall VC++, I`ll mark this question as answered and if i ever find a way around it i`ll post an update.
Please log in to comment

Answers

1

The grayed button does not prevent an uninstall, it simply prevents humans from clicking on the button.  When you use SCCM to remove it, it will work because it's using the "MSIEXEC /X {GUID}" syntax to remove it.

Answered 04/17/2014 by: vjaneczko
Seventh Degree Black Belt

Please log in to comment
1

Yes.. Do not remove VC++. It can be a dependcy for other application also.

as vjaneczko said, use msiexec /x {GUID} to uninstall your main application.

Answered 04/21/2014 by: jagadeish
Red Belt

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