3 Replies Latest reply on Apr 30, 2009 11:58 AM by mrspike

    SDMCACHE (Discard Period) Reg Key


      I modified the discard period reg key on a machine to 0x0000012c (300) which is hex for 300 seconds or 5 minutes.  This was only for testing purposes, to see if the package I had distributed and was in sdmcache would clear out.  It didn't.  Even after a reboot and manually restarting the TMC service as well.  Is this value to low for testing or is something else wrong here.  I used a batch file which runs a .reg file to modify this setting.  Attached are the files which I originally received from landesk support but the .reg file originally was setup for 30 days.

        • 1. Re: SDMCACHE (Discard Period) Reg Key
          mrspike SSMMVPGroup

          was the file distributed prior to your change or after?


          I have found that if the change is made after, it does not go back and clear out old files.  I believe as each file is cached it is time stamped at that point and will die when it expires.



          • 2. Re: SDMCACHE (Discard Period) Reg Key

            Now that I think of it, it may have been after.  What I did is setup a distribution package setting the main file as the batch file, with the .reg key and office 2003 files as "additional" files.  What originally happened is the Office files and batch file copied over to cache, but the .reg key didn't make it so the batch file failed and the registry never updated.  I reset the hash on the .reg key, ran the task again and it succeeded in changing the registry, but to answer your question I guess technically the files were already there before the registry change.  Do you suggest I just manually delete all files out of cache, set the registry back to the way it was, reboot and rerun the whole task again?

            • 3. Re: SDMCACHE (Discard Period) Reg Key
              mrspike SSMMVPGroup

              If this on one machine, or just a few, manually deleting it would be the easiest.


              If have a lot of room on the hard drive, you could just wait for it to expire normally.


              If you have a lot of machines with it and you need the to free up space, you could send a script to delete them, otherwise again, you can just wait the two or 14 days it takes to expire.



              BUT.... If you want to the same files to be on the system for a deployment, you can just rerun your task and those that are there will just be checked to ensure the hashes match and anything new or different will be downloaded as needed.



              Not exactly sure what you are doing, so that it why I offered so many choices.