Client Cache

From: Dave Halperin (davidhalperin_at_hotmail.com)
Date: 04/16/04 

Date: Fri, 16 Apr 2004 15:13:24 -0400

I had a question about the client cache. This is what is in the manual:

Managing the Advanced Client download cache is important if the client
downloads and runs
new advertised programs, but the cache is too full of active downloaded
packages.
When a package is downloaded it is placed in the cache and locked. SMS does
not delete a
package from cache if it is locked. A package is unlocked when either of the
following events
occurs:
u 30 days have passed and the program has not been run
u 24 hours have passed since the program was run
After SMS unlocks the package, it cannot be locked again unless it is
discarded and then
downloaded again.
When a package must be downloaded but the cache cannot accommodate the
package, SMS
checks the other packages in cache to determine whether deleting any or all
of the oldest
packages will free enough space to place the new package into the cache. If
deleting any or all of
the oldest packages does not free enough space, the new package is not
placed into the cache.
This might be the case if there is a package that is currently locked. If
deleting any or all of the
oldest packages does free enough space in the cache, SMS does so, and places
the new package
into the cache.
Users with administrative credentials on the computers they are using can
manage the download
cache. Users can change the size or location of the cache, or delete all
current contents. These
options are in the Temporary Program Download Folder section of the Advanced
tab of the
Systems Management item in Control Panel.

My question:
IF the package is .msi based, is downloaded to the client , run and then
eventually deleted, does this break the self heal feature? Knowing Windows
installer like I do, I am 99% sure it will. IS there any rule that can be
set? Anyone know what happens and if so, where it may be documented?

Thanks
Dave

Relevant Pages

  • Re: Client Cache
    ... the MSI file from the cache and updates the source list. ... > When a package is downloaded it is placed in the cache and locked. ... SMS> does ... > Users with administrative credentials on the computers they are using can> manage the download ...
    (microsoft.public.sms.misc)
  • Re: Client Cache
    ... > I had a question about the client cache. ... > Managing the Advanced Client download cache is important if the client ... > When a package is downloaded it is placed in the cache and locked. ... > After SMS unlocks the package, it cannot be locked again unless it is ...
    (microsoft.public.sms.admin)
  • Re: How to prevent corrupted binary downloads
    ... >> a client machine. ... so my theory was that somehow a corrupt version was downloaded ... >> got in the cache and subsequent requests just reloaded the corrupt data ... We finally solved the problem by giving the download directory ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: software updates and packages
    ... Q1- The clients get the updates from SMS server, ... Q2 - The client keeps a copy of the downloaded files in its cache, ... The cache by default is 250 MB in size. ... download exceeds the total cache size available, ...
    (microsoft.public.sms.swdist)
  • Re: client cache for windows updates
    ... Download & execute is afaik not even supported for patch packages or at ... Normally the client has the logic of only installing the patches it needs ... > can stay up-to-date with updates, I am noticing that the cache will each ...
    (microsoft.public.sms.admin)