|
#9
| ||||
| ||||
| Just to state the obvious: 10.4.11 is available.
__________________ MacBook Air 13" 1.6 GHz, 2 GB RAM, 80 GB HD. Mac OS X 10.5.5 MacBook 13" 1.83 GHz, 2 GB RAM, 160 GB HD. Mac OS X 10.5.5 Hackintosh Core2Duo 2.4 GHz, 2 GB RAM, 160 GB HD. Mac OS X 10.5.5 iPhone 3G 16 GB (v2.1), AppleTV 1G 40 GB (v2.1) Mac user since 1987, Apple Product Professional 2007, 2008. |
|
#10
| |||
| |||
| Yup, doesn't help ![]() |
|
#11
| |||
| |||
| Restart the server or have it reload the updates. Does any system sees the updates or absolute none. In the latter case the sus is not working oke. At least a restart will be required. Also check which updates are loaded and if any update mentioned on the apple update server is loaded on your server. Good luck, kees |
|
#12
| |||
| |||
| getting Tiger software update server going We had this problem because the server was not done downloading all the updates which took it about 8 hours on a T1. Also, there's a change we did to the software update preference file on the client side to include the host.company.dom:PORT and for PORT we used 8088 and made sure the 8088 entry was listed on the server settings. examples: 192.168.1.100:8088 server.company.com:8088 After a server reboot, it began working. You can grab a utility that will permit you to set the software update server plist on the client side using the example above. Hit your favorite mac software download site and search for "software update server" here's a link to one at SOFTPEDIA.COM named Set Software Update Server http://mac.softpedia.com/progDownloa...oad-23966.html I also read somewhere to be sure you have your DNS server setup correctly for reverse of the softwareupdate server, but I would think using the IP address would get around that. Last edited by itsasony; November 16th, 2007 at 10:53 AM. Reason: title change |
|
#13
| |||
| |||
| It's working now :-D I think it downloading was part of the problem, but I also found that when the proxy settings are set on the clients, they can't see any available updates, even when I tell them to bypass the proxy for that specific address. So the server's working properly now, just the clients are misbehaving. Thanks for all the help. |