We have thought about that approach before, but we did not end up adopting it because the mere act of placing ThinApp Capture on a shared access is that the capture progress will invariably capture some temporary files and registry settings related to the shared access (to ThinApp Capture) that we do not to capture. In our experience, during the capturing progress, we could not exclude the fact that the aforementioned files or settings.may change, so that they will not be removed when comparing the baseline to post-capture snapshots. The only sure way is to run the ThinApp Capture as a "portable" app from a single directory which we can delete entirely from the snapshot capture.
↧