Software Deployment

This seems to be along the same topic as repackaging Microsoft Access 2000. Unless what you mean by "repackaging" is different than what the industry generally means, then the best practice is not to repackage it. Note bkelly's reply at : http://itninja.com/question/faulttree-1044

Visio 2000, like Access 2000, is already in a highly manageable and useable native .msi format. Software that is already compiled into well formed .msi format is not to be "recaptured" and repackaged into .msi. I tried "recapturing" and "repackaging" a very simple (which Visio is not) .msi once just as an experiment. The results were not pretty.

Visio 2000 can be customized with the Microsoft Office Custom Installation Wizard. It provides all the customization to an administrative installation point of Visio that is needed. You use it to create an .mst (transform) file that can be applied at the time of installation of Visio.

To take advantage of the transform you have created, you will need to make sure the Windows Installer service has been installed on the NT4 workstation ahead of time. You can then install from the command line, ect, with something like:

msiexec.exe /i "path_to_the_msi" TRANSFORMS="path_to_transform_file" /qn


craig --<>.