Are you certain setup.exe is not being called to reconfigure your O365 client? Another common way of managing updates is to rerun Setup.exe and specify the desired version (this is a common way to do it in SCCM, for example).
If you decide to change these settings, you must update your configuration.xml file, and then run the Office Deployment Tool again.ĪutoUpdates are Enabled in your sample configuration.xml. The update settings in the configuration.xml file are applied to Office 365 ProPlus when you use the Office Deployment Tool to deploy Office 365 ProPlus. Per Technet - Configure update settings for Office 365 ProPlus, With version 2019, Microsoft no longer supports the use of ISOs/MSIs and now uses a Click-to-run (CTR) installer alongside an xml configuration file. Microsoft has changed the way Office 2019 is installed and deployed. Your issue seems focused around the configuration of O365 changing when the update process runs. Office Professional Plus for Windows - 2019. It will not really give you an error if the XML is not parsed correctly (even with verbose logging and a log path configured). (Office 365) Setup.exe is very particular about the XML formatting. lacking.ĭrop the space in the ExcludeApp element between ID= and "Publisher". The syntax listed in the Technet reference here is.
It looks like your syntax is incorrect it should look like this (please note the spaces, or lack thereof): Īlso, be careful about licensing: if the user doesn't actually have a Professional Plus license but instead has a different one, as soon as he/she logs in to any Office 365 application the setup will automatically start and make sure the installed applications match the actual license assigned to the user I witnessed this myself when I erroneously deployed a Professional Plus edition to several computers, only to have the Office 365 setup remove Access and Skype For Business after the first log in of users which actually only had Business Premium licenses (SfB was not physically removed but it was made unusable due to a licensing mismatch: it was installed but it refused to activate, because the Business Premium edition only includes SfB Basic, while the Professional Plus edition includes the full version, and thus now the installed application refused to work).
This is the official reference on how to exclude specific applications from Office 365 deployments. The update installs Publisher and Outlook even though they were excluded in the config and not installed initially. After I log into my Office 365 account, it starts an office update and the update installs some of the excluded items on the system. Office installs perfectly fine and the excluded apps are not on the system after the initial install.
I'll put the ODT, an XML, and a batch file for them into an ISO and say "here, run setup".I'm attempting to install Office 365 2016 through the click-to-run customization and exclude a set of applications. All of them were onboard and right there with me.Īnd if anyone stuck in their old ways just absolutely can't deal. But, once I showed them examples, showed the syntax for various things you can do with ODT, showed them, etc. iso and running setup.exe, they looked at me like I had 3 heads when I was explaining that this won't be how it works in the future. I shared with them my master plan for automated deployment but also wanted them to be comfortable with ODT for one-off installs they'll be doing. I'm planning our deployment & switchover from perpetual/MSI installs to O365 ProPlus/C2R for about 3000 seats. This download is needed for administrators to set up activation for volume license editions of Office 2019, Project 2019, or Visio 2019 by using either the Key Management Service (KMS) or Active Directory. Happened that way with the guys in our support team. I honestly think the very small learning curve of XML files is a little more daunting than Microsoft thinks it is, but once you just see it work, it's stupid easy.