How does cpm go about monitoring installs

does CPM

A: detect an installer and then track all the files that the installer puts on the users pc and all the files that may spawn from the files that the installer puts on the users pc.

for example: installer is detected and cpm monitors the installer putting files a,b and c on the users pc and the installer is done but files a,b and add files d,e and f and cpm monitors what files a,b and c created as well.

B: monitor only files that the installer puts on users pc

C: detects an installer and monitors everything being put on the users computer during the install and if the user is creating new files or folders then this will also be considered by cpm as files and folders related to the program the user is installing which would cause files and folders unrelated to the program to be removed if the user decides to uninstall that program

D: none of the above. Please explain how it works and how it avoids removing unrelated files, folders, reg keys and values and drivers if it can avoid removing stuff unrelated to the program that the user wants to uninstall

The monitoring concept behind CPM corresponds to the variant ‘A’.
Thank you.

I’d like to see CPM have the option to continue monitoring an install beyond the initial installation phase - i.e. up to the initial launch of the installed app and also including any subsequent configuration of the app. By this I mean the following;

  1. User starts an install which is monitored by CPM
  2. User completes installation
  3. CPM prompts whether to end monitoring
  4. User answers NO and launches newly installed app which is still being monitored.
  5. User configures application to suit
  6. User tells CPM to complete monitoring (or CPM continues to prompt at regular intervals)

This way, when the user makes an installer packer from the resulting monitored installation, the package would contain a standardised set of configurations. This may prove handy when used in conjuction with CESM for pushing standardised installs across a LAN.

What think?
Ewen :slight_smile:

I liked Panic’s suggestions.
Anyway, my experience with CleanSweep from Norton (years and years ago) is that the “monitoring” includes a lot of other files/registry keys being changed in background by other opened applications.
The final “cleaning” needed to be manual and very careful or you deleted what you shouldn’t.

I’ve tried doing these:

  1. install an editor
  2. created sample1.txt file using the editor
  3. restart the windows
  4. created sample2.txt file using the editor
  5. uninstall the editor

In the text file i’ve created only sample1.txt is included in the uninstall process sample2.txt file is excluded.

Does it monitors the program after reboot? If so, why does sample2.txt is excluded? But for me, it’s good to be excluded cause these files are created by user. I’m just wondering how monitoring works.

The programs are monitored until the first reboot in order to keep the monitored user created information at minimum, although there are some files excluded in any circumstance ( music, video and pictures). The editors’ files will be added also.
Thank you.

Thanks, when in comes to application update such as firefox, how do they works? I had updated my firefox and find out that the new version had been monitored but the old version still in the list which is partially uninstalled application which mean that it creates a new monitored application.

Does the new monitored firefox updated the list of monitored files from the old version or just monitored the updated files?

Seems useful so stickied

Best wishes