Find Microsoft Office 2016 Standard MSI Command-Line Installation Documentation
Question details
The user needs documentation for modifying an Office 2016 Standard MSI installation and deploying changes across multiple computers.

- Product
- Microsoft Office 2016 Standard, Windows Installer (MSI) edition
- Device & OS
- not provided
- Scenario
- An administrator wants to add installed features and understand supported setup.exe parameters, MSP files, and deployment procedures.
- Observed behavior
- The relevant Microsoft documentation appears unavailable, leaving the administrator without confirmed instructions for the specific MSI edition.
Confirm that the installation media is for Office 2016 Standard MSI, not a Click-to-Run edition, and identify whether you are customizing a new installation or changing an existing one. Keep the media's setup.exe, configuration files, and any MSP files available when reviewing deployment guidance.
Locate Microsoft deployment documentation for Office 2016 MSI
Use edition-specific documentation to identify supported Setup options, customization tools, and feature-modification procedures.
Office 2016 MSI deployment differs from Click-to-Run deployment. Instructions for the Office Deployment Tool do not replace Windows Installer guidance for this edition.
Open Microsoft Learn and search its previous-version documentation for “Office 2016 Windows Installer deployment,” “Office 2016 Setup command-line options,” and “Office Customization Tool Office 2016.” Check that each result applies to MSI-based Office rather than Click-to-Run.
Open the Office 2016 Standard installation media and inspect the product-specific folder containing Config.xml. Use its product information alongside the matching Microsoft documentation to confirm the product ID; do not substitute an ID from another Office edition.
In the MSI deployment documentation, locate the sections covering Setup configuration, installation customization files, modifying an existing installation, and applying updates. Check the documented scope of each setup.exe parameter before combining it with a configuration or MSP file.

Request edition-specific guidance from Microsoft enterprise support
Use an administrator-focused support channel when archived documentation is missing or does not explain the required modification.
Use WPS Office for everyday document work without Office 2016 MSI deployment
WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation tasks. Its familiar interface and Microsoft Office file compatibility help users migrate smoothly, but it does not repair Office 2016 MSI installations or replace Microsoft's enterprise deployment guidance.

Frequently Asked Questions
Can I use the Office Deployment Tool for Office 2016 Standard MSI?
No. The Office Deployment Tool is intended for supported Click-to-Run deployments, not Office 2016 MSI installation media. Search Microsoft Learn's previous-version documentation for Office 2016 Windows Installer deployment and Setup options.
Where can I confirm the product ID for my Office installation?
Inspect the product-specific Config.xml file on your Office installation media, then compare its product information with the documentation for that exact edition. If the mapping is unclear, provide the edition and media details to Microsoft enterprise support rather than guessing an ID.
Is a customization MSP file the same as an Office update MSP file?
No. A customization MSP created with the Office Customization Tool stores installation settings, while an update MSP contains a software patch. Consult the corresponding customization or patching documentation before choosing how to apply it.
Where should I ask if the old TechNet documentation or forum is unavailable?
Use Microsoft Q&A or your organization's Microsoft support portal. Include “Office 2016 Standard MSI” in the question title and explain whether you are performing a new installation, adding features, or applying patches.
Can WPS Office fix my Office 2016 MSI deployment commands?
No. WPS Office does not manage Microsoft Office MSI installations, product IDs, or MSP deployment. It can serve as an alternative for editing Office-format files when your workflow does not require Microsoft Office-specific features.




