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

Tracking Sophos endpoint health

VCU

Not all Sophos customers will be using the Sophos Enterprise Management system to track the health of endpoints. We user data mining of endpoints through applications like LANdesk. We also do scripts to check the health of systems. But with this new numbering change we have lost the options to do either.

SophosAV version number changes

http://www.sophos.com/support/knowledgebase/article/110781.html

What do others do to track the health of Sophos endpoints?

Does this product change above impact you?

Thanks

:2624


This thread was automatically locked due to age.
  • 0

    Fortunately for me, this doesn't matter, as I use the console to check everything.

    I know in some environments you aren't always free to access what you need, so other forms of checking need to be run, but then you have to question why in fact you don't have the access to or use the console to track the goings on..?

    :2627
  • 0

    What information are you trying to obtain from the client to pass to LANdesk?

    Thanks.

    :2692
  • 0

    Hello :)

    This a might help even though it was for a different purpose. (troubleshooting)

    I created a script which would check sophos and fix anything if required.
    It does the following:

    check if Sophos AutoUpdate is installed (Install if nec.)

    Check if the Anti-Virus is installed. (install if nec.)

    > Check RMS is installed (Install if nec. - this wouldnt be your case if you are not using a console)

    after that i do configuratins checks.

    check if the autoupdate location is correct (correct if nec)

    check if the iupd config file is correct (correct if nec  - more for rms)

    For one of our clients, i did a check to see if the task scheduler service was started (scans werent going down to the machines)

    There is other stuff i added to the script

    What OS it is (windows 7 copy location are different)

    Machine name,  how long it took plus the amount of space left on a machine.

    Once it had done the above. it copied the log to the server so I can monitor it from one location.
    If the above is installed and updating with the right details, you probably wont find a machine with an older version.

    Nothing beats the console though. :)

    :2695
  • 0

    What I check with LANDesk now is the Sophos product build version number which has been changing each month. This we can track from the registry. It will point out what systems are broken. 

    Sophos breaks:

    Over the past 3 years I've seen Sophos break or fail to install because of incorrect Windows permissions. I created a custom repair program to address the numberous Windows permission errors seen. Most of them are covered here:

    http://www.sophos.com/support/knowledgebase/article/32249.html

    http://www.sophos.com/support/knowledgebase/article/39357.html

    This addresses most of the cases seen but there are a few that have permission issues that could not be corrected through a script and the procedure "I" from article 32249 is requried.

    That script looks pretty nice.

    Thanks

    :2714
  • 0

    Would you mind sharing the script you mentioned in this post?

    Thank you so much.

    :22463