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

UNIX updating

Hi,

We have installed Sophos Antivirus (version 9.15.1 VE3.74.2) on UNIX SP AIX1.

Computers are visible and managed via Enterprise console 5.5.1

Issue was that computers were not updating. Update manager is configured and working on LINUX a WINDOWS servers.

We have discovered that these UNIX machines does not update from default network path Server\Sophosupdate\CIDs\S000\EESAVUNIX\AIX_PPC but from this path Server\Sophosupdate\CIDs\S000\AIX_PPC

Unfortunately updates are downloaded to default path.

Is it possible to configure this path somehow?

Thanks,

Michal

 



This thread was automatically locked due to age.
Parents
  • Hello Michal,

    visible and managed [...] UNIX machines does not update from default network path
    do they show as compliant with the updating policy and are the Primary (and optionally Secondary) location as expected (i.e the paths SUM on the server deploys to)? AFAIK an updating policy sent to then endpoints contains all available products and their paths, the endpoint agent selects the appropriate for its platform but does not modify it.
    I don't have a license for UNIX so I can't say how it behaves or supposed to behave. I'd say the SEC should produce the correct paths from the subscription selected, the endpoints receive, process, and apply it accordingly. For the first I'd export the updating policy to check which paths are sent.

    Christian   

  • Hi Christian,

    Thanks for your reply.

    Yes UNIX computers are compliant with updating policy like WINDOWS and LINUX machines.

    I have created export you mentioned. Default path for updates is

    \\<server_name>\SophosUpdate

    I have checked in details of WINDOWS, LINUX and UNIX machines path from which they download updates

    Windows has \\<server_name>\SophosUpdate\CIDs\S000\SAVSCFXP\ and updated files are directly in this folder

    Linux has \\<server_name>\SophosUpdate\CIDs\S000\savlinux and updated files are directly in this folder 

    UNIX has \\<server_name>\SophosUpdate\CIDs\S000, but updated files are downloaded to \\<server_name>\SophosUpdate\CIDs\S000\EESAVUNIX\AIX_PPC

    somehow update manager is expecting updated files in different folder from the folder where they were downloaded from Sophos.

    If I could modify path where updates are placed, or path for update manager , issue would be fixed.

     

    Michal

     

     

     

  • Hello Michal,

    as said, I don't have a UNIX subscription so I can't check what SEC puts into the policy for the UNIX platforms. It might just be the "subscription tag" (Snnn). Previously a path for UNIX had two elements - EESAVUNIX and a platform-dependent subfolder like \AIX_PPC.

    Either SEC has always put EESAVUNIX into the policy and the endpoint added the platform path - then it'd be an issue with SEC 5.5.1.
    Or the path always ended in Snnn and the updater in version 9.15 builds the path incorrectly.

    A possible workaround is a specific updating policy for your UNIX machines (if feasible and if it indeed works as I assume): In the Primary Source add the \EESAVUNIX folder.  SEC will complain but accept this location. The endpoints should then build the correct path.

    Nevertheless you should contact Support to find out how it's supposed to work.

    Christian 

Reply
  • Hello Michal,

    as said, I don't have a UNIX subscription so I can't check what SEC puts into the policy for the UNIX platforms. It might just be the "subscription tag" (Snnn). Previously a path for UNIX had two elements - EESAVUNIX and a platform-dependent subfolder like \AIX_PPC.

    Either SEC has always put EESAVUNIX into the policy and the endpoint added the platform path - then it'd be an issue with SEC 5.5.1.
    Or the path always ended in Snnn and the updater in version 9.15 builds the path incorrectly.

    A possible workaround is a specific updating policy for your UNIX machines (if feasible and if it indeed works as I assume): In the Primary Source add the \EESAVUNIX folder.  SEC will complain but accept this location. The endpoints should then build the correct path.

    Nevertheless you should contact Support to find out how it's supposed to work.

    Christian 

Children