|
|
Create a transparent local software update server
Setting up a local software update server for Macs is a great idea and well worth it. I have a slightly different (and I think simpler) method, though YMMV.
Create a transparent local software update server
I like the original idea a lot better - try your model in an organization with thousand of clients…
Create a transparent local software update server
I appreciate all your comments, although I must say only few people understand my solution so I will emphasise what matters this time again: This doesn't require any modifications on clients. Most of the solutions suggested were already described in many places, for example here at macosxhints: 10.4: Manually add a Tiger Software Update Server I agree that using e.g.
Yes, this is actually a DNS hack, but what I like is that the setup is very simple. Just the server, one
Brilliant!... 10.6 Server update:
OK, I have this up and running on 10.6.1 server now...
Brilliant!... 10.6 Server update:
Truly a great hack, thanks for that. Thought I would add that I have it up and running on Server 10.5.8, and it's happily serving updates to clients using 10.4, 10.5 and 10.6 (haven't tested older ones).
Brilliant!... 10.6 Server update:
Alright, I now also have 10.5.8 Server sending out updates to Lion clients!
Added: http://swscan.apple.com/content/catalogs/others/index-leopard-snowleopard.merged-1.sucatalogto mirror-config-1.plist Left it for 24 hours to download updates and propagate the catalogs, then redirected index-lion-snowleopard-leopard.merged-1.sucatalogto /usr/share/swupd/html/content/catalogs/others/index-lion-snowleopard-leopard.merged-1.sucatalog.appleThanks again to the original poster for the great tip! |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|