Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 9802 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Testing Macs not updating from 9.1.8 to 9.2.2

AaronMelgares

We have a testing group to test the preview versions of the Sophos client.

Our process has been to move computers from a standard group into the testing group which has an update policy using a preview subscription.  This way we can use a small number of computers to try out the preview versions of the Sophos client.  It's worked well for the last year, but now I'm having a problem.

Macs running Sophos 9.1.8 that are moved into the testing group are not updating to 9.2.2 even when they report they are compliant with the test Updating policy and are "Up to date" in the Update Details tab of the console.  The AutoUpdate log on the clients say they have updated successfully.  The detection data ad IDEs match the 9.2.2 clients so they seem to be getting detection data updates, just not updating to 9.2.2.

I'm going to create a new test group and new test CID, but it seems odd that this worked before and doesn't work now.  The Macs are running 10.7.5, 10.9.5, and mostly 10.10.1. 

Any thoughts?

Aaron

:55405


This thread was automatically locked due to age.
  • 0

    Hello Aaron,

    just tried it and all the Macs (10.7.5, 10.8.5, 10.9.4, 10.9.5, 10.10.1) did upgrade to v9.2.2 (well, some didn't - turned out I hadn't applied the correct updating policy to their group :smileywink:). BTW - Data (and therefore IDEs - 5.09 with 403 right now) are the same for 9.1.8 and 9.2.2.

    Christian

    :55410
  • 0

    We figured this out today.

    The Mac 9.2.2 clients includes these files without extensions:

    ESCOSX/Sophos Installer Components/savi.bundle/Contents/_CodeSignature/CodeDirectory

    ESCOSX/Sophos Installer Components/savi.bundle/Contents/_CodeSignature/CodeRequirements

    ESCOSX/Sophos Installer Components/savi.bundle/Contents/_CodeSignature/CodeResources

    ESCOSX/Sophos Installer Components/savi.bundle/Contents/_CodeSignature/CodeSignature

    The Mac 9.1.8 clients also include these files without extensions:

    ESCOSX/Sophos Anti-Virus.mpkg/Contents/_CodeSignature/CodeDirectory

    ESCOSX/Sophos Anti-Virus.mpkg/Contents/_CodeSignature/CodeRequirements

    ESCOSX/Sophos Anti-Virus.mpkg/Contents/_CodeSignature/CodeResources

    ESCOSX/Sophos Anti-Virus.mpkg/Contents/_CodeSignature/CodeSignature

    We recently upgraded our server from IIS 7 to 7.5 and the 7.5 web server was not configured to serve these files.  We added this to the MIME type config:

    File extension type: .

    MIME type: application/octet-stream

    And the files now download and our Macs are updating from 9.1.8 to 9.2.2.

    Apparently the previous .* setting worked to allow files without extensions in 7 but didn't work with 7.5.

    This was stopping updates for all the Mac clients, but since most of our Macs were already at 9.1.8, they didn't see this issue.

    Thanks for the confirmation that it worked for you Christian, it led us to investigate the web server itself. :smileyhappy:

    - Aaron

    :55418
  • 0

    Hello Aaron,

    you have probably changed the update location (CID) in the policy - do you observe that (at least some of) the Macs revert to their initial update location?

    Christian

    :55443
  • 0

    Actually, yes - I'm seeing about 10% of the Macs in my testing group revert back to the original update CID even after I send a "comply with updating policy" command to point to the preview CID.  I'll post anything I find out in the thread you referenced.

    Aaron

    :55452