With MSI Package Builder you can track changes made to your operating system and create a deployment package based on these changes. With the help of the monitoring technology, you can easily create an MSI, an App-V or an MSIX/AppX package from any installation you want and even on any changes you performed manually. Just start monitoring, perform the changes and stop monitoring – the new project created will contain all these changes. You can launch the advanced monitoring with an ability of creating a deployment package on completion choosing the Advanced Monitoring option within the Repackage Installation wizard.
Within the scope of the monitoring process configuration, first you are proposed to provide a name for the project to be created as the monitoring results. This project will contain all changes performed by the running processes to the operating system during the monitoring session.
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 Pic 2. 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 was selected, during the next step you can provide a path to save a resulting App-V package to and configure the package. The detailed information about an 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 3.
The wrong processes monitoring filters configuration may lead to improper installation monitoring if the activity of the process required by the installation to succeed is ignored. 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.
As soon as you press the Finish button, the monitoring process is started, and since that moment until the moment when you stop it, all changes except those skipped in view of the monitoring filters configuration are recorded and saved to the specified project. The deployment package based on these changes is created at the specified location.
When should I stop the monitoring process?
While using an advanced mode for monitoring changes, the monitoring process cannot be stopped automatically, because there is no trigger for that. Therefore, it is up to you to choose the moment when it should be stopped. Before stopping the monitoring process, you should make sure that all required changes are performed. It means that the installations you have monitored have exited, and all the operations have been fully completed, thus the required files are fully copied, moved, created or deleted, and required registry keys and values are fully saved to the windows registry, etc.
As soon as you stop the monitoring process, the project is created containing the recorded changes. If you are using the Repackage Installation wizard this project is automatically prepared and a deployment package is created. For the manual capturing mode, you should prepare the created project before building a deployment package. See the Projects Preparation section for the information about the required preparation steps.