Office 365 ProPlus Installer - Details on how to setup and deploy Office 365 ProPlus 2013 and 2016 using click-to-run technologies

Posted: Thursday, December 22, 2016 11:14:25 PM(UTC)


Member Original PosterPosts: 31

In order to deploy Office 365 ProPlus 2013 and 2016 there are few requirements to download and setup. For our environment we have a dedicated deployment share for all sites for these instructions I will use the \\networkpath\Office 365 for this guide but you will need to replace this with your own network paths.

For our environment, we created the following subfolders:
  • 2013
  • 2016

For each of those folders we created another subfolder:
  • OfficeProPlus

Download C2R setup files:
You need to download the Office Deployment tool for Click to Run for the version you want to deploy and run the setup to extract the files. Copy only the Setup.exe file into the version\OfficeProPlus folder that you are deploying.
2013 file -
2016 file -

Configuration XML Files
Download the attached Office365ProPlusInstall - Silent.xml configuration files that I have already setup and copy them to version\OfficeProPlus folder.
Edit both the XML files with your favorite notepad program to adjust the paths to your environment.

Download source files
Now you will need to create a batch script that will download the source files for your for your office version.
I created a Update_Package - Office365ProPlus.bat script in each version\OfficeProPlus folder with the following commands:
2013 batch - "\\networkpath\Office 365\2013\OfficeProPlus\setup.exe" /download "\\networkpath\Office 365\2013\OfficeProPlus\Office365ProPlusInstall - Silent.xml"

2016 batch - "\\networkpath\Office 365\2016\OfficeProPlus\setup.exe" /download "\\networkpath\Office 365\2016\OfficeProPlus\Office365ProPlusInstall - Silent.xml"

After the download finishes, you will be ready to import the Lansweeper Deployment package and deploy Office 365 ProPlus 2013 or 2016.

You can also use this method to deploy other Office software provided in your Office 365 subscription such as VisioPro or ProjectPro.

*** I have updated this deployment package to include the OffScrub.vbs scripts and a method to uninstall all previous versions as indicated by several comments.
Edit Line #4 in Pre-OfficeUninstall.ps1 script to the network path that you will store the linked Remove-PreviousOfficeInstalls.ps1 files here!AubfyF65XTIkg7MWSArLt6IztbnPtg
Handles attachments (1kb) downloaded 214 time(s). (1kb) downloaded 900 time(s).
Deploy Office 365 ProPlus 2016 x32Download Package
DescriptionDeploy office 2016 x32
Final ActionNothing
Max. Duration0 min(s), 2 hour(s)
1. Prep Uninstall
Return Codes 0,1641,3010
SuccessGo To Step 2
FailureStop (Failure)
Command powershell.exe -ExecutionPolicy ByPass -File "\\networkpath\Remove-PreviousOfficeInstalls\Prep-OfficeUninstall.ps1"
2. Check for Mimecast x64
SuccessGo To Step 3
FailureGo To Step 4
File C:\Program Files\Mimecast\Mimecast Outlook Add-In musepkg64.exe Exists
3. Remove Mimecast x64
TypeMSI Uninstaller
Return Codes 0,1641,3010
SuccessGo To Step 4
FailureStop (Failure)
Software Name Mimecast for Outlook 64-bit
Software Version 7.0.1762.17740
4. Run Uninstall Scripts
Return Codes 0,1641,3010
SuccessGo To Step 5
FailureStop (Failure)
Command powershell.exe -ExecutionPolicy ByPass -File "C:\~O365Temp\Remove-PreviousOfficeInstalls\Remove-PreviousOfficeInstalls.ps1"
5. Install Office 365 Business
Return Codes 0,1641,3010
SuccessGo To Step 6
FailureStop (Failure)
Command "\\networkpath\Office ProPlus\setup.exe" /Configure "\\networkpath\Office ProPlus\2016\configuration.xml"
6. Remove Temp Folders
Return Codes 0,1641,3010
SuccessStop (Success)
FailureStop (Failure)
Command rmdir C:\~O365Temp /S /Q
#1wxfisch Member Posts: 11  
posted: 1/30/2018 7:09:27 PM(UTC)
This is good, and I have a deployment setup similar to this, however we need to uninstall Office 2013 and 2010 from client PCs prior to installing Office 365. Currently I am checking a registry key (word.application CurVer) to determine which version of office is installed, and then trying to use the Setup.exe /uninstall command to to uninstall office silently (using a configuration.xml file to tell it to run silently). I have two problems though:

First, is that the uninstaller does not seem to run at all. I have tried various batch scripts and command line deployment options, it always throws an error that /uninstall is not a valid switch (which it clearly is, it works when I run it manually)

Second is that the deployment commands do not wait for the installer (and I am guessing the uninstaller) to finish before moving to the next step, which for the installer is success. I need to know that the installation actually was successful, not that it was started successfully, as well as ensure that the uninstall of the old versions finished before moving onto installing the new versions.
#2joshmaline Member Posts: 9  
posted: 2/15/2018 11:50:28 PM(UTC)
Our MS velocity team pointed us to the Offscrub utility (.vbs script), There is a different scrubber for each version of office you run and you can switch on/off what products you wish to uninstall or just use the /ALL switch to wipe it clean. I found the scripts out there on github, but this is the article they pointed me to on how to use them for 07, you can search github for 10, and 13. Offscrub article

#3keys_it Member Original PosterPosts: 31  
posted: 6/12/2018 7:29:54 PM(UTC)
I have updated the package with additional scripts to meet those needs. We had to tackle this issue for a new environment sometime last year but I never thought about updating the package on here.
#4maltenburger Member Posts: 1  
posted: 8/9/2018 3:20:24 PM(UTC)
Thanks so much for taking the time to post this. This is very helpful.

#5Lewis_Spokane Member Posts: 14  
posted: 5/10/2019 4:30:45 PM(UTC)
Question: Step 5 command, do you need the quotes around the network path?
#6Lewis_Spokane Member Posts: 14  
posted: 5/10/2019 8:14:09 PM(UTC)
How to verify that it worked?

My update path is the CDN and not a network share. Will it not check the CDN until the regularly scheduled time?

I changed the channel on my own machine to "targeted" which should put me at version 1902 but I'm still sitting on 1808 after deploying the package and restarting my machine.

edit: Since deploying the package I'm getting a lot of errors in Event Viewer that say Windows Update Failure 3
#7CyberCitizen Member Posts: 415  
posted: 5/13/2019 2:41:54 AM(UTC)
Originally Posted by: Lewis_Spokane Go to Quoted Post
Question: Step 5 command, do you need the quotes around the network path?

Yes because if there is any spaces in your network path, dos won't get there unless you have wrapped the path in quotes.

I am deploying office like below.

"{PackageShare}\Office 365\2016\OfficeProPlus\setup.exe" /configure "{PackageShare}\Office 365\2016\OfficeProPlus\Office365ProPlusInstall - Silent.xml"

Active Discussions

Lansweeper Recording history of IP address for device
by  Steven R   Go to last post Go to first unread
Last post: Today at 1:58:33 AM(UTC)
Lansweeper LSAgent Wrong Domains for Users
by  Notonyourradar  
Go to last post Go to first unread
Last post: Yesterday at 10:13:32 PM(UTC)
Lansweeper LsAgent for Ubuntu 12 i686
by  MaxGas   Go to last post Go to first unread
Last post: Yesterday at 10:00:00 AM(UTC)
Lansweeper Lansweeper custom report
by  Arelan  
Go to last post Go to first unread
Last post: 4/9/2021 4:22:46 PM(UTC)
Lansweeper Bulk Update Scanning Schedules
by  Hendrik.VE   Go to last post Go to first unread
Last post: 4/9/2021 1:45:41 PM(UTC)
Lansweeper Consulting Assets With an Expired License
by  Hendrik.VE  
Go to last post Go to first unread
Last post: 4/9/2021 9:48:31 AM(UTC)
Lansweeper Ticket visibility for non-agents
by  Arno Butter   Go to last post Go to first unread
Last post: 4/8/2021 5:17:03 PM(UTC)
Lansweeper Powershell scripts and deployment
by  roysam  
Go to last post Go to first unread
Last post: 4/8/2021 4:07:54 PM(UTC)