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

SAVSCFXP versus ESXP - Whats the difference?

Wally

Does anybody know what the difference is between these 2 folders.

I had the clients originally getting updates from ESXP and then one day they were getting it from SAVSCFXP

I am now having all sorts of trouble.

How do I roll back the clients to look for the ESXP folder?

:15663


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

    HI,

    They should have different sub-folders, SAVSCFXP  contains the Sophos Client Firewall package, ESXP  is just SAV.

    Just because it's there doesn't mean the client have to use it.  That would depend on your licence to use it an if you choose to deploy the firewall component.  Either way the CID is still valid and can be used just like the ESXP .  If you like it just gives you the potential to deploy the firewall but you don't have to.

    What is the trouble you have?  Clients unable to find the share?

    If you open on one of the clients that's failing, the file:

    iconn.cfg

    found:

    C:\ProgramData\Sophos\AutoUpdate\Config \

    or

    C:\Program files\Sophos\AutoUpdate\Config \

    does that point to ESXP  rather than SAVSCFXP?  Is it a case of just sending down the right policy to the machines to point them at this new share?


    Regards,

    Jak 

    :15671
Reply
  • 0

    HI,

    They should have different sub-folders, SAVSCFXP  contains the Sophos Client Firewall package, ESXP  is just SAV.

    Just because it's there doesn't mean the client have to use it.  That would depend on your licence to use it an if you choose to deploy the firewall component.  Either way the CID is still valid and can be used just like the ESXP .  If you like it just gives you the potential to deploy the firewall but you don't have to.

    What is the trouble you have?  Clients unable to find the share?

    If you open on one of the clients that's failing, the file:

    iconn.cfg

    found:

    C:\ProgramData\Sophos\AutoUpdate\Config \

    or

    C:\Program files\Sophos\AutoUpdate\Config \

    does that point to ESXP  rather than SAVSCFXP?  Is it a case of just sending down the right policy to the machines to point them at this new share?


    Regards,

    Jak 

    :15671
Children
No Data