This post covers the steps to deploy Office 365 Proplus using SCCM. There are multiple methods to deploy Office 365 proplus using SCCM. However in every method a configuration file is used along with Office 365 deployment. The SCCM Office 365 Installer feature was first released in SCCM 1702. Since then lot of enhancements have been made to the tool. In this post I am using SCCM 1806 to create Office 365 installer. I believe this is the most easiest method to deploy Office 365 proplus using SCCM.
Before you deploy Office 365 using SCCM, I would also like to add a point here about the Office 365 installer. When you create office 365 installer using SCCM, there is no uninstall command added in deployment type. Not sure why but i assume you would use only Office 365 post deployment. In addition you can still add the uninstall command but why would you do that ?.
Deploy Office 365 ProPlus using SCCM
To deploy Office 365 proplus using SCCM, launch the configuration manager console. Click Software Library > Overview > Office 365 Client Management. Click Office 365 Installer in the console. This will bring up Microsoft Office 365 client installation wizard.
Under Application settings you specify name and content location. The content location is the path where the Office 365 installation files are downloaded. Click Next.
Click the button Go to the Office Customization Tool.
Office 365 Customization Tool
You will see Office Customization tool launched. This tool will create the configuration file for all the changes that you do. You can customize a lot of settings. And the settings are deployed along with Office 365. To create or update a configuration file, click Next link in the tool.
This is very important step. Look into right pane to see changes that you make.
- Select Organization name. Click Add button.
- Select the office version. In most cases 32-bit office version is deployed. Click Update button when you make any changes.
- Next, select the Office version. The best part here is you can select what office apps you want to deploy.
What’s available under Software ?
- Office Suite – Includes Office 365 ProPlus and Office 365 Business.
- Visio – Includes Visio STD and PRO 2016, Visio Pro for Office 365.
- Project – Includes Project STD and PRO 2016, Project online desktop client.
Select Primary language. You can add additional languages if required. When you add addition language, click Update button.
Select the installation channel and version of Office 365. I always prefer to have the latest version of office 365 deployed.
Under Upgrades, you find two very important options.
- Automatically upgrade 2013 click-to-run based office products.
- Automatically remove all prior version MSI products.
Select the options based on your requirement and proceed to next step.
Under Licensing and display settings, there is not much you can change. The default one is KMS client key.
Lot of options under Preferences. Select the office app first and then customize the settings on right pane.
Select either Yes or No to deploy the application now. Click Next.
Choose the collection to which you want to deploy this application. Click Next.
Configure the deployment settings. Click Next.
For remaining steps, click Next and on completion page click Close.
Office 365 ProPlus Configuration File
Here is the office 365 proplus configuration file that you get once you customize with above settings.
<Configuration> <Add OfficeClientEdition="32" Channel="Broad" OfficeMgmtCOM="TRUE" Version="16.0.9126.2275"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <ExcludeApp ID="Access" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="OneNote" /> <ExcludeApp ID="OneDrive" /> <ExcludeApp ID="Publisher" /> </Product> </Add> <RemoveMSI All="TRUE" /> <AppSettings> <Setup Name="Company" Value="PD" /> </AppSettings> </Configuration>
Testing Office 365 Installation
Launch software center on client machine and select the Office 365 app. Click Install, the application is first downloaded from DP and installed.
While the app is installing, open Appenforce.log to monitor the installation.