Software Update Server settings

[brianwells]

I just setup a Software Update service on a Mac OS X 10.5.8 Leopard Server and am trying to determine the best settings to use.

Right now I have the service automatically copy all new updates from Apple, but not automatically enable the copied updates. This is so that we can test the updates before manually enabling them for our production enviroment.

The setting that I am unsure of is “Purge unused/legacy software update packages automatically”. Does this cause all old updates to be deleted even if the newer update has not yet been enabled? For example, suppose Apple were to release a 10.5.9 update. Would the 10.5.8 update presently on server be deleted even though we had not yet enabled the new 10.5.9 update?

I would appreciate any comments from those of you who have worked with Software Update.

Thanks,

– Brian Wells

[brianwells]

Well, I was able to figure this out. It appears that when the Software Update Server gets a new list from Apple, it removes all the old updates from the list of those available to your clients. If the “Purge unused/legacy software update packages automatically” setting is enabled, then it will also delete the old updates off the server.

So when iTunes 9 came out the older iTunes version was no longer available to the computers even though I had not yet enabled the newer iTunes. Not the best way for it to work, but at least I know about it.

— Brian Wells

[brianwells]

I just looked at the [i]System Imaging & Software Update Administration[/i] manual for Snow Leopard Server.

[url]http://manuals.info.apple.com/en_US/SystemImage_v10.6.pdf[/url]

It appears that there is new functionality for offering older (deprecated) versions of software updates. I’ll see if I can update one of our Xserves and try out the new Software Update Server in the next week or so. 🙂

– Brian Wells

[Author]

Posts