I was recently having some trouble with a software package installation and had to get MS PSS involved. The engineer asked me to run the setup.msi as:
setup.msi /Lvoicewormup C:log.txt
What the heck? That first parameter instructs the MSI to create a log of the installation. The second tells it where to create the log file and what to call it. BTW, that is "worm" and not "warm". Yeah, I know.
In my years of software deployment, I’ve never seen this before. It created a log file of the installation that helped us diagnose the issue.
It struck me that this would make for a great package program in SMS 2003 or SCCM 2007. You could copy one of the unattended programs and modify it to use this logging parameter. This would help you diagnosing any issues you have during testing or trouble shooting of package deployment.