FabianL Posted December 30, 2015 Report post Posted December 30, 2015 Hello, We are currently running SCCM 2012 R2 in our environment. We are running a Primary Site server with Endpoint protection and started using OSD. So far it has been a challenge but the guides here and on other online resources have been a tremendous help. We now want to leverage SCCM's capabilities to help us identify rogue software as well as try and make sure that our environment PC's are using a safe version of Java, Adobe Flash, Adobe Reader, etc. Could SCCM help us with this? Also once that software is identified would we be able to uninstall the rogue software and install a correct version of Java, Adobe Flash, etc. If so could someone with more experience provide some insight as to how I would configure something like this? Thank you! Quote Share this post Link to post Share on other sites More sharing options...
YPCC Posted December 31, 2015 Report post Posted December 31, 2015 Most definitely can be done, and the more that you want automated, the more tedious the initial configuration will be (dynamic query collections, uninstall packages, config baselines etc). Youd be pulling together multiple features but could in theory automate the whole rogue software uninstall process. Much depends on what you classify as "rogue" software. If you are not fully co.fortable woth sccm i'd start basic. Go to assets and compliance > inventoried software. Search for names of rogue software like 'torrents', 'java' etc. Will give you a overall view of whats in use in your environment. Once you have names of software you want to uninstall, design a query that lists these names, version and uninstall string of your rogue software. Using the results of the query, you can create a script to uninstall the rogue software in one hit or segregate it. Theres a lot more to this, if you need further info i can follow up. At a high level what you want to do is: - Determine what rogue software is in use - Define a baseline of software you want (latest Java, latest Flash etc) - Deteine if you want instant remediation of noncompliant machines or if you are happy to accept a 1 week or so timeframe. (Hw/sw inventory runs once per week by default whereas a compliance baseline could be set to run much more frequently thus giving you a faster result) - Establish a uninstall mechanism (script, in hours, out of hours etc) - Maintainibility, what will you do when a new Java comes out. How easy will it be to update the exisiting setup to cater for this. Lots of consideration as you can see. Quote Share this post Link to post Share on other sites More sharing options...
FabianL Posted January 1, 2016 Report post Posted January 1, 2016 Thank you YPCC! I really appreciate the information you provided. I will start working on this and get back to you if I have additional questions. Happy New Year! Quote Share this post Link to post Share on other sites More sharing options...
