Skip to main content

Hello,



I have been crafting an Apple Software Update policy this week and have run into a few issues. I am running a reposado master with cascaded slaves for remote sites. I have set the update servers in the JSS for the various network segments.



I have two policies so far and a smart-group that searches for machines with more than 0 updates available. The first policy just notifies the user that they have updates available and to launch Software Update through Self-Service. The second is the Self-Service policy that is set under packages to "Set Server" and "Install all Software Updates".



The first policy works just fine and notifies the user. The second policy works, however it still pulls the updates from Apple rather than one of my reposado servers. I also noticed that it doesn't modify /Library/Preferences/com.apple/SoftwareUpdate.plist. Should it update this for you, or does it use another method?



I will open a ticket with JAMF, but was wondering if this works for anyone else... and if you have any tips to streamline this process more for the end-user.



Thanks,
Ken

Thanks to Eric L. from Jamf, we are closer to getting this to work. I hadn't set the update servers to "Set System Wide".



However my new problem is how reposado writes it's url's... the standard url for softwareupdate should look like:
http://server1.domain.com:8080/index-leopard-snowleopard.merged-1.sucatalog



But in reposado it looks like:
http://server1.domain.com:8080/content/catalogs/others/index-leopard-snowleopard.merged-1.sucatalog



Time to play with apache and try to setup some redirects it seems.

Jamf recommended using mcx to push the CatalogURL to the clients because of the url difference. I found if I added redirects in Apache, everything works like a charm.

Terms & ConditionsCookie settings