Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Update the Software Update Server without re-downloading OS X Server
I had the need to update a server that was acting as a Software Update Server. I knew that the machine had the update on it, but was unsure of how to get it to see the locally-hosted update. If you open Terminal and issue this command...
open /usr/share/swupd/html/index.sucatalog
...then Software Update will launch, looking at the localhost -- no need to re-download the update from Apple.
    •    
  • Currently 2.07 / 5
  You rated: 5 / 5 (14 votes cast)
 
[5,621 views]  

Update the Software Update Server without re-downloading | 3 comments | Create New Account
Click here to return to the 'Update the Software Update Server without re-downloading' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Update the Software Update Server without re-downloading
Authored by: kiltbear on Oct 20, '09 07:52:13AM

I set my update server to look to itself the same way I set up the clients. Things seem to work well this way.



[ Reply to This | # ]
Update the Software Update Server without re-downloading
Authored by: chrisfriend on Oct 20, '09 08:02:19AM

I do the same as kiltbear. It seems silly to point the machine acting as SUS to itself, but it works great. That setting doesn't influence where the SUS process goes for updates, only where the user-facing Software Update process looks.

I'd recommend using Software Update Enabler if you're just changing the settings on a small number of machines. It works smoothly with SL now, too.

http://www.allocinit.net/apps/suenabler/



[ Reply to This | # ]
Update the Software Update Server without re-downloading
Authored by: ehemmete on Oct 20, '09 08:13:30AM
You can also point your server back to itself via the command line. No third party GUI necessary.
defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL http://my.server.com:8088/

Replace my.server.com with your servers hostname or IP. Don't forget the port number (normally 8088) and the trailing /.

[ Reply to This | # ]