Resolution
fact
VigilEnt Security Agent for Windows 3.x
symptom
Batch File is not being executed by VigilEnt Security Agent for Windows Detect.
cause
fix
note
The batch file you have setup to execute must be located on the local box. It cannot be on a mapped drive or remote box because the VigilEnt Security Agent for Windows Detect will not be able to locate and execute it.
VigilEnt Security Agent for Windows 3.x
symptom
Batch File is not being executed by VigilEnt Security Agent for Windows Detect.
cause
VigilEnt Security Agent for Windows Detect cannot execute the command because the string of data is not entered correctly. The string of data in the executable tab in VigilEnt Security Agent for Windows Detect should look like:
- cmd.exe /c start (the directory of the batch file)
fix
To verify this refer to the following instructions below:
- Click Start | Programs | VigilEnt Security Agent | Configure VSANT Detect. The VigilEnt Security Agent for Windows Detect GUI will open.
- Double-click the Rule that is not executing the string of data. This will expand the rule showing Generic Condition and Action.
- Double-click Action to open the Actions GUI.
- Select the Exec tab.
- In the 'Command Name' field type the following:
- cmd.exe /c start (the directory of the batch file on the local machine)
- Click Add/Save.
- Click OK.
- Select Config File | Save from the Configure VSANT Detect window to apply changes.
note
The batch file you have setup to execute must be located on the local box. It cannot be on a mapped drive or remote box because the VigilEnt Security Agent for Windows Detect will not be able to locate and execute it.
Additional Information
Formerly known as NETIQKB31693