36552 Views Previous 1 2 3 Next 36 Replies Latest reply: Aug 10, 2010 6:21 AM by UKenGB Go to original post
i've just tried this on a dev server and it works like a charm so far. snow leopard files ARE being hosted by the server and ARE downloading properly to snow leopard clients after making a change to the softwareupdate.plist
yet to check: whether 10.4 and 10.5 clients are still working as they should.
we updated two 10.5.8 servers to supply 10.6 updates some time ago as per the above and all has been well... until recently.
Neither SUS is now supplying 10.6.x updates post 10.6.2. Both SUS working fine for everything else so we were hoping to find others with the same problem. Anyone suffering? Anyone fixed it?
a question in reference to your reply about the redirect (knowing fully that i might seem like the biggest ignorant):
what does it mean to "add a redirect in my webserver"? And how do i do it? because i think your reply may be the solution to my problem…
+-- the thing is i followed to the letter Jan's instructions but i'm having trouble with all the 10.6 clients (all pushed through the Workgroup manager to index-leopard-snowleopard...). All the 10.6 clients' SU are giving the error of server not responding.+
Here's the solution I found for updating past 10.6.2, thanks to the information in these two posts:
On my Snow clients, I run this command as root:
defaults write /Library/Preferences/com.apple.SoftwareUpdate CatalogURL "http://my-SUS_server-FQDN.com:8088/index-leopard-snowleopard.merged-1.sucatalo g"
And now, my Snow clients see their correct updates from my Leopard server.
I found a method that is working on our network environment (SUS + OD server 10.5.8, client 10.5.8 AND 10.6).
Here's what we did:
1. Stop SUS (serveradmin stop swupdate)
2. On SUS server, create meta folder in /usr/share/swupd/html/content/
3. Download file http://swscan.apple.com/content/meta/mirror-config-1.plist and copy to /usr/share/swupd/html/content/meta
4. Edit it, and make it like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
5. Start SUS (serveradmin start swupdate) and wait until the following catalog files in /usr/share/swupd/html/content/catalogs/others are generated:
-rw-r--r-- 1 root wheel 1278985 Jul 29 13:50 index-leopard-snowleopard.merged-1.sucatalog
-rw-r--r-- 1 root wheel 928903 Jul 29 13:50 index-leopard.merged-1.sucatalog
6. Create the following symbolic links in the html folder:
ln -s /usr/share/swupd/html/content/catalogs/index.sucatalog
ln -s /usr/share/swupd/html/content/catalogs/others/index-leopard.merged-1.sucatalog
ln -s /usr/share/swupd/html/content/catalogs/others/index-leopard-snowleopard.merged- 1.sucatalog
7. Wait until SUS server download 10.6.x updates
At this time SUS server is ready.
Now you have to tell to the clients how to use it correctly.
You must manage OS X 10.5.x clients differently from OS X 10.6.x clients.
8. On the OD master server, with Workgroup Manager, create two Groups, i.e.:
9. Configure the Login ==> SoftwareUpdate preference string accordingly:
10. Insert in the first Group only clients with OS X 10.5.x,
Insert in the first Group only clients with OS X 10.6.x
11. Logoff and login on the clients in order to activate the OD policy.
That's it: SoftwareUpdate will find updates for the correct OS version
Message was edited by: montinlo
Message was edited by: montinlo
I can see how this solution should work, but I am wondering why the mirror-config-1.plist file is downloaded and modified and used locally rather than simply modifying /etc/swupd/swupd.plist as follows:-
as it is for Snow Leopard Server?
It occurs to me that Leopard's Software Update Server doesn't understand <key>otherCatalogs</key> so this method wouldn't work. Can anyone confirm this?