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.
Parents
  • 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
Reply
  • 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
Children
No Data