Hi!
I've read this thread and now I have some questions.
I want to use this on multiple computers and with both limited users and administrators. The set-up I had in mind is this:
- Every day the limited user cleans out his bin and temporary internet explorer files
- Every week the administrator cleans out the Windows temp. folders and the folders that a limited user can't access because of it's limited rights
What I understand is that the /auto command performs the cleanup that has been set for that user. So if I use Windows scheduler and I let it run using a local user, it cleans out X and Y and when it executes using an admin account it cleans out X Y Z.
The problem is that it costs time to configure these settings for all users on all PC's. What I want to know is where these settings are being stored so I can just copy/paste them using a regedit or filecopy.
Please let me know.
I'm going to bump this post one more time ![:)]()
.
I would like to know where the settings are being stored so I can give people better support, using a pre-made configuration.
By default, they are stored for each user under HKEY_CURRENT_USER\Software\VB and VBA Program Settings\CCleaner\Options except for the automatic update check which is a system-wide option (applies to all users) and is located under HKEY_LOCAL_MACHINE\SOFTWARE\CCleaner.
However, rather than plug the registry of your users, a better approach for "pushing" CCleaner, is to use the option for storing settings in an INI file. It would be named CCleaner.ini and placed in the same path as CCleaner.exe. And the easiest way to configure INI mode is to create a file named portable.dat in the same path, which forces CCleaner to operate in "portable" mode. Although portable mode is intended for use with USB flash drives, it doesn't do anything more than force CCleaner.exe to ignore the registry in favor of the INI file.
You can download the portable build of CCleaner by clicking on the "Other builds" link near the bottom of the download page, but there is absolutely no difference in the software between the builds; it's merely a packaging difference. The portable build is zipped (no installer) and comes with a pre-made portable.dat (which you could easily make yourself with Notepad).
Wow!
This is even more information then I've asked for but it's perfect!
hosebeast , thank you!
I'm going to try the mobile version and let you know if it works for me. (or if it doesn't ![;)]()
)