When we first introduced MSI, there were several occurances where non-install team changes would break the msi validation. The build would pass, and the msi may even run correctly, but MSI validation would fail. These were usually situations where teams would introduce files or directories with strange characters in them (-, ~, /, etc). We would find this out way too later, and be in crisis mode. So we introduced the running of MSI validation (MSIVAL tool). All teams have had to run this tool, to ensure their changes didn't break automation. Over the years, we've refined our MSI Makefiles to not allow most of the breakage to happen. Everytime we'd uncover an issue, we'd address it in the Makefile/Makefile-scripts so that we could support the particular change.

There are several reasons why it's time to remove this tool from the build:

-It's been years since any teams have introduced MSI validation errors. Are Makefiles can handle basically any changes to the jre/jdk images
-It's an extra hassle/step in the build machine setup
-This tool doesn't have a proper Makefile sanity check, it currently gives a weird error if it's not installed. We've run into lots of trouble trying to debug this for many teams. It would be an extra effort to add this sanity check.
-Kelly O has had issues installing this tool on headless JPRT tools. This has made it very difficult to add the install repo building to the JPRT build.

We can add this validation to our DS build scripts, or even to our SQE automation suites. It does not need to be part of the build for all teams.