My organization primarily uses Application Catalog for users to self service themselves... (service desk installed a licensed program last year to 3500 computers by accident by adding one collection to another,
so we are now self service and use the Application catalog for 99% of installs, we have basically moved away from computer based collections and utilize the Application Catalog for all software)
I have users in my environment that have SO many different versions of Java for legacy software and installing the new one does not uninstall some of the other versions of Java thus there is a conflict on the system. I have the all the installs published for all different versions that are out in the field in the Application Catalog AND I have a script that uninstalls all versions of Java so that they can uninstall the wrong ones and then go back and install the ones that they know they need after.
I use a script to run the uninstalls, then have it echo out a file and the detection method sees the file and congratulates the program and declares it a success. BUT users want the ability to uninstall and reinstall without contact service desk to be able to re-run it - the file already exists and can not be ran again... thinks it is already completed.
how do I get the system to be able to re-run an application so that the APPLICATION can run several times when launched from Application Catalog to suit the users needs. I don't want to keep adding computer to collection or having user contact the service desk to delete the detection file so that it can be ran again...
i.e. user uninstalls Java, installs correct verstion for what they need today - run the uninstall application again, then run the other version of Java they want tomorrow.
is there a way SCCM to detect that program is uninstalled and pass the success back to the console to say that the program is a success? or any other method so that the application can be ran - sometimes MULTIPLE times just like this Java application?