Hi, I use "gpedit.msc" to block the IE cleaning options (ctrl+shift+del), for example, I want the users at my home / work do not delete the web history.
I use CCleaner to clean other temporary files, but people are using it to clean everything because they can simply tick the IE history option.
I can tick "read only" in the "ccleaner.ini" (the options file) proprieties but it surely doesn't prevents the users from ticking the IE history checkbox. =/

I'd appreciate if I have the ability to block the option "unticked" in CCleaner options since I don't want to uninstall it. =/

Possible solutions:
1. When installing CC it'd have a CCAdmin.exe that brings the feature I'm requesting.
2. Add a "block settings" button to CC configuration and define a password to unblock it.

I think this feature would be very useful to systems administrators.
Thanks.

I thought something new today. You could give us the option to permanently hide the options we don't want other people to change, this options could be recovered using the password or the admin executable I'm requesting.
I still think the password idea would be better but I had this thought and wanted to share.

1. Download and install Resource Hacker (freeware).
2. Open CCleaner.exe in Resource Hacker and manually edit out the INI settings you don't want.
3. Save CCleaner.exe in Resource Hacker.

Resource Hacker will create a backup copy of the original unedited CCleaner.exe file in CCleaner's install folder in case you wish to go back to it, or you can simply delete it.

Screenshot (click to enlarge):

Thanks for the suggestion, that would be a great solution, but this way I have to do this process on each time CCleaner is updated. :/
I think it's not a big work to do if you think it's one or three computers but imagine if I'm managing 40 or more computers...

@ Andavari. Nice find; haven't seen that before.

@ luik. you would only have to do this once per new version and copy the deployables. Given the specialised functionality that you require that doesn't seen like much of an overhead! You have to redeploy the executable when you intercept a new ccleaner release anyway.

Do your users have administrator rights? If not that gives you other options anyway. If they do, the can manually circumvent any restrictions you put in place if they choose to.

+1


Oh you are right, I don't know what I was thinking!


They do have admin rights but they aren't that much intelligent!
What would be the "other options" if them don't have admin rights?

For example, you may be able to use group policy to restrict ccleaner changes by changing registry key permissions or file permissions so that they can't make changes to settings. I haven't tried this, but it may work depending on how ccleaner operates.

Or you could change the folder permissions so they can't delete the IE history.

Of course ... if you are relying on running on ccleaner to clean files that wouldn't work for you either ... so that would not be a very satisfactory solution.

Also, like it or not, many badly written programs need admin privileges to run properly ... so you might find that doing this would prevent other programs from functioning.

But if the users are not very technical, Andavari's option is probably the better one anyway

If you're the admin making an SFX or script file with the patched CCleaner.exe in it to install over your network shouldn't be too tough I wouldn't think. Then again I'm not doing this on 40+ computers and find just keeping two updated a royal pain in the ...