According to Configuration options for the Office Deployment Tool: Is there anything like this that allows verbose logging, or any other form of debugging, for installs using the Office Deployment Tool with Office 2016?

However, this is specific to the old installation procedure which appears to have been per application ('a verbose log for the install of the Word component, one for Excel, and so on'), whereas my understanding is that ODT (introduced with Office 2013) installs them all as one. To enable verbose logging you will want to set the following registry keys. We will have a verbose log for the install of the Word component, one for Excel, and so on. With verbose MSI logging enabled we will get a verbose log file for each component that Office 2007/2010 installs. In Office 2007/2010 there is a setup.exe log file that gets created by default, but it does not give the amount of detail that is usually required to diagnose an installation failure. The first thing to do when troubleshooting Office install failures is to ensure that MSI verbose logging is enabled. The problem is compounded by the fact that I can't see any way to get information about what ODT is actually doing - it simply gives this vague status message, and no other information beyond error messages (and I've extracted as much relevant info from those as I can).Īccording to this MS blog article from 2010, for earlier versions of Office it was possible to enable 'Verbose logging' for their installers: I'm having a difficult issue with installing Office 2016 using the Office Deployment Tool (ODT).

Office 2019 standard configuration.xml