Does the agent’s chroot/sandbox allow for installers to write logs? When writing/debugging software installation tasks, it’d sure be handy to tuck away the msiexec log output, or upload it for analysis.
I output my installer logs to the BES Client Logs folder using command line switches. The advantage of the client log folder is that it is grabbed by the existing client diagnostic task.
The way to do this with MSI’s are the same, but other installer types vary.
I use the following naming convention:
install_NAME_OF_SOFTWARE.log
1 Like
So…
"{folder "__Global\Logs" of data folder of client}\install_PRODUCT.log"
That works great. Thanks!
Here is an example:
http://bigfix.me/fixlet/details/3902
This logs to a folder, not a file, which is the reason it lacks the .log extension. Also, this is not an installer task, which is why it doesn’t include “install”
/silent /log "{ (pathname of folder "__BESData\__Global\Logs" of parent folder of client) }\Logs_DellUpdate"
This would be the same as: (using the data folder inspector)
/silent /log "{ (pathname of folder "__Global\Logs" of data folder of client) }\Logs_DellUpdate"