You don't have to meter software just to find it whether or not it has been used. This data in in AI. BDNA even normalizes it. I blogged this 3 years ago....
My blog uses normalized data but the same can be done without normalized data, it's just a little more work. http://myitforum.com/myitforumwp/2013/01/07/tracking-automatic-software-removals/ ________________________________ John Marcum MCITP, MCTS, MCSA Desktop Architect Bradley Arant Boult Cummings LLP ________________________________ [H_Logo] From: [email protected] [mailto:[email protected]] On Behalf Of Duncan McAlynn Sent: Tuesday, January 5, 2016 12:45 PM To: [email protected] Subject: [mssms] RE: MS Project Uninstall To extend Charles' thoughts here for a second... This is a process that can be easily automated based upon Software Metering data, Software Inventory data and Collection usage. The framework: Collection #1: Based on SWI data, systems with Project installed Collection #2: Based on SWM data, systems with Project installed (limiting collection based upon #1) but not used within the past 90 days Collection #3: Based upon whatever criteria necessary to specify which users should be able to install Project through the Software Center Advertisement #1: Using the information provided below for the removal, target collection #2 with the uninstall command line. This should be a daily recurring advertisement. As new systems hit the 90 day threshold, they have the software removed and the license is reclaimed. (NOTE: some EULAs do not permit the immediate usage of the license and require a shelfing period before it can be re-used on another system. Check with your vendor.) As systems fall into collection #1, if they go the specified time period without using the software, they will then fall into collection #2 and have the software removed. Upon refresh of their SWI data, they will subsequently be removed from both collections while users in Collection #3 will continue to be able to re-install the app through the Software Center. Hope this helps.. HAPPY NEW YEAR! Duncan McAlynn, Sr. Solutions Specialist, Americas HEAT Software M: +1.512.391.9111 | [email protected]<mailto:[email protected]> HEAT Software | 490 N McCarthy Blvd. Suite 100 | Milpitas, CA 95035 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Charles Hiland Sent: Tuesday, January 05, 2016 12:04 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: MS Project Uninstall I am doing this in my environment right now, actually. I use PowerShell App Deployment Toolkit<http://psappdeploytoolkit.com/> for my SCCM deployments whenever possible. There is a slight learning curve, but nothing you shouldn't be able to handle if you're already using SCCM, and once you learn it, you will probably want to use it every chance you get. The documentation is well written and the steps are pretty straight forward. The uninstall string within the PowerShell script itself is: Execute-Process -Path 'setup.exe' -Parameters '/uninstall PrjStd /config "PrjStd.WW\config.xml"' Of course you would want to edit your config.xml to suit your needs. We reclaim applications that haven't been used in 90 days, but leave the application as an available install in the software center should the user need it again. This uninstall requires that the application be cached again, but it's not a big deal as it is a relatively small deployment. Hope this helps. -Charlie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gerding, Matt Sent: Tuesday, January 05, 2016 12:47 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] MS Project Uninstall Does anyone have a best practice approach in SCCM 2012 R2 for deploying an uninstall of Microsoft Project Standard x86 2010? I am new to SCCM and recently created a package for project, which was inadvertently deployed to a significant amount of PC's within my company. I have attempted to deploy an uninstallation package using the cmd msiexec.exe /x {GUID}, which was acquired from the registry of a local machine that had Project installed on it. Unfortunately, my attempts so far have been unsuccessful. Thanks, Matthew Gerding Information Technology Centurion Medical Products [email protected]<mailto:[email protected]> 517.540.1618 ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer.
