Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 3553 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

Sophos ESDP offline updating

Radovicious

Hello.

At the very beggining I would like to apologize if there was already a thread about this subject - I wasn't able to find one using different keywords, though I find it hard to believe that noone ever had the same problem. I am an IT Technician at the Warsaw University of Technology, we are running 200-machine site license. Most of the computers are plugged into our network, but we've also got some that are at our employees houses etc., and as you might already guess, they haven't got access to the Internet. Therefore, Sophos installed on them can't update itself.

Here goes the question: is it possible to download offline installer for updates? Or some type of database files that we can copy into some directory so it will be available for Sophos to use?

Thanks in advance. Best regards,

Radoslaw Zydok

:10013


This thread was automatically locked due to age.
Parents
  • 0

    I agree that the CID level is a "safe" level to distribute the updates at and this would cover data, minor and major updates.  Is file size a concern?  If the user was bringing in a USB stick and dowloading roughly 100MB I assume that would be ok?

    I guess the frequency at which they can obtain the updates is one of the main factors that will influence the method you choose.

    One solution would be to create an SFX (WinRAR) of the CID (the creation of which could be automated to be created every hour/day and shared in someway, E.g. file share, web server to keep a recent copy available) that the users could download and run which would unpack them a local CID on their machine and have AutoUpdate point to that.  This way if they ever came "online" at somepoint in the future you could just change their configuration to point to a web CID for example.  

    This would essentially give them a 100MB (worse case all sub packages of the CID) exe to download that they could just run once they got home to update their "local" CID. Once SAU next checked it would update.  SAU could even be poked once unpacked to force an check and therefore an update.

    Regards,
    Jak

    :10113
Reply
  • 0

    I agree that the CID level is a "safe" level to distribute the updates at and this would cover data, minor and major updates.  Is file size a concern?  If the user was bringing in a USB stick and dowloading roughly 100MB I assume that would be ok?

    I guess the frequency at which they can obtain the updates is one of the main factors that will influence the method you choose.

    One solution would be to create an SFX (WinRAR) of the CID (the creation of which could be automated to be created every hour/day and shared in someway, E.g. file share, web server to keep a recent copy available) that the users could download and run which would unpack them a local CID on their machine and have AutoUpdate point to that.  This way if they ever came "online" at somepoint in the future you could just change their configuration to point to a web CID for example.  

    This would essentially give them a 100MB (worse case all sub packages of the CID) exe to download that they could just run once they got home to update their "local" CID. Once SAU next checked it would update.  SAU could even be poked once unpacked to force an check and therefore an update.

    Regards,
    Jak

    :10113
Children
No Data
Unfiltered HTML