Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • +5 person also asked this people also asked this
  • Locked Locked
  • Replies 27 replies
  • Answers 4 answers
  • Subscribers 20 subscribers
  • Views 190808 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

Sophosinstall exe replaced with sophossetup exe in Sophos Central console

JustinTL

Hi all,

Clicking the Download Complete Windows Installer link under Protect Devices in our Sophos Central console now downloads a file called SophoSetup.exe. This is both for server and endpoints.  Does anyone know when this changed and when any documentation will be available about this as a search of the Sophos site so far produces no results and the document about automated installs still references sophosinstall.exe.  I assume that sophossetup.exe can still use the -q silent switch in batch files but will test this.

Thanks

Justin



This thread was automatically locked due to age.
  • 0 in reply to BmaltWCI

    So I see when running sophossetup /? from the cmd line:

    Just seems strange there was no announcement of such a change both to available switches and the setup file name changing etc - unless I'm looking in the wrong places for announcements of course!

    Thanks

    Justin

  • +1 in reply to JustinTL

    Yeah, that looks right. I tested this from 32-bit cmd line (for SCCM I test everything 32-bit) and it worked:

    SophosSetup.exe --products=intercept --quiet

    We only install InterceptX product, that's why the product= line. But --quiet worked.

    I don't know why the switches require two dashes, that seems weird to me, but whatever.

  • 0 in reply to BmaltWCI

    Tested this as well, replaced sophosinstall -q in the install batch file with SophosSetup --quiet and install works as intended.  As mentioned though, would have been nice to be notified of these changes - maybe the Sophos Central Dashboard would be a good place instead of/as well as the Global Security News?  Time for a trip to https://ideas.sophos.com/ methinks....

    Thanks

    Justin

  • 0

    I noticed the change too and my old package in SCCM has expired. Tried to set this up but the instructions on support for sccm deployment but it points to the old settings/installer. Thanks to the other person who replied here with the correct support page.

  • 0 in reply to Rohan Dwyer

    So this is why nothing is working anymore. I've got about 60-70 servers and networks which have a management component that downloads the file for each one, naming it sophosinstall.exe (because that's what it called it) and now it doesn't run at all.

     

    Spent a while trying to fix this. Cheers for the post identifying where the problem is! Now for hours fixing the batch install script on each system.

  • 0

    Does anyone know where the installer now creates install log files such as the bootrap and autoupdate log. 

     

    They used to be under the %temp% folder with the old installer but I cant find it there

     

    I also cant find it under c:\windows\temp, C:\program files(x86)\Sophos or anything useful in the Windows event viewer

     

    Thanks,

    Greg

  • 0

    So this change has been a major impact to our organization as our Enterprise Sophos Central is divided up into 50+ sub-estates for regional IT staff to manage their endpoints via their own managed sub-estates.

    However we procure and image systems centrally.

     

    Beyond the unannounced command line parameter changes the installer now has two phases.

     

    It creates under the programs(x86) folder a SOPHOS directory with a sub called CLOUDINSTALLEr.

     

    SophosSetup.exe then passes to an executable in that directory various other parameters (embedded in the SophosSetup.exe) that are unique to your portal in sophos center (i.e. customer token and MCS server)

     

    The primary issue we are seeing is that our script to install the proper sophosinstaller with MCS token adjustments is now not working as for some reason our freshly imaged systems on first boot are not presenting some environment setting that the new Sophos installer is looking for and when run manually SophosSetup.exe now says something like "environment error" a reboot is required . Note the previous installer did not have this issue.

    Unfortunately we too have been unable to find any logs anywhere (or wherever they may have moved) to tell us more information as to this issue.

     

    In the end.. THANK YOU Sophos for making changes and not really letting us know about this.

     

    Our imaging workflow and pipeline now is back to an automated step or two to get sophos installed due to this issue.   

     

  • 0 in reply to Alan Kurk

    Like most I think we're jumping the gun a little bit - while the .exe / URL change of the download was annoying someone kindly pointed out to me that this is just the thin installer and has been around a while too.

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

    Has all the command line options on that page too.

     

    For those who still want the old installer you can copy the URL it gives you and just change the end from sophossetup.exe to sophosinstaller.exe (or was it sophosinstall.exe) and it'll download it as usual.

     

    If anyone does find the logs folder or see's the documentation for it that would be handy - because I couldn't find them it's why I spent hours trying to figure out why it wouldn't deploy. 

     

    -Ian

  • 0 in reply to Ian Hellier

    Hi Ian,

     

    Thanks for that info. 

     

    I still would like to have log files produced during the install so I can troubleshoot failed installations. I assume that means I need to use the sophosinstall.exe file instead. Unless you know where the log files generated by sophossetup.exe are located?

    The URL I get on the deployment page just shows as 

    cloud.sophos.com/.../blank-windows-thin-installer. <GUID> here replaces my partner identifier. 

    I've tried adding sophosinstall.exe to this URL but I get a 'file not found'.

     

    Greg

Unfiltered HTML