As Office 2016 has reached the end of (October 2020), it is now in Extended Support (ending October 2025).
You can write XML manually or use Microsoft’s web-based Office Customization Tool (recommended for simplicity).
To uninstall specific products, use <Remove> : office 2016 deployment tool
The ODT operates using two primary components: a engine and a configuration.xml file. You edit the XML file to define your deployment settings and then run the setup engine from the command line to execute those instructions. Common use cases include:
setup.exe /configure config.xml
This downloads Office 2016 source to the folder defined in your XML (add SourcePath if needed).
<Configuration> <Add OfficeClientEdition="64" Channel="PerpetualVL2016"> <Product ID="ProPlusVolume" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"> <Language ID="en-us" /> <ExcludeApp ID="Access" /> <ExcludeApp ID="Publisher" /> </Product> </Add> <Display Level="None" AcceptEULA="TRUE" /> </Configuration> As Office 2016 has reached the end of
For mass deployment via Group Policy or SCCM, you want zero user interaction.