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

    Hello Azurus,

    you have probably read this thread on how to "customize" the removal, haven't you?

    SuppressCompetitorDetection works for me (although I've installed a free product for testing but as no avremove.log has been produced I'm sure it did not run at all). Of course the path for the key has to be changed on 64bit systems and I'd like to point out that - contrary to one's expectation - it has to be a REG_SZ value.

    machines are unable to perform the upgrade

    I think I'm missing something here - isn't the CRT only invoked when you deploy (using setup.exe) but not when AutoUpdate performs regular updates? Why do you have to deploy the new version instead of letting AU do the work?

    Christian

    :12941
Reply
  • 0

    Hello Azurus,

    you have probably read this thread on how to "customize" the removal, haven't you?

    SuppressCompetitorDetection works for me (although I've installed a free product for testing but as no avremove.log has been produced I'm sure it did not run at all). Of course the path for the key has to be changed on 64bit systems and I'd like to point out that - contrary to one's expectation - it has to be a REG_SZ value.

    machines are unable to perform the upgrade

    I think I'm missing something here - isn't the CRT only invoked when you deploy (using setup.exe) but not when AutoUpdate performs regular updates? Why do you have to deploy the new version instead of letting AU do the work?

    Christian

    :12941
Children
No Data