InigoMontoya Posted June 19, 2013 Report post Posted June 19, 2013 I am able to deploy packages fine, but when a client installs a package it is no longer displayed in the Available Software section of Software Center. So, if there is a problem with a program and it needs to be re installed, does that mean that users would have to click on "Installation Status" or "Installed Software" to find the package again and re install it? I have created a package that clients download locally and it runs a PowerShell script that starts the EXE for the program and then does a few other things. The software installs fine through the script, but in Software Center I can only see the package in the "Installation Status" section which says that it is installed. if I uninstall the software through add/remove programs, and run all of the actions within the configuration manager client - the package stays in the "installation status" section and still states that it is installed. If this is how Software Center is supposed to function, then Microsoft needs to change this. After you install a package or application, you should still be able to view it in the "Available Software" section unless you actually want to set the deployment to expire... Please help Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted June 19, 2013 Report post Posted June 19, 2013 Are you talking about regular packages or application? Packages have no detection rules, so their staus is based on successful execution of the deployment. Once it got executed successfully, it will not be reset again, execpt you chose to reinstall and the deployment fails. If you talk an application that will not return to be available/installable, most likely you detection rule is not configured properly or the uninstall Routine did not clean up correctly. Anyways, sometimes you just Need to press F5 in the Software center to update the views. That's actually the only "bug" in there. Everything else works just fine. They "available Software" grid is only showing new, not yet executed, Installations. Additinally it's listing also not installed applications. Quote Share this post Link to post Share on other sites More sharing options...
InigoMontoya Posted June 19, 2013 Report post Posted June 19, 2013 I realize that "Available Software" only shows new, not yet executed, installations - that is what I am saying is designed poorly. I have tested with a package and with an application, once I installed the application from Software Center, it will forever appear in "Installed Software" even if I uninstall the application from the client. Also, what do you mean detection rules? are you referring to the software inventory cycle schedule? If so, I manually ran all of those actions from the configuration manager client while the application was listed in "Installed Software" but in reality, it was uninstalled from the system. I guess that is the issue - if you uninstall an application that was installed through software center, will it ever show up in "Available Software" again? what Client data detection cycles have to run to detect that the application from Software Center is no longer on that system? and yes, F5 has become my best friend while testing in Software Center... Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted June 19, 2013 Report post Posted June 19, 2013 it will forever appear in "Installed Software" even if I uninstall the application from the client. If you run the application deplyoment evaluation cycle, the Client will check if the application is installed, based on the detection rules defined in the deplyoment type. If the Application is mandatory, it will immediately try to reinstall the app, if it was not detected. So if the conditions of the detection rule will not clean up properly by the uninstall command, the Software will stay in the installed section, because the Client does not recognize that the app got uninstalled. I have seen this only with some old Java runtime Versions when they got uninstalled with the SCCM Client Center for 2007, on a 2012 client. The Problem was that the registry key under HKLM\Software\Microsoft\Windows\currentversion\uninstall has not been cleaned up and the detection rule was pointing to the product code. Also, if you define additional steps in your Installation script, like Setting registry keys or copying files, which are not part of the Setup themself, and base your detection rules on one of them, you also have to provide a uninstall script which removes these items again. A normal uninstall via appwiz.cpl won't work anymore and will leave your Client in this messy state. Check your appdiscovery.log to see what's going on. You can also run the cycle from the command line with this command. WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000121}” /NOINTERACTIVE Quote Share this post Link to post Share on other sites More sharing options...
InigoMontoya Posted June 20, 2013 Report post Posted June 20, 2013 So, are you saying that if you install an application from Software Center, you also have to uninstall that application using Software Center? otherwise it will not detect that the application no longer exists on the machine? Normally (most end users) would use windows add / remove programs to uninstall software that is no longer needed or not working. Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted June 20, 2013 Report post Posted June 20, 2013 Well, like i said: it depends all on your detection rules. If you run a setup without scripted actions around, to adjust additional stuff like copying files or creating registry keys, which are used for detection rules, a regular uninstall trough add/remove programs should just work fine (in most cases). You should always test this before you send one of your apps to production. Software which is no longer needed on a machine will be uninstalled automatically with the uninstall action of the application in our environment. Normal users have no local admin rights to uninstall any software. Quote Share this post Link to post Share on other sites More sharing options...
InigoMontoya Posted June 25, 2013 Report post Posted June 25, 2013 I manage a unique group of users - 95% of them are developers who require local admin rights on their machines. So, I don't fully understand what you are saying. Lets say that I publish a package and it installs fine, but it installs another package first that runs a script to add registry keys - if I uninstall the application from a client through Add/Remove programs, then it would never undo what the original package installed. So if I create custom packages with scripts and or calling other packages first - then they will never leave the "Installed Software" section in software center. How would I configure detection rules for a package? Quote Share this post Link to post Share on other sites More sharing options...
