Caching packages/installs

[#1]

I have flipped through the manual and I haven't found anything clear on how caching works. Our users move around a lot and may not be connected long enough for some of the packages to be downloaded to their machines. Does the caching feature allow for partial downloads then finish later when it has the chance or does it keep starting from the beginning until it completes the download of the files?

--Grant

[ernstcs]

Hi Grant,

Partial downloads are an option if you have the HTTP option enabled in the
JSS for your distribution point and the link created in the JSS Setup
Utility. There is some info in the 7.31 guide starting on pg 114 regarding
settings for HTTP.

When installers, other than DMGs, get added to the JSS, like PKGs, Casper
Admin should create a Bill of Materials (BOM) file for this to work.

Otherwise it's pretty much how it sounds, if you cache something it places
the package on the client to be used later with another policy typically to
install specific or all cached packages. I can't recall the location of the
cached packages. Page 322 starts the Caching Packages section in the guide.

If your on an older version...it's still similar, at least if you're running
a version where HTTP enabled distribution points were added.

Hope that helps.

Craig E

[#3]

Cached packages are stored in /Library/Application Support/JAMF/Downloads
The Downloads folder will not appear until you select something to be
cached.

We used Caching when we rolled out Office 2008 to our 900 users, then just
used the "install from cache" to trigger the installation. It went very well
and cut down on network traffic.

[#4]

We also used the local cache for CS4 rollout last year.
Just be aware that you don’t run any policies that will also run cached installs.

Funny thing happened to me last year. I had over a hundred users with a cached install of CS4 and we were ramping up towards a "release day".
Then I created a SelfService policy to install all available updates from our SUS…but accidentally also checked the option to install cached installs.

Nick Caro Senior Desktop Support Administrator

[stevewood]

The path is actually: /Library/Application Support/JAMF/Waiting Room

I believe the Downloads folder is for offline policies.

I use caches packages for large CS4 deployments and for deploying the
combo updater for OS X updates, especially to my laptop users. Since I
do those installs on logout, the user doesn't have to wait for the
package to download and then install.

Steve

Sent from my iPhone

[jarednichols]

I don't know offhand, but cached files are stored in /Library/Application
Support/JAMF/Waiting Room.

You could make a policy to cache a large file, execute it, pull the
network, reconnect and let it check in again to see if it picks up or if
it starts over. I would assume that if you're using HTTP transfers that
there's a possibility of resumption. AFP, likely not.

j
-- Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

[jarednichols]

Hahah oh look at that... You guys answered that while I was out last
week... Thanks Outlook beta for not lighting up that thread... :)
-- Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436