MSI Package Builder allows you to automatically monitor the changes performed by a single installation or a set of installations and create a deployment package based on these changes. When multiple installations are monitored, they are launched one by one in the specified order. To perform automated monitoring you should choose the Automated Monitoring option in the Repackage Installation wizard.
Let us take a look at the automated monitoring process configuration. Firstly, you should specify a name for the project to be created on a basis of the monitored changes, provide a set of installations to be monitored and define the installation order Pic 1. You can define command-line parameters to be passed to the installer application for each installation while adding it. It is possible to monitor Windows Installer packages, Microsoft Software patches and executable installation packages.
On the next step, you are about to choose if you would like to create an MSI package, an App-V package or an MSIX/AppX package on a basis of the monitoring results.
In case you have chosen to create an MSI package, the next step is to provide a path to save a resulting MSI package to and configure the package. The detailed information about an MSI package configuration is available in the Creating MSI Package section of this document. If the App-V package output has been selected, during the next step you can provide a path to save the resulting App-V package to and configure the package. Detailed information on the App-V package configuration is available in the Creating App-V Package section of this document. As for the MSIX/AppX package output, you can provide a path to save the package to, define the package configuration options, target platforms and digital signature settings. Refer the Creating MSIX/AppX Package section of this document for details.
As for the monitoring filters, you can define additional processes to be filtered choosing them from those currently running Pic 4.
A wrong processes monitoring filters configuration may lead to improper installation monitoring if the activity of the process required by the installation. You must not filter the processes when you are not sure if their activity can affect the installation results. Otherwise, the deployment package built as a result of such monitoring will not be able to perform the same installation.
It is also possible to add/remove any process from those currently running to/from the persistent monitoring filters, such as change the persistent monitoring process filters configuration using a corresponding hyperlink.
After you press Finish the monitoring process is started and as soon as it completes a deployment package is created containing the monitored changes in the specified location.
When does the monitoring process stop?
When a monitoring process is running, you can see the monitoring progress on a screen Pic 5. It displays how many installations from those defined are already complete.
As soon as all the installations are complete, the monitoring process is stopped automatically. The installation is treated as completed when the installer process and all the processes daughterly to the installer process exit.
Please note that if the setup wizard suggests running the installed application upon the installation completion, you should decline this suggestion. Otherwise, the monitoring module will wait for the started application to exit.
You can abandon the monitoring process using the Stop button at any time, although it is not recommended.
The automated monitoring process does not stop. Which option should I choose?
You can face the situation, when you have passed through all the steps of the setup wizard, but the automated monitoring process does not stop. To choose further steps, it is required to understand what leads to this situation. Let us take a closer look at the list of possible reasons and appropriate solutions for each one.
Firstly, the monitoring process may not be stopping because the installation is still performing the application configuration in background. Thus, it is recommended to be patient and always wait for some time after the installer application user interface has closed.
Another possible reason is that the monitored installation has launched the installed application or one of its modules. This can happen if you have not unchecked an appropriate option on the installation wizard finish page, or if the installation always performs the step of launching the installed program. Please note that those executable modules can be run in the background or minimized to tray. In such a case, you should close the launched applications and continue waiting for the monitoring to stop automatically. The monitoring module will switch to next installation, if any, or create the deployment package, if this installation is the last one from those monitored, as soon as those applications are closed. In case if it is not possible to close the launched applications, but you are sure that the installation is fully complete, you can stop the monitoring process manually and create the deployment package based on the changes currently monitored by pressing the Stop button and then choosing the option to proceed with creation.
It is not recommended that the automated monitoring process be stopped manually to proceed with the deployment package creation unless you are positively sure the installation is fully complete. In case the setup is still in progress, the repackaging will be incomplete.
The last reason is that the installation does not fulfill the requirements for automated monitoring (the process performing the installation does not exit after the setup is complete). If you are not sure that the installation process is fully complete and cannot find out the processes that are preventing the automated monitoring from being completed, you can abort the monitoring process by pressing the Stop button and then choosing the Abort Monitoring option. All the monitored changes will be irreparably lost. In such a case it may be convenient for you to use repackaging via wrapping.