Dell PowerStore 1200T Using the Common Event Enabler 8.x on Windows Platforms - Page 24

Setting container handling policies, Modifying LimitChoiceStop settings, Trend Micro ServerProtect

Page 24 highlights

Steps 1. Navigate to the Symantec Protection Engine Status page. Click Configuration and Resources. 2. Specify a temporary directory for scanning. NOTE: Allow enough room for this directory to grow because it can become several GBs in size. If a local AV solution is used, ensure to also exclude this directory from scanning. A local AV solution on the AV machine must not be allowed to scan the temporary working directory in use by Symantec Protection Engine. Setting container handling policies The RPCRequestTimeout value set in the viruschecker.conf file (the default is 25000 milliseconds) should be set to greater than the Symantec Protection Engine Container File Processing Limit for the time to extract a file. Not doing so can cause the VNX Data Mover or Unity NAS server to repeat the scans for large files to other AV machines while the scan is still in progress by the AV machine. This timeout should be set 30 to 60 seconds higher than the container file processing limit so that the VNX Data Mover or Unity NAS server has adequate time to receive the response. The Symantec timeout can be set lower depending on the security scanning requirements and processing load of the AV machine. Modifying LimitChoiceStop settings The LimitChoiceStop parameter controls container violations actions. If this is set to false, the scan engine allows access to a file that is violating some of the container policies (such as max extract time exceeded) and will only log this error. If this is set to true (the default setting), the scan engine blocks access to (deletes) the file on the container violations. About this task You need to set the LimitChoiceStop parameter to false. Failure to perform this step results in an AV_INTERFACE error and CAVA will not come online: Steps 1. Edit the filtering.xml file that resides in the SAV install directory. 2. Set the LimitChoiceStop option to false. Trend Micro ServerProtect If you are installing Trend Micro ServerProtect, use the installation path shown in Installation procedure for Trend Micro. Table 5. Installation procedure for Trend Micro Step Action Procedure 1. Create a domain user with the EMC virus-checking right. Configuring the Domain User Account 2. Configure virus-checking parameters on the VNX Data Movers Configuring viruschecker.conf or Unity NAS servers. 3. Install CAVA (as part of CEE) on the Windows AV machines. Installing the Common Event Enabler 4. Install the Trend AV engine. Install Trend Micro ServerProtect 5. Start the virus-checking client on the VNX Data Movers or Unity Managing the VC Client NAS servers. 6. Verify the CAVA installation. Verify the installation 24 Installing Third-Party Application Antivirus Engines

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84

Steps
1.
Navigate to the Symantec Protection Engine
Status
page. Click
Configuration
and
Resources
.
2.
Specify a temporary directory for scanning.
NOTE:
Allow enough room for this directory to grow because it can become several GBs in size. If a local AV solution is
used, ensure to also exclude this directory from scanning. A local AV solution on the AV machine must not be allowed to
scan the temporary working directory in use by Symantec Protection Engine.
Setting container handling policies
The
RPCRequestTimeout
value set in the
viruschecker.conf
file (the default is 25000 milliseconds) should be set to
greater than the Symantec Protection Engine Container File Processing Limit for the time to extract a file. Not doing so can
cause the VNX Data Mover or Unity NAS server to repeat the scans for large files to other AV machines while the scan is still in
progress by the AV machine.
This timeout should be set 30 to 60 seconds higher than the container file processing limit so that the VNX Data Mover or
Unity NAS server has adequate time to receive the response. The Symantec timeout can be set lower depending on the security
scanning requirements and processing load of the AV machine.
Modifying LimitChoiceStop settings
The
LimitChoiceStop
parameter controls container violations actions. If this is set to false, the scan engine allows access to
a file that is violating some of the container policies (such as max extract time exceeded) and will only log this error. If this is set
to true (the default setting), the scan engine blocks access to (deletes) the file on the container violations.
About this task
You need to set the
LimitChoiceStop
parameter to false. Failure to perform this step results in an
AV_INTERFACE
error
and CAVA will not come online:
Steps
1.
Edit the
filtering.xml
file that resides in the SAV install directory.
2.
Set the
LimitChoiceStop
option to
false
.
Trend Micro ServerProtect
If you are installing Trend Micro ServerProtect, use the installation path shown in
Installation procedure for Trend Micro
.
Table 5. Installation procedure for Trend Micro
Step
Action
Procedure
1.
Create a domain user with the EMC virus-checking right.
Configuring the Domain User Account
2.
Configure virus-checking parameters on the VNX Data Movers
or Unity NAS servers.
Configuring viruschecker.conf
3.
Install CAVA (as part of CEE) on the Windows AV machines.
Installing the Common Event Enabler
4.
Install the Trend AV engine.
Install Trend Micro ServerProtect
5.
Start the virus-checking client on the VNX Data Movers or Unity
NAS servers.
Managing the VC Client
6.
Verify the CAVA installation.
Verify the installation
24
Installing Third-Party Application Antivirus Engines