I will second everything about Powershell App Deployment Toolkit. It has many of the features we all wish were natively in ConfigMgr.
BRIAN ILLNER | Canal Insurance Company 864.250.9227 864.679.2537 Fax Visit canalinsurance.com<http://canalinsurance.com> for news and information. [cid:[email protected]] [cid:[email protected]]<https://www.linkedin.com/company/canal-insurance-company> WARNING: As the information in this transmittal (including attachments, if any) may contain confidential, proprietary, or business trade secret information, it should only be reviewed by those who are the intended recipients. Unless you are an intended recipient, any review, use, disclosure, distribution or copying of this transmittal (or any attachments) is strictly prohibited. If you have received this transmittal in error, please notify me immediately by reply email and destroy all copies of the transmittal. While Canal believes this transmittal to be free of virus or other defect, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by Canal (or its subsidiaries and affiliates) for any loss or damage arising therefrom. From: [email protected] [mailto:[email protected]] On Behalf Of Charles Hiland Sent: Tuesday, January 5, 2016 1:04 PM To: [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
