cleanmgr cleans all drives...

  • Thread starter Thread starter developmental2
  • Start date Start date
D

developmental2

hi,

I tried to set an automated cleanmgr (through shceduler)
but it always insists on doing all drives, even though I specifically
tell it to:
cleanmgr /d c: /sageset:2 (also tried other numbers and caps on the
parameters, no spaces etc)

and then cleanmgr /sagerun:2

My other drives take a long time to clean and I don't want them
done...(the hanging windows confuse the users)
it also does the floppy which is ridiculous.


Thanks
 
hi,

I tried to set an automated cleanmgr (through shceduler)
but it always insists on doing all drives, even though I specifically
tell it to:
cleanmgr /d c: /sageset:2 (also tried other numbers and caps on the
parameters, no spaces etc)

and then cleanmgr /sagerun:2

My other drives take a long time to clean and I don't want them
done...(the hanging windows confuse the users)
it also does the floppy which is ridiculous.


Thanks
Click to expand...

Congratulations on finding the switches in the Microwaffle.

I've not tried it, but my interpretation of the word-torrent hidden in
Q315246 is this:

You can specify /dx (where x is the drive letter. Q315246 suggests that the
syntax should be "/d x:" Q255512 appears to suggest "/dx" [no space, no
colon])
You may specify /sageset:x which stores the drive(s?) specified in the "/d"
option(s?) in the registry. Whether you should use "/dc /dd" or "/dcd" with
or without spaces/colons is carefully avoided.

The documenter also appears to feel that "\sageset" is an option to cleanmgr
(Q315246) and helpfully states "The options for the files that you can
specify for Disk Cleanup by using /sageset and /sagerun include: "(here
follows a list in Q315246) without actually bothering to expose HOW these
options can be specified.

I'd guess that running with the parameters "/dc /sageset:2" SHOULD create a
registry entry (perhaps with CLEANMGR as part of the key) BUT that it'd be
created under the CURRENT USER. Similarly, the "/sagerun:2" should extract
the parameters from the registry - again under the current user.

So it's possible that you're storing the parameters under LOGONUSERNAME and
the scheduler is then not finding the parameters you set because it's logged
in as SCHEDULEUSERNAME - hence it decides to do all drives...

No doubt you want to specify different profiles for different machines,
otherwise "cleanmgr /dx" would seem to be the appropriate choice and you
wouldn't need to use the sageset/sagerun facility.

I'd suggest as a starting point you look into the registry to see whether
cleanmgr is actually creating entries.

HTH

....Bill
 
Back
Top