SUS via MCX

dpertschi
Valued Contributor

No internal SUS enabled right now, but I'm getting there, I've got nine SUS servers enabled and am now looking at options to define the clients preferred server.

Looking through the archives the three choices seem to be MCX, policy or defined in the Network Segments. I have it configured via the latter but I don't believe it's being set properly across the board.

Anyway, I'm looking now to do this via MCX instead and simply would like to know, when creating the mcx pref. do you specify the value as:

http://server.company.com:8088/index.sucatalog or
http://server.company.com:8088/index-leopard-snowleopard.merged-1.sucatalog

or doesn't it matter (it must right)?

Also, going this route, in the Network Segments should I set Default SUS to None?

Thanks a lot....
Darrin

2 ACCEPTED SOLUTIONS

ToriAnneke
Contributor II

For 10.5
http://your.jss.computer:8088/index.sucatalog

For 10.6
http://your.jss.computer:8088/index-leopard-snowleopard.merged-1.sucatalog

For 10.7
http://your.jss.computer:8088/index-lion-snowleopard-leopard.merged-1.sucatalog

All set to System Level Enforced and I scope them to Smart Groups which sniff out 10.5 or 10.6 or 10.7 machines

works like a charm!

View solution in original post

gregneagle
Valued Contributor

"What OS are the clients? If they are 10.6 & 10.7 then the index.sucatalog URL should suffice."

Sorry to disagree with Ben. The client OS is not important. This is controlled by the software update server. Prior to OS X Server 10.6.7, you needed to use OS-specific URLs. OS X Server 10.6.7, 10.6.8, and Lion Server figure out the OS the client is using and return the appropriate catalog when the client requests index.sucatalog.

Reposado and the NetSUS appliance do not implement this feature; you must point your clients to the OS-specific catalog.

-Greg

View solution in original post

5 REPLIES 5

bentoms
Release Candidate Programs Tester

Hi Darrin,

What OS are the clients? If they are 10.6 & 10.7 then the index.sucatalog URL should suffice.

ToriAnneke
Contributor II

For 10.5
http://your.jss.computer:8088/index.sucatalog

For 10.6
http://your.jss.computer:8088/index-leopard-snowleopard.merged-1.sucatalog

For 10.7
http://your.jss.computer:8088/index-lion-snowleopard-leopard.merged-1.sucatalog

All set to System Level Enforced and I scope them to Smart Groups which sniff out 10.5 or 10.6 or 10.7 machines

works like a charm!

gregneagle
Valued Contributor

"What OS are the clients? If they are 10.6 & 10.7 then the index.sucatalog URL should suffice."

Sorry to disagree with Ben. The client OS is not important. This is controlled by the software update server. Prior to OS X Server 10.6.7, you needed to use OS-specific URLs. OS X Server 10.6.7, 10.6.8, and Lion Server figure out the OS the client is using and return the appropriate catalog when the client requests index.sucatalog.

Reposado and the NetSUS appliance do not implement this feature; you must point your clients to the OS-specific catalog.

-Greg

bentoms
Release Candidate Programs Tester

Yep what Greg said.

dpertschi
Valued Contributor

Thanks Greg, that certainly simplifies, I've also got all three OS to deal with.

Also, when using MCX for this, do I have to set Network Segments Default SUS to None?