Office Installation Errors

Configure a Silent Office Professional Plus 2016 Installation in SCCM

Algirdas JasaitisAlgirdas Jasaitis Nov 22, 2026 868 views

Question details

Configure an SCCM deployment of Office Professional Plus 2016 to install silently without selected components.

Configure a Silent Office Professional Plus 2016 Installation in SCCM
Product
Microsoft Office Professional Plus 2016
Device & OS
not provided
Scenario
Deploy Office through SCCM with a customized component selection and no user prompts.
Observed behavior
Setup behaves like an upgrade and does not complete as expected.
Before you start

Confirm whether the installation source is an MSI-based volume-license package or a Click-to-Run package, and identify any Office versions already installed on the test device. The customization and deployment tools depend on the installation technology.

Solution 1Recommended

Customize and Troubleshoot an MSI-Based Office 2016 Deployment

Use the Office Customization Tool to select components and silent settings, then check SCCM and setup logs if the deployment does not complete.

The Office Customization Tool applies to supported MSI-based volume-license media. Click-to-Run deployments use the Office Deployment Tool and a configuration XML file instead.

Existing Office installations can affect setup behavior. Review what is installed and the intended upgrade or removal settings before changing the deployment.

1
Open the customization tool

From the MSI-based Office 2016 installation source, run setup.exe /admin and create a customization file for the product.

2
Configure the installation

In the Office Customization Tool, open Modify Setup properties and Set feature installation states as appropriate. Set unwanted features to Not Available, and use Licensing and user interface to accept the license terms and set the display level to None.

3
Save and deploy the customization

Save the customization as an MSP file. In the SCCM deployment program, run setup.exe /adminfile followed by the path to that MSP file, and ensure the installation source and MSP are available to the deployment.

4
Check the deployment result

Run the deployment on a test device, then review SCCM client logs, Office setup logs, and the application's detection method. Compare the installed Office products and versions with the intended deployment.

5
Escalate with deployment details

If setup still behaves like an upgrade or fails to finish, contact Microsoft commercial support with the setup logs, SCCM logs, installation technology, and customization settings.

Customize and Troubleshoot an MSI-Based Office 2016 Deployment
Click-to-Run source: If the source is Click-to-Run rather than MSI-based, review the Office Deployment Tool configuration XML and its application exclusion settings instead of using setup.exe /admin.
Free Microsoft Office alternative

Use WPS Office as an Alternative for Everyday Office Work

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for easier migration. It does not fix the Microsoft Office SCCM deployment.

Open and edit Word, Excel, and PowerPoint files, including DOCX, XLSX, and PPTX formatsUse a familiar interface for documents, spreadsheets, and presentationsWork with common Office files when moving between applicationsAccess a free, lightweight suite for everyday office tasks
microsoft office alternative - wps office

Frequently Asked Questions

How do I exclude an Office 2016 component from an MSI installation?

Run setup.exe /admin from the volume-license installation source. In Set feature installation states, set the unwanted feature to Not Available, save the MSP file, and apply it during setup.

How can I make the Office 2016 installation silent?

In the Office Customization Tool, open Licensing and user interface, accept the license terms, and set the display level to None. Save the MSP file and include it in the SCCM setup command.

Why does Office setup appear to run as an upgrade?

An existing Office installation or the deployment's upgrade settings may affect setup behavior. Check the installed Office products, the customization settings, and the Office setup logs before changing the deployment.

Should I use the Office Deployment Tool or the Office Customization Tool?

Use the Office Customization Tool for supported MSI-based volume-license media. For Click-to-Run media, use the Office Deployment Tool with a configuration XML file.

Where should I look if SCCM reports that the installation failed?

Review the SCCM client logs, Office setup logs, and the application's detection method on a test device. If the result remains unclear, provide those logs and the deployment settings to Microsoft commercial support.