
Disable this if you require your users to accept the EULA when opening Office for the first time.Ĭonfigure the default file format. I did not select to uninstall Visio and Project as I’m also not installing these with this installation package.Īutomatically accept the EULA on behalf of your users prevents the EULA from being displayed the first time a user opens Office. The upgrade options is a feature that allows M365 Apps / Office 365 to remove previous installations of Office, and even upgrade between different architectures (32-bit 64-bit). Log files are by default stored in the %temp% folder. Microsoft should remove that option from this wizard to avoid the confusion. Logging is no longer supported in the Office Deployment Tool so go ahead and disable that. Select the primary language, and any additional languages and proofing tools to be installed. Background service for Microsoft search in Bing is also something I don’t need to install. I also don’t want to install Skype for Business as I selected Teams to be installed in this package. Note that OneDrive (Groove) is out of support from Januand should not be selected or installed. Select the Office products you want to install as part of this M365 Apps / Office 365 installation. I did not select any Visio, Project or any other additional products. I select the 64-bit version and Microsoft 365 Apps for enterprise as the office suite, and “Monthly Enterprise Channel” as the update channel. The office customization tool will open up. Enter a description if you like (optional), and click next to continue.Ĭlick the “Go to the Office Customization Tool”. MEMCM downloads the source files to this location. I use Microsoft 365 Apps for Enterprise in the name while writing this guide.

The Microsoft Office 365 Client Installation Wizard will open.

Navigate to “Software Library -> Office 365 Client Management” and click on Office 365 Installer. The Office Customization Tool used by MEMCM also don’t support the configuration to set the installation as silent (hint Microsoft, please update that), and we will fix that as well to ensure we end up with a M365 Apps / Office 365 installation package that installs silently. The name Office 365 is thoroughly worked into my blood, but I will try to stay consistent with the new name in this guide. MEMCM at version 2010 (or ConfigMgr or SCCM etc) have not updated their console, and still call M365 Apps by it’s old Office 365 name. Note: Microsoft rebranded Office 365 to Microsoft 365 Apps. This guide will show you step by step how to create the M365 Apps installation package using the built-in installer in MEMCM. How to Install M365 Apps with MEMCM Installer.
