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

Sophos Endpoint 10

visualjazz

Pains we've had with moving to Endpoint 10 (note - we tested on 34 clients with no issues and went ahead with a larger deployment.)

Environment - Win7 x64 SP1

UNC paths start acting funny - kicking you back up to top level (this happens randomly).

 - This also applies to drive maps.

 - Also affects DFS paths and non DFS paths

Turning off web protection on the policy level makes clients no longer have internet.

 - Resolved by turning off the web service (net stop servicename)

Outlook 2010 crashing - now this may be indirect but since moving to endpoint 10 we've had a lot of clients just freeze.

Application Control differs from policy - this is caused when you add the Dallas Cowboys to the blocked list.

We are moving back to v9.7 currently.

:20979


This thread was automatically locked due to age.
  • 0

    We are talking to them currently.

    Nothing to do with the installation, everything is basically stock standard.

    :21025
  • 0

    Hi

    "Application Control differs from policy - this is caused when you add the Dallas Cowboys to the blocked list. "

    Seems to be a bug in the data, the VVF.xml file (C:\ProgramData\Sophos\Sophos Endpoint Management\5.0\Updates\Secure\SDFs\SophosMA\sec\MSDC\vvf.xml ) has 2 entries for this.  If you move one of them to the left in the dialog, does it comply?  I'll raise a ticket with support about this.

    I've not seen any problems with UNC paths as yet or the other problems, and http://www.sophos.com/support/knowledgebase/article/116241.html

    might help explain internet problems.

    Jak

    :21029
  • 0

    Hello All,

    I am new to the Sophos community as well as working with Sophos anti-virus.  The company I work for are currently in the process of purchasing Sophos and have implemented 3 laptops with v10 for testing purposes.  We have been having some issues and we have opened a ticket with technical support.

    Sophos Ticket #3048603 (Device control failed to disable device)

    This seems to describe the symptoms we’’’’re seeing, and we are running this version of PGP desktop too.

    http://www.symantec.com/connect/forums/pgp-wde-102-sophos-endpoint-security-and-control-freezes

    Desktop OS: Win7 x32 SP1 and Win7 x64 SP1 (on-going issues)

    - Client tend to not boot up while on the network, desktop just hangs at "waiting".

    - After client does boot up the PC will automatically perfrom a reboot

    Of course after contacting Symantec in regards to this the response was to purchase Symantec Endpoint Virus Protection instead.  Sophos technical support did contact us saying the fix will be in release v10.0.2 which is supposed to be out this week.  As far as the functionality as well as the interface goes I like Sophos. Apparently Sophos does not like what we are running on our laptops and hopefully this can all be figured out soon any advice will be greatly appreciated.

    :21175
  • 0

    HI,

    The current issue I'm aware of with PGP and SAV 10 is to do with the LSP component. As far as I know this is to be fixed in 10.2. There was however, an unrelated issue between PGP and SAV a while best described by the post on that page:

    ". . .we have run extensive tests internally around this issue and these indicate the issue lies outside of the Sophos product line. The issue appears to relate to the calling of the Windows API, ::LogonUser. Auto-update calls this every time it updates but the issue can be replicated by calling the API when Sophos hasn't even been installed on the system which would indicate an issue with the Symantec PGP 10.2.

    Could you:

    1. Clear the directory:  
      "C:\ProgramData\Sophos\AutoUpdate\Logs \" of  "Alupdate*.log" files, just to remove the history.
    2.  Kick off another update of AutoUpdate and then paste here the logs when you have the problem.  Do they mention: LogonUser , on an error line.  

    Maybe you could scan the current logs you have for that text first before deleting them,  The main idea behind clearing them is to shrink them just to cover one update for posting here.

    If this is the case, then 10.2 will not fix it and this is a Symantec problem where it prevents the LogoUser function being called.  The AutoUpdate logs should help identify the problem you have.

    Regards,

    Jak

    :21195