locked
Application cache not purging when pushed via OSD TS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I push out between 25 and 30 applications during my OSD TS and am finding that the application install files are sticking around in cache and not deleting when the cache is full causing the TS to fail (packages delete just fine). I've double checked all the applications and made sure that "Persist in cache" and "Branch sharing" checkboxes are unchecked. I've had to work around this by bumping up the cache space but that's not really the point. If the files aren't supposed to persist in the cache then they shouldn't. It's been a week since I last tested and the files are still in the cache. This happened pre-SP1 and continues post-SP1. Has anyone else run into this and, if so, have any ideas where I can look next?
    Tuesday, February 5, 2013 6:57 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    The Client cache will only delete a package/application 24 hours after it was last used even if the disk space is needed. From TechNet, I assume this is the reason of the disk filling up.

    From TechNet:

    Cached content is not automatically deleted but remains in the cache for at least one day after the client used that content. If you configure the package properties with the option to persist content in the client cache, the client does not automatically delete the package content from the cache. If the client cache space is used by packages that have been downloaded within the last 24 hours and the client must download new packages, you can either increase the client cache size or choose the delete option to delete persisted cache content.

    http://technet.microsoft.com/en-us/library/gg712288.aspx

    The behaviour was the same in SCCM 2007 if I am not mistaken.

    Regards,
    Jörgen

    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Marked as answer by Mike Horton Tuesday, February 5, 2013 10:10 PM
    Tuesday, February 5, 2013 7:39 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mike,

    do you mean something like this? http://innovation.connect.microsoft.com/configmgrsp1openbeta/Thread/View.aspx?ThreadId=8781

    At the end of the day we gave the VM on which we captured the Image a larger HDD.

    David O'Brien | MCITP/MCSE/MCSA, CCEE/CCIA | My blog: www.david-obrien.net | me on Twitter: @david_obrien | sepago GmbH

    Tuesday, February 5, 2013 7:24 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi,

    The Client cache will only delete a package/application 24 hours after it was last used even if the disk space is needed. From TechNet, I assume this is the reason of the disk filling up.

    From TechNet:

    Cached content is not automatically deleted but remains in the cache for at least one day after the client used that content. If you configure the package properties with the option to persist content in the client cache, the client does not automatically delete the package content from the cache. If the client cache space is used by packages that have been downloaded within the last 24 hours and the client must download new packages, you can either increase the client cache size or choose the delete option to delete persisted cache content.

    http://technet.microsoft.com/en-us/library/gg712288.aspx

    The behaviour was the same in SCCM 2007 if I am not mistaken.

    Regards,
    Jörgen

    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Marked as answer by Mike Horton Tuesday, February 5, 2013 10:10 PM
    Tuesday, February 5, 2013 7:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't have access to that thread David so I can't see exactly what it says. In our case drive space isn't a problem but it's the theory of the thing. Applications shouldn't be sticking in the cache.
    Tuesday, February 5, 2013 8:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Jögen, I'm only seeing it with Applications. The few packages that I push down are getting deleted. I've also left the application cache alone for a week and it's still there. Something that I'm not seeing with 2007 (we're still using 2007 in production) so it must be something they've changed 2012 as my OSD TS is the same for 2012 as it was for 2007 except that I've moved what I could from Packages to Applications. In 2007 our cache space is set to 5GB and is also the same for 2012. I never had a problem running out of cache space pushing the same programs down as part of the OSD in 2007 but in 2012 I've had to boost the cache to 10GB for the OSD to complete without failing. If I check a system that was deployed from 2007 the cache is empty after an OSD. My concern is that eventually we'll run into a situation where we can't push down files because the cache is filled but I'd never heard about the 24hr rule before (or if I did I'd forgotten it). 

    I'll see if I can push some more applications at it to fill the current cache to verify that files are indeed getting deleted.

    EDIT: Just pushed out another 5 GB of files and the cache did delete.
    • Edited by Mike Horton Tuesday, February 5, 2013 10:11 PM
    Tuesday, February 5, 2013 8:42 PM