Skip to main content
Question

10.5.5 SUS hitting a brick wall

  • October 24, 2008
  • 4 replies
  • 42 views
M
Forum|alt.badge.img+23

Hey all,
Sorry if this is slightly off-topic, but is anyone having difficulties with
Software Update Server under 10.5.5?

I the service is running, I can ping the SUS, the index.sucatalog file is in
the /usr/share/swupd/html/ directory, and the permissions are lrwxr-xr-x. As far as I can tell this should be working, but when I try to update a
client, I get "Operation could not be completed. (NSURLErrorDomain error
-1100.)"

Has anyone with a successful 10.5.5 SUS had to do anything beyond Apple's
documentation to get it to work? I'm passing the SUS setting through
Casper. I've tried both the DNS name and IP in the SUS record in the JSS.

Thanks,
Miles

    4 replies

    Eyoung
    Forum|alt.badge.img+10
    • Eyoung
    • Contributor
    • October 24, 2008

    I was seeing that error as well. Trying to run software update from casper, ARD or any remote command got that error immediately.

    I found the issue was managing the software update server in the WGM setting for the machine... Once turned off managing the updates the error went away.

    Eric Young
    eyoung at thayer.org
    781-664-2286

    M
    Forum|alt.badge.img+23
    • milesleacy
    • Author
    • Valued Contributor
    • October 24, 2008

    Thank you for that. I deleted the client from WGM, deleted the managed
    prefs, and rebooted. Then I made sure my "enforce management framework"
    policy ran. After that, I ran "softwareupdate -l", and I no longer get the
    error. Unfortunately, it seems that my client is looking to Apple instead
    of my internal SUS as specified in the JSS.
    Any ideas as to what could be causing this? It appears that the client
    isn't taking the setting from the JSS. Can anyone refresh my memory - does
    the JSS write to com.apple.SoftwareUpdate.plist, or does it use some other
    mechanism?

    There is a /Library/Preferences/com.apple.SoftwareUpdate.plist file, but it
    does not contain an UpdateURL key. There is no
    ~/Library/Preferences/com.apple.SoftwareUpdate.plist file.

    And just to rule out the "did you plug it in" level of troubleshooting - I
    am remembering correctly that the "enforce management framework" policy will
    configure the client's SUS setting as specified in the JSS, aren't I?

    Eyoung
    Forum|alt.badge.img+10
    • Eyoung
    • Contributor
    • October 24, 2008

    I've hardcoded the internal server to the OS package. Then for a belt and suspenders apprach I also have it in the framework policy and make sure I enable the Set Server button for the software update policy I run.

    ~~~~~~~~~~
    A cynic is a man who, when he smells flowers, looks around for a coffin. --H. L. Mencken

    Eric Young
    eyoung at thayer.org

    M
    Forum|alt.badge.img+23
    • milesleacy
    • Author
    • Valued Contributor
    • October 24, 2008

    This is resolved.

    In case anyone was interested, the issue was twofold:
    1. I *was* incorrect. Enforce management framework will not set the SUS. The "Set Server" checkbox in the Software Update section of the software
    tab does that.

    1. After creating a policy to do the above, I tried to test it by issuing the following command at the client: sudo jamf manage -action every15 This will trigger the policy, but the random interval will apply. To trigger a policy instantly, the policy verb is used instead of the manage verb.

    I figured out #1 on my own. Support gave me #2. Support is awesome, call
    them when you're stuck. I'm sorry I don't remember his name, but during my
    call, the random interval occurred, and the policy ran, so I told him I was
    happy and to consider my issue resolved. He called back a few minutes later
    to explain why it took a few minutes for the policy to run and how to
    trigger it instantly in the future, which is great seeing as it's been a few
    months since I've actively managed a JSS and my jamf-binary-fu is weak. So
    thanks again, mystery support man!

    Terms & ConditionsCookie settingsAccessibility statement