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. You “CAN” upgrade Office in-place without removing previous suites, however I always run into legacy shared components that get left behind. 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. First off, create a group (generally via WMI query or a file check) to detect and remove each application. The next section will contain various scripts and command lines that we’ll use to remove Office-Dependent products and Office itself. 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.Microsoft Office Suites and Applications (i.e.This is broken out (generally) into two different groups. The first stage of our Task Sequence will include detecting the software currently installed on the system. Start out by creating a new (empty) Custom Task Sequence. Office 2013/2016/365 Scrub Script Extract the OffScrub scripts from the EasyFix download and add them to your Office Upgrade package:.Office 2010 Scrub Script Extract the OffScrub10.vbs and add it to your Office Upgrade package:.Next, use the “Easy Fix Download” link to obtain and extract the Office Scrub scripts for Office 2010+ IME14-Cleanup.ps1 – This cleans up registry keys associated with the Office IME (Input Method Editor).Get-MSOfficeProducts.ps1 – 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).Start by downloading the following scripts: New-CMPackage -Name 'Microsoft Office 2016 Upgrade Files' -Path '\\SERVER\SOURCES\Microsoft Office 2016 Upgrade Files' (NOTE: This package should NOT contain any of the actual Office installer binaries). This package will consist of detection scripts, Office Scrub scripts and any other custom code used for your overall upgrade process. (If you need assistance with this, there is plenty of guidance here and here)īefore we get going, we need to create a new package called “Office 2016 Upgrade Files”. An existing Application/Package for installing Office 2016/365, Visio, Project, etc.Working knowledge of ConfigMgr 2012/Current Branch Task Sequences.
![microsoft office 365 2016 c2r download x64 microsoft office 365 2016 c2r download x64](https://1.bp.blogspot.com/-_TGYPy_KefI/WLGb0su40GI/AAAAAAAACXo/BFohmD0_ROA0VaQMP8T9u9xEbXUG87rCwCLcB/s1600/customize%2Boffice%2Bc2r%2Binstallation.jpg)
I have provided a link to my Sway 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. Earlier 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).