Content Cache Setup Issues

[sgiesbrecht]

Hello everyone

Having issues with Content Caching for the past few weeks and driving me crazy.

We have a M2 Mac mini with the IP address 10.10.10.10 ( not real IP ).
The end-points are on the same network.

I've created a Configuration Profile for the Cache System and the end-points with the following
Configuration Profile Settings.

I have read https://support.apple.com/en-ca/guide/deployment/depde72e125f/web and https://support.apple.com/en-ca/guide/mac-help/mchl3b6c3720/mac and I can't seem to get it working

Do I need a DNS TXT record? I didn't put one in since I set the My Local Networks to use one public IP address

What am I doing wrong?

Here is my Configurations settings

[atomczynski · Accepted solution]

Hello,

Here are some links to read over:

https://support.apple.com/guide/deployment/intro-to-content-caching-depde72e125f/web

https://support.apple.com/guide/mac-help/set-up-content-caching-on-mac-mchl3b6c3720/mac

https://support.apple.com/guide/deployment/advanced-content-caching-settings-depc8f669b20/1/web/1.0


Few things to point out.
If you have a single WAN / external IP you do not need a DNS TXT entry.
The parent IP is if utilized if you have multiple cache servers and you want one of them to host the updates and other content for others to download from. This is something that is utilized in larger deployments.

I suggest, set this up first "manually" on the client without the Jamf Cache configuration profile. Confirm this is working, and after that reapply/transfer your settings to a profile.

Also take a look at the following:
https://marketplace.jamf.com/details/jamf-environment-test
https://support.apple.com/en-us/HT210060

[user-dIrrpGXxza]

I think your problem is that you're trying to do this via MDM. Just enable content caching on the content cache server with the default options (both server and clients share the same IP address if I understand what you wrote above correctly) directly from macOS without the use of JAMF. Clients don't need any configuration at all, they will discover the cache automatically. If it still doesn't work, check status of the cache (perhaps your server has a different external IP than the clients?), and check the logs. AssetCache has a pretty extensive logging capability that is pretty clear if something is broken.

You can also verify manually from a macOS client that your cache is indeed working from the client by using the utility AssetCacheLocatorUtil.

[sgiesbrecht]

I guess I'd over thought this and screwed it up.

it's is working tmk.

now writing a script to verify if the workstations are using the cache system

than you both for your assistance

[atomczynski]

You can use this for an extension attribute in Jamf Pro.

#Jamf Pro Extension Attribute used to return the active Caching Server(s) found by a Mac
#Note that the return is either a multi-line output of IPs or null if none are found
#Note - each server is listed once whether it caches iCloud data or just shared assets
#
#
result=`/usr/bin/AssetCacheLocatorUtil 2>&1 | grep guid | awk '{print$4}' | sed 's/^\(.*\):.*$/\1/' | sort | uniq`
echo "<result>$result</result>"

[sgiesbrecht]

@atomczynski 

I ran the command "/usr/bin/AssetCacheLocatorUtil 2>&1"  on the in Terminal to check and notice that my cache system has "rank 1, not favored, healthy".  how can I make it favored?

all others ( workstations ) are marked as unhealthy ( which is ok ) which is not an issue