Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com

Login

Remember Me

Directory Tree

check_sophos

Rating
4 votes
Favoured:
0
Current Version
0.2
Last Release Date
2011-11-11
Compatible With
  • Nagios 3.x
Owner
License
GPL
Hits
90072
Files:
FileDescription
check_sophos.vbsCheck_sophos.vbs
Nagios CSP

Meet The New Nagios Core Services Platform

Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.

Monitoring Made Magically Better

  • Nagios Core on Overdrive
  • Powerful Monitoring Dashboards
  • Time-Saving Configuration Wizards
  • Open Source Powered Monitoring On Steroids
  • And So Much More!
Check_sophos.vbs checks that the current virus definition date for Sophos Antivirus is within acceptable bounds.
When SNMP is not an option this is pretty useful.

' Script: check_sophos.vbs
' Ripped from the check_av plugin by Matt White
' Version: 0.2
' changelog: added check x64 support 6-DEC-2012
' Updated code by robert.fults001@gmail.com
' Date: Nov. 11, 2011
' Details: Check that the current virus definition date for Sophos Antivirus is within acceptable bounds

' NSC.ini:
' check_sophos=cscript.exe //NoLogo scriptscheck_sophos.vbs /W:$ARG1$ /c:$ARG2$

' Call with:
' ./check_nrpe -H 10.9.48.185 -c check_sophos -a 0 1
Reviews (2)
bySpik31, October 24, 2014
Great script for checking windows machines with sophos. Although the enterprise console does this, it's useful for monitoring individual important servers. This also is useful because it is written in vbs and can be applied to 2003 machines as well as 2008!
bymsweet, March 21, 2013
C:Program FilesNSClient++scriptscheck_sophos.vbs(28, 3) Microsoft VBScript runtime error: Type mismatch: 'Cint'
Owner's reply

How are you calling the check and what OS are you running this on? I have this script running with no issues on several Windows Server 2003 and 2008 R2 instances.