5/20/2019 0 Comments Wmic Uninstall Office 2010Earlier this year I did a presentation at the Central Texas Systems Management User Group (CTSMUG) in Austin on migrating our company to Office 2016 (MSI). I have provided a link to my of that presentation for some general context however this blog post will be a more technical explanation of how I went about upgrading all our systems to Office 2016. ![]() I had this issue when trying to uninstall and reinstall Web Deploy using wmic via a batch file. It did not help running the batch file with elevated privileges. Uninstall of Lync 2010 We are in the middle of rolling out O365 Pro Plus on Win 7 and I was wondering if there was a script to uninstall Lync 2010? I have the OffScrub10.vbs script that removes the Office 2010 suite, but Lync is not included in that suite, therefore is left on the PC once the script is complete. Prerequisites • Working knowledge of ConfigMgr 2012/Current Branch Task Sequences. • An existing Application/Package for installing Office 2016/365, Visio, Project, etc. (If you need assistance with this, there is plenty of guidance and ) Before we get going, we need to create a new package called “Office 2016 Upgrade Files”. This package will consist of detection scripts, Office Scrub scripts and any other custom code used for your overall upgrade process. (NOTE: This package should NOT contain any of the actual Office installer binaries). New-CMPackage -Name 'Microsoft Office 2016 Upgrade Files' -Path ' SERVER SOURCES Microsoft Office 2016 Upgrade Files' Content Start by downloading the following scripts: • – I developed this script to detect as many Microsoft Office (non-server) products that I had in my environment (NOTE: The language packs section needs improvement to cover more languages). • – This cleans up registry keys associated with the Office IME (Input Method Editor). Next, use the “Easy Fix Download” link to obtain and extract the Office Scrub scripts for Office 2010+ • Extract the OffScrub10.vbs and add it to your Office Upgrade package: • Extract the OffScrub scripts from the EasyFix download and add them to your Office Upgrade package: Task Sequence – Detection Start out by creating a new (empty) Custom Task Sequence. The first stage of our Task Sequence will include detecting the software currently installed on the system. This is broken out (generally) into two different groups. • Microsoft Office Suites and Applications (i.e. Free download font cool jazz apkhere. The best website for free high-quality Cool Jazz Apk fonts, with 25 free Cool Jazz Apk fonts for immediate download, and 56 professional Cool Jazz Apk fonts for the best price on the Web. Visio, Project, Language Packs) • Office-Dependent Applications – Other software packages that have a dependency on one or more Office applications that may need special attention (reinstall) during an Office upgrade. Removal The next section will contain various scripts and command lines that we’ll use to remove Office-Dependent products and Office itself. First off, create a group (generally via WMI query or a file check) to detect and remove each application. Be sure to add a custom Task Sequence variable as indicated in the screenshot above so you can use that to re-install the software later. You “CAN” upgrade Office in-place without removing previous suites, however I always run into legacy shared components that get left behind. When these are left behind, the system still downloads ALL of the updates for the full suite (including service packs) so I prefer to perform a rip and replace of the Office suite. Once you have removed the Office-Dependent applications, the next set of steps will systematically remove Microsoft Office. I’ll list this out in order of how we did it as we had excellent success with this specific order of operations no matter what the system had installed. • Remove Microsoft Office – This uses the Get-MSOfficeProducts.ps1 script from the Detection step but with the added –Uninstall parameter. ![]() This step works well to remove Office 2003 components and some of the newer components using standard methods. NOTE: There is an Office Scrub script for available however I never verified that it worked. • Uninstall Office 2007 – I used the main Office 2007 Professional Plus installation media with custom to remove SharePoint Designer, Proofing Tools and the rest of the suite (in that order) since I already had the original package used to install it. I’m not doing anything else related to Visio/Project or Language Packs during this section. NOTE: There is an Office Scrub script for available however I never verified that it worked. • Uninstall Office 2010/2013/2016 – Microsoft has published “scrub” scripts for each version of Office that work incredibly well.
0 Comments
Leave a Reply. |