«

Software Update Enabler 2.0

Just released Software Update Enabler 2.0 now with Snow Leopard support, a simplified UI and the ability for non-administrators to authenticate to set the update server.

If you’re using Snow Leopard or a Snow Leopard Software Update server you really want to grab it now!

This entry was posted on Thursday, September 3rd, 2009 at 1:32 pm and is filed under Mac. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

7 Responses to “Software Update Enabler 2.0”

  1. James Says:
    September 3rd, 2009 at 3:47 pm

    Does the server also have to be running Snow Leopard if the client is?

    (I’m stuck on ‘Verifying Server…” and spinning worm wheel thing).

  2. proton Says:
    September 3rd, 2009 at 3:53 pm

    Yes, the server should be running Snow Leopard in order to receive any Snow Leopard Specific updates.

    Being stuck at the “verifying server” stage probably indicates a firewall issue being unable to connect to the server while it waits for NSURLRequest to timeout. There should be a timeout of 5 seconds per request, but we try port 8088 and 80 for each of a number of different catalogs per OS release.

  3. ptitpiffuté Says:
    September 4th, 2009 at 12:12 pm

    I’ve the same issue as James has described, exept that I’m running SL Server and client. I’ve checked on the firewall side, nothing is setup, I’ve Littlesnitch, but it doesn’t seem to be blocking anything.

    So what is going on then …..

    Cheers

    PS : nice work for this app

  4. Tom Says:
    September 9th, 2009 at 12:29 pm

    Love you software!!

    when I run the app on MacBook Pro I get a box that says My Software is Up To Date, but under that window is another window that can not be clicked on that says Show Details, Not Now and Install.

    I am running Snow Leopard on the MacBook Pro and Snow Leopard Server.

  5. Robb Allan Says:
    September 12th, 2009 at 3:11 pm

    Here’s a problem with 2.0 (from the SL swupd_error_log on the server):

    “Symbolic link not allowed or link target not accessible: /var/db/swupd/html/index-leopard-snowleopard.merged-1.sucatalog”

  6. Ivan Mykytyn Says:
    September 29th, 2009 at 11:14 pm

    Great piece of software.

    To anyone stuck at “verifying” or finding “Symbolic link not allowed or link target not accessible: /var/db/swupd/html/index-leopard-snowleopard.merged-1.sucatalog” in their server log.

    Your update server has probably not finished downloading updates. It will not start responding till it has done that – which takes a day or so depending on the speed of your connection. Be patient. If you do see the above message in your log it most likely means your request is getting to the server (look at the source IP), but the server is saying – go away, I am not ready yet.

    Overall the process is:
    1 Enable software update server in server admin.
    2 In the software update settings tab – typically – tick the boxes for
    Enable all new updates from Apple
    Automatically enable copied updates
    Delete outdated software updates
    3 Start the server
    4 Wait till the update server has completed downloading the available updates. You can check progress under the updates and info tabs. My current updates folder sits at about 17gb, so expact to wait for a day or so.
    5 When downloading is complete you should be able to connect to your server at http://YourServerName.WhateverExtension:8088/ (just like in the example.

    Not everyone is an IT specialist, with many people setting up a server for home or small office use. One thing they often miss is that you can connect to your server at:
    Its local address – for example if your server is called “myserver” then connect to http://myserver.local:8088/ If you are not sure what your server’s local name is you will see it at the top of the Overview tab in server admin.
    It’s IP number – for example if your server’s IP is 10.0.0.10 then connect to http://10.0.0.10:8088/

    Once again thanks for a great piece of software – it lets anyone carry out the task without recourse to the terminal.

  7. Kieren Says:
    October 26th, 2009 at 1:32 pm

    Another Note for those who are stuck with the verifying server error…..

    It seems that my Uni has not yet updated their SWupdate server from Leopard to Snow Leopard yet.
    As I am now on SL and trying to get SUE to work. There is a fault in that if the .sucatalog cannot be found on the server for the CLIENTS OS then the message is not updated on the UI – hence the look of a hang.

    As a test I added the index.sucatalog to the 10.6 catalog plist and it found the server and the catalog file straight away.
    NOTE : THIS is not a fix as I pointed 10.6 at a 10.5 SWupdate server and so no updates were available, it was just an excercise in finding out what the hang in the UI was caused by.

    Hope this Helps Andrew fix this minor annoyance to some.

    Thanks to Andrew For all his hard work on making many of our lives simpler ;)

    Kieren

Leave a Reply