Most packager rely on making a snapshot of the entire system before installing a new application then comparing that to another complete snapshot after the application is installed to determine all the changes the application needs to be installed. There are a couple downsides to this approach:
- The process of taking the before and after snapshot can be very time consuming especially if the system has many applications installed.
- The snapshot comparison looks at all changes made to the system, even those made externally to the application installation. This forces the administrator to become intimately familiar with the application to determine what folders or registry keys need to be excluded from the package.
- Since the snapshot process requires access to all areas of the file system the administrator needs to add more excludes to the install job to get the snapshot to work properly.
Our packager relies on monitoring the application installation at the kernel level to see what file and registry changes are made during the installation of the application. This approach greatly improves the accuracy of the changes made and improves the time to capture the installation since we don’t need to perform full snapshots before and after the installation. Administrators can then modify the package in the package editor.
Package File System