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

Creating a 'Full' Sophos Cloud Windows installer to minimize initial bandwidth utilization - NO LONGER SUPPORTED!

 

We just purchased Sophos Central last week with several hundred seats for endpoint and intercept X. I am really pleased with the product however, last Monday there was documentation on how to create a "FULL" installer to prevent hundreds of clients simultaneously downloading the ~250MB installer, unfortunately by last Friday when I purchased the product and went to create the installer this feature was no longer available and all documentation pointing the the following KB article was pulled offline.

 https://community.sophos.com/kb/en-us/121318

Anyone have any ideas on how to proceed besides install on a handful of clients at a time or paying a couple thousand dollars for professional support?

I'm sure I am not alone as any enterprise installation will be facing the same situation, unless you are fine with pumping a 100GB down your network lol.

Thanks in advance for any help you can provide!

 

Charlie



This thread was automatically locked due to age.
Parents Reply Children
  • The new installer will use the Update Cache during the install. The old installer only used the cache once the Endpoint was installed. If you tail the installer log you can watch it choose the Update Cache.

  • The installer log should look something like this

    2018-01-27T08:57:57.3852599Z INFO : Analyzing whether to update from Sophos CDN or update cache
    2018-01-27T08:57:57.3852599Z INFO : Checking access to update cache: mc-sgni.ukaws.co.uk:8191
    2018-01-27T08:57:57.3852599Z INFO : Updating configured to use: HTTPS
    2018-01-27T08:57:57.3852599Z INFO : Update Cache Cert Path folder: C:\\ProgramData\\Sophos\\Certificates\\AutoUpdate\\Cache
    2018-01-27T08:57:57.5258851Z INFO : Successfully connected to cache
    2018-01-27T08:57:57.5258851Z INFO : Cache response time: 85ms
    2018-01-27T08:57:57.5258851Z INFO : Analysis complete - Using update cache: mc-sgni.ukaws.co.uk:8191
    2018-01-27T08:57:57.5258851Z INFO : Updating from cache: mc-sgni.ukaws.co.uk:8191
    2018-01-27T08:57:57.5258851Z INFO : Updating configured to use: HTTPS

    Hope that helps.

  • I have set up an update cache server but having trouble pulling down updates, verified everything working and agent is updating just failing to pull down the cache. Restarted server and also the service in services.msc. I'm going to let that simmer overnight and hopefully when I come in tomorrow I'll be ready to test.

     

    Thanks again for the tip can't wait to try it!

  • If you run this command - Get-Content "c:\programdata\sophos\UpdateCache\Logs\uc.log" -wait | where { $_ -match “State changing” }

    You should see - [2017-09-10T17:57:37Z] [cfc] Info: [StateMachine::Run:53] State changing initial_download -> active

    Hope this helps.

  • Looks like the cache server did indeed solve the problem! Thanks all for the suggestion!

  • Charlie, were you looking at getting updates or the initial installer being pulled from it instead of the internet cache?

     

    I've installed the local update cache but had no success in having the installer pull from it, and instead it sill pull data from the internet. I keep maxing out my internet pipe trying to install it. Complaining just because it is very inefficient way to install it.

     

    Any thoughts?

  • Are you sure you are using the Thin Installer? It should be called SophosSetup.exe. Also make sure the Endpoint can connect to Update Cache on 8191.

    community.sophos.com/.../122577