Kaseya Community

CheckDefsUpToDate_Symantec.vbs script no longer working now that customer is running Symantec Endpoint Protection 12.1.3001.165

This question is not answered

Posted by Salvatore DiPietro

on Dec 6, 2013 7:16 PM

We have been using a VBScript developed by Onno de Vries in a procedure for customers using Symantec Endpoint Protection to make certain that the virus definitions are up to date. This has been working fine until we had a customer upgrade to SEP12.

The text of the vbscript is:

'**
'**
'**
'** Developed by Onno de Vries, Senior Consultant Kaseya Benelux on behalf of Kaseya.
'** Date : 05-11-2007
'** Version: 1.0
'**
'**
'*************************************************************************************
'** Several Declarations
'**
Dim AgentDir,FileLocation,FileName,SearchCurrent,SearchUsed,StartChar,CurrentFound,UsedFound
Const ForReading = 1
'**
'** Enable parsing arguments to the vbs and collect them
'**
Set ArgObj = Wscript.Arguments
AgentDir = ArgObj(0)
FileLocation = ArgObj(1)
'**
'** Set Variables for further processing
'**
FileName = "DefInfo.dat"
SearchUsed = "CurDefs="
StartChar = "="
UsedFound = 0
'**
'** Open the definfo.dat file for reading to find the line containing the Current Definitions and Used Definitions
'**
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.OpenTextFile(FileLocation + "\" + FileName, ForReading)
'Set objFile = objFSO.OpenTextFile("c:\temp\DefInfo.dat", ForReading)
'**
'**Search the line in the file that contains the Definition numbers.
'**
Do Until objFile.AtEndOfStream
strLine = objFile.ReadLine
If Instr(1, strLine, SearchUsed, 1) > 0 Then
'**
'**The line containting the Current Definition is found, now locate the Current Definition itself within this line.
'**
CurrentDefinition = Mid(strLine,Instr(1, strLine, StartChar, 1)+1, Len(strLine)-Len(SearchCurrent))
'**
'**set pointer for further processing (see below)
'**
CurrentFound = 1
Exit do
End If
Loop
ObjFile.Close
If CurrentFound =1 Then
'**
'** calculate the difference in days, write this to a seperate file to be used in the Kaseya script.
'** Then you can enter any number of days in the 2nd script If statement that your maximum difference is before an alarm is generated.
'**
dC = Mid(CurrentDefinition, 7,2)
mC = Mid(CurrentDefinition, 5,2)
yC= Left(CurrentDefinition,4)
Age = DateDiff("d",CDate(dC & "/" & mC & "/" & yC),Date)
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\Age.txt")
objFile.WriteLine(Age)
objFile.Close
'**
'**Write the Current Definition to a file, so the Kaseya script can pick it up.
'**
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\CurrentDefinition.txt")
objFile.WriteLine(CurrentDefinition)
objFile.Close
'**
'**Write the Used Definition to a file, so the Kaseya script can pick it up.
'**
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\UsedDefinition.txt")
objFile.WriteLine(UsedDefinition)
objFile.Close
Else
'**
'** When Current of Used Definition is not found, check SeachCurrent/SearchUsed/StartChar/ variables and/or NumberSearch routine!
'** For notifying you that something is wrong, Definition number "0000" is entered in the file (the Kaseya Script will pick this up.)
'**
If CurrentFound = 0 And UsedFound = 0 Then
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\CurrentDefinition.txt")
objFile.WriteLine("0000")
objFile.Close
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\UsedDefinition.txt")
objFile.WriteLine("0000")
objFile.Close
Else
if CurrentFound = 1 Then
'**
'** When only Current Definition is found, check SeachCurrent/SearchUsed/StartChar/ variables and/or NumberSearch routine!
'** For notifying you that something is wrong, Used Definition number "0000" is entered in the file (the Kaseya Script will pick this up.)
'**
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\UsedDefinition.txt")
objFile.WriteLine("0000")
objFile.Close
Else
'**
'** When onlyUsed Definition is found, check SeachCurrent/SearchUsed/StartChar/ variables and/or NumberSearch routine!
'** For notifying you that something is wrong, Current Definition number "0000" is entered in the file (the Kaseya Script will pick this up.)
'**
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(AgentDir + "\CurrentDefinition.txt")
objFile.WriteLine("0000")
objFile.Close
End If
End If
End If
set ArgObj = Nothing

What I am seeing now is that the procedure running this script just hangs no matter how much time you give it. When I attempt to run the script using wscript I get the following message:

Script: C:\Proguard\CheckDefsUpToDate_Symantec.vbs

Line: 18

Char: 2

Error: Subscript out of range

Code: 800A0009

Source: Microsoft VBScript runtime error

I have researched the error and it appears to be related to the following arguements:

AgentDir = ArgObj(0)

However I have had no luck in figuring out what exactly is wrong. I am a noob when it comes to vbscripts, so any help would be greatly appreciated.

Thanks

All Replies

Posted by zippo

on Dec 6, 2013 8:01 PM

AgentDir is the first argument that you're passing to the script when you call it. FileLocation is the second argument that you pass when you call the script. Something is wrong with the first argument you are passing to the script. Check to see if the Agent Directory location has changed with the SEP Agent upgrade and then pass the corrected info to the script when you call it.

Posted by Salvatore DiPietro

on Dec 6, 2013 10:13 PM

As AgentDir is not set in the script itself, is that something that would be configured in another portion of the Agent Procedure, or does it have a default value (like %systemroot%\temp)?

Posted by Paul Haaker

on Dec 7, 2013 2:47 AM

I bet the registry returns the path for the definfo.dat files as being something like

F:\Program Files\Common Files\Symantec Shared\VirusDef\20131127.003

But I'll also bet if you check the definfo.dat file is actually in

F:\Program Files\Common Files\Symantec Shared\VirusDefs

This seems to be the case with SEP 12

So I just added the follwing to my vbscript.

Essentially if it cant find definfo.dat in the path from the registry then look up one level as well

e.g.

If (CreateObject("Scripting.FileSystemObject")).FileExists(FileLocation + "\" + FileName) Then

else

if instr(FileLocation,"VirusDefs") > 0 then

Trimlength = instr(FileLocation,"VirusDefs")

FileLocation = left(FileLocation,Trimlength + 8)

end if

Hope this helps

Paul

Typos fixed
[edited by: Paul Haaker at 9:13 PM (GMT -8) on Dec 6, 2013]

Posted by zippo

on Dec 8, 2013 4:36 AM

There is no parsing of the registry in the original script. The AgentDir path is the first one of two arguments that are passed to the script by the calling procedure. The procedure calling the script would need to be edited to provide the correct path for the 12.x version of SEP. If you decide to go with Paul's route, which is certainly doable, you would need to edit the script to remove the requirement for the first argument and use Paul's snippet to replace it. Then you would also need to edit the calling procedure so that you didn't pass the path when the script is called.

Posted by Paul Haaker

on Dec 8, 2013 5:16 AM

FileLocation = ArgObj(1) is passed to the script from the Kaseya script , which checks the registry values of the vaRIOUSE KETS DEPENDING ON IF IT IS v11 OR 12 ETC

E.G. HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\SharedDefs\DEFWATCH_10

In SEP 11 the value returned was something like F:\Program Files\Common Files\Symantec Shared\VirusDef\20131127.003 and it was in this path the vbscript could then locate the definfo.dat.

BUT in SEP 12 it is no longer the correct path , hence you need to look in e.g. F:\Program Files\Common Files\Symantec Shared\VirusDef instead.

So I still use both arguments as A) I need to know where to save the age.txt , UsedDefinition.txt etc files , and B I need to know the path to the definfo.dat

So my added code ..would go

AgentDir = ArgObj(0)

FileLocation = ArgObj(1)

'**

'** Set Variables for further processing

'**

FileName = "DefInfo.dat"

If (CreateObject("Scripting.FileSystemObject")).FileExists(FileLocation + "\" + FileName) Then

else

if instr(FileLocation,"VirusDefs") > 0 then

Trimlength = instr(FileLocation,"VirusDefs")

FileLocation = left(FileLocation,Trimlength + 8)

end if

SearchUsed = "CurDefs="

StartChar = "="

UsedFound = 0

'**

'** Open the definfo.dat file for reading to find the line containing the Current Definitions and Used Definitions

'**

Set objFSO = CreateObject("Scripting.FileSystemObject")

etc

as per the orginal post

Posted by Paul Haaker

on Dec 8, 2013 5:17 AM

FileLocation = ArgObj(1) is passed to the script from the Kaseya script , which checks the registry values of the vaRIOUSE KETS DEPENDING ON IF IT IS v11 OR 12 ETC

E.G. HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\SharedDefs\DEFWATCH_10

In SEP 11 the value returned was something like F:\Program Files\Common Files\Symantec Shared\VirusDef\20131127.003 and it was in this path the vbscript could then locate the definfo.dat.

BUT in SEP 12 it is no longer the correct path , hence you need to look in e.g. F:\Program Files\Common Files\Symantec Shared\VirusDef instead.

So I still use both arguments as A) I need to know where to save the age.txt , UsedDefinition.txt etc files , and B I need to know the path to the definfo.dat

So my added code ..would go

AgentDir = ArgObj(0)

FileLocation = ArgObj(1)

'**

'** Set Variables for further processing

'**

FileName = "DefInfo.dat"

If (CreateObject("Scripting.FileSystemObject")).FileExists(FileLocation + "\" + FileName) Then

else

if instr(FileLocation,"VirusDefs") > 0 then

Trimlength = instr(FileLocation,"VirusDefs")

FileLocation = left(FileLocation,Trimlength + 8)

end if

SearchUsed = "CurDefs="

StartChar = "="

UsedFound = 0

'**

'** Open the definfo.dat file for reading to find the line containing the Current Definitions and Used Definitions

'**

Set objFSO = CreateObject("Scripting.FileSystemObject")

etc

as per the orginal post

Posted by zippo

on Dec 10, 2013 6:47 PM

That looks good, Paul and should answer the OP's questions.

Posted by Salvatore DiPietro

on Dec 10, 2013 6:52 PM

My apologies for not getting back to you sooner. Thank you both for your assistance on this. I am testing it now and will let you know how it works out.

Posted by Salvatore DiPietro

on Dec 10, 2013 8:54 PM

It appears that the procedure is still stalling when it goes to run the VBScript, even after adding the lines that Paul suggested in the location that he suggested. It appears that the script is still not getting the correct information from the agent procedure.

I have looked the procedure over and cannot see where this is failing. I have exported the procedure and the xml data for it is below.

<?xml version="1.0" encoding="utf-8"?>

</Condition>

<Then>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Statement>

</Then>

<Else>

</Statement>

</Statement>

</Else>

</If>

</Body>

</Procedure>

</ScriptExport>

Posted by Paul Haaker

on Dec 10, 2013 9:47 PM

Log onto the machine and check.

I think the reg path you're returning as the DefInfoLocation is incomplete

What value is returned from

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\Content\Virusdefs

This should return the path to the definfo.dat file so I think you need to be searching for

e.g What does

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\CurrentVersion\SharedDefs\DEFWATCH_10

return instead ?

Paul

Script checking if Symantec Endpoint Protection AV is outdated two or more days and putting only those machines in report

Hover popup and Run Procedure Now no longer working?

Remove Symantec Endpoint Protection

Symantec Endpoint Protection

Symantec Endpoint Protection and Discovery

CheckDefsUpToDate_Symantec.vbs script no longer working now that customer is running Symantec Endpoint Protection 12.1.3001.165