When it comes to installation packaging, the Mentor Install Program (MIP) doesn’t offer anything newer than the “Batch Tool” (batch script/XML) at this time. However, we do have services available to help develop custom packaging to meet your global deployment needs. Refer to the data sheet to read more, and we can set up a time to discuss further if you’d like more information.
Just to let you know.. I create Batch files usig the Mentor Install Program, then wrap these in a script using NullSoft Scriptable Install System (NSIS Wiki ). This creates a self-installable executable that can be distributed for your client installs. It works really well for almost any Windows software, including Mentor. If anyone needs details on this, let me know.
We also create the bat files and write a VBScript as a wrapper around the bat file. The script uninstalls the previous version, then installs the new version and any patches, then makes sure the environment is setup correctly. Our key is that at each location has the same location via the use of DFS links so that everyone sees the same location for the software install files, libraries, and scripts. I've got 14 locations where I support software. Once the install scripts are written, the biggest issue is getting the software replicated at each location. This can take time depending on your network speeds.
What I'd like to find out is how to get/force users to install a patch when it's needed.