Software Center: Install and Uninstall Available Software Software Center is designed for easy installation and removal of optional software without the need for administrator rights on Windows computers that are managed by University of Minnesota IT. SCCM12R2 App Installed - Install Uninstall Greyed Out. Via Software Center), and uninstall works as. And have the device install it from SCCM if it was. May 11, 2015 If I refresh Software Center the Uninstall button is greyed out of that app. If I change the focus to another package in Software Center and then click on the first app again the Uninstall button comes back.
Hello, I'meters fairly new to SCCM administration, and I've work into a circumstance where I can deploy iTunes 12.2.2.25, but the uninstall key can be greyed out. ITunes comes as a bundle of 5 MSIs, which I have got deployed as a single application with several deployment varieties all tied collectively with dependencies. The program installs well, but I need to create sure uninstalling works for when improvements are launched.
Any assistance on what I need to perform to allow this software to uninstall via Software Center? Which I possess implemented as a one application with several deployment forms all tied collectively with dependencies This isn'testosterone levels how it's designed to function. You put on't use multiple deployment varieties to install multiple parts of one software. The just time you create several deployment varieties for an program is certainly when you possess even more than one way of setting up that software and you only would like one to operate on any given machine, age.g. When an software has independent 32-bit and 64-bit installers. Discover for even more details.
For something Iike iTunes, where yóu possess multiple MSIs that need to become installed, you have two choices. First, you can make a deployment type that operates a script which sets up all the required MSIs. The can be very helpful with this. The second way to do this would be to generate separate Programs for each MSl, éach with its personal deployment kind, and create one Software type on the others.
I find the very first method is the most reliable. I've attempted to deploy iTunes and QuickTime making use of the 2nd method, and what ended up happening can be that when an update for iTunes arrived out, it got destroyed my QuickTime depIoyment because iTunes set up a newer edition of Apple Application Support.
SCCM noticed that the version of AAS that I had made QuickTime reliant on has been no longer set up on my customers and tried (and been unsuccessful) to re-instaIl it. I experienced to move in and update everything to acknowledge the brand-new version of AAS.
On the various other hands, if you simply make use of a script and it attempts to set up an older edition of one óf the MSIs ovér a newer edition, it simply won't perform anything. (In truth, it will fall short with the mistake 'A newer edition of this product is currently installed', but I believe the PSADT snacks this error program code as a 'success'.) As for upgrading iTunes, I have never acquired any issue with simply setting up the brand-new variations of all thé MSIs over top of the outdated variations, so I wouldn't get worried about uninstalling before updating. (This certainly isn't the case for all MSIs, but Apple's seem to become strong.) Move ahead and create an uninstall fór iTunes.msi itseIf if you wish customers to become capable to uninstaIl it through thé Software program Center, but I'd suggest against uninstalling ány of the dépendencies expected to the possible of breaking something else which is dependent on them (like QuickTime).