Diagnosing enterprise installer failures can be difficult, as error information may be in any or all of:
- msiexec's log
- Chrome's log (C:\Windows\Temp\chrome_installer.log)
- Google Update's log (C:\ProgramData\Google\Update\Log\GoogleUpdate.log)

Admins probably know how to run "msiexec.exe /l*vx foo.log /i GoogleChromeEnterprise.msi" to get the first log, but the other two often require many back-and-forths. It would be super awesome if Chrome's and Google Update's logs were automagically included in the MSI log.

MsiProcessMessage from a custom action may be the way to do this. To make it really nice, such logging should only include the portions of the Chrome and GU logs that pertain to the install at hand.