The deployment build scripts run the script below after the install ws build is complete. Sometimes the install MSI files will be created without errors, but they still may be DOA. This happened recently when T&L integrated demos with "-" in their path. The nightly build passed fine, but this introduced a bug with the install Makefiles that made the JDK installer DOA. This wasn't realized until 4 days after the T&L integration, and it delayed Deployment's pit. So all teams should really be running MSI validation after install builds. We should add msi validation to the install Makefiles.

#
# Validate the jre and jdk msi files
#
ValidateMSI(){
  echo "validating the msi files"
  C:/devtools/MsiVal2/msival2.exe O:/links/iftw-60/${BUILD_TYPE}/latest/windows-${ARCH}/iftw/jre1.6.0-iftw.msi C:/devtools/MsiVal2/logo.cub -f
  C:/devtools/MsiVal2/msival2.exe O:/links/iftw-60/${BUILD_TYPE}/latest/windows-${ARCH}/iftw/jdk1.6.0-iftw.msi C:/devtools/MsiVal2/logo.cub -f
  echo "finished validating msi files"
}