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

Disabling Sophos Competitor Check on deploy (upgrade)

Azurus

We are running Sophos alongside Cisco CSA. I have 450 machines that are unable to perform the upgrade unless I remove the Cisco CSA uninstall registry key, perform install, then re-import it. We will be running them together, and it's aggravating that Sophos doesn't want to play nice. They shouldn't be able to dictate whether I can run certain software on my machine, and if they do, it should default to playing nice with it rather than not installed. Now I have over 400 machines in an error state.

I have tried changing the ProductCatalog.xml and removing the entry for CSA in the CRT.config on the SUM install share. This does not work. The MSI fails with the same issue.

I have also tried adding the registry values:

SuppressCompetitorDetection=1

SuppressPreSAVCDT=1

...to HKLM\Software\Sophos\SAVService\SetupOptions\    as it says is possible here: http://www.sophos.com/support/knowledgebase/article/36207.html#MachGlobConfigFiles

Error logs continue to show that the MSI installation failed due to "A product with a similar function installed". 

Please help. Thanks

:12931


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

    As was suspected, and after consulting with the Sophos engineers, the second check is done during the install, and not pre-install.

    To fix this problem, a .cfg file was created and put into the root of the update share. In my case that was " ..\CIDs\S000" . The .cfg file was composed of the following.

    [SetupOptions]
suppressCRT=1
SuppressCompetitorDetection=1
SuppressPreSavCDT=1

    Once the file was in-place, I had to kind of "compile" the install so it would include the .cfg file when it installed or updated from the share. I had to run this from the command line and reference the UNC path of each share and run the command. I can't remember the exact syntax used but it invoked the ConfigureSAV.exe file on the SAVSCFXP\savxp directory.

    :13549
Reply
  • 0

    As was suspected, and after consulting with the Sophos engineers, the second check is done during the install, and not pre-install.

    To fix this problem, a .cfg file was created and put into the root of the update share. In my case that was " ..\CIDs\S000" . The .cfg file was composed of the following.

    [SetupOptions]
suppressCRT=1
SuppressCompetitorDetection=1
SuppressPreSavCDT=1

    Once the file was in-place, I had to kind of "compile" the install so it would include the .cfg file when it installed or updated from the share. I had to run this from the command line and reference the UNC path of each share and run the command. I can't remember the exact syntax used but it invoked the ConfigureSAV.exe file on the SAVSCFXP\savxp directory.

    :13549
Children
No Data