Kernel mode memory usage of the Client/Server Security Agent is very high

Support
Solution ID Last Updated
1036648 Date : 2011/05/13 Time:8:42 AM , (PST)


Product/Version Platform
Client Server Messaging Security for SMB - 3.6;Client Server Security for SMB - 3.6;
Not Applicable - N/A

Problem Description

The system resource (kernel mode memory) usage of the Client/Server Security Agent is very high, and prevents other applications and/or system drivers from working properly.

Solution

This occurs because Scan Engine 8.55 (released on October 31, 2007), which is used by the Client/Server Security Agent, disabled the “SystemMapView” option to fix a conflict with Express Mail Server. Disabling the option increased kernel memory utilization by 18-20 MB. In addition to this, the growing virus pattern (LPT$VPN.*) also uses kernel memory.

   

As a workaround, do either of the following:

   

Option I: Contact Technical Support to request for a server-side tool that will automate the following for all clients:

 

Enable the “SystemMapView” option

 

Set the “PagedPoolSize” option to the maximum value

   

Option II: Manually set “PagedPoolSize” to the maximum value and enable the “SystemMapView” option.

   

To set the “PagedPoolSize” to maximum:

   

1.

Open the Registry Editor:

 

a.

From the desktop, click Start > Run.

 

b.

Type "regedit" then click OK.

 

Important: Always create a backup before modifying the registry. Incorrect registry changes may cause serious issues. Should this occur, restore it by referring to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

2.

Go to the HKEY_LOCAL_MACHINE \System\CurrentControlSet\Control\Session Manager\Memory Management hive.

3.

Change the value of the "PagedPoolSize" key to “0xFFFFFFFF”.

4.

Reboot the machine.

   

To enable “SystemMapView”:

   

1.

Open the Registry Editor:

 

a.

From the desktop, click Start > Run.

 

b.

Type "regedit" then click OK.

 

Important: Always create a backup before modifying the registry. Incorrect registry changes may cause serious issues. Should this occur, restore it by referring to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

2.

Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSApiNt\Parameters.

3.

Add a new DWORD value called "EnableSystemView" then assign it a value of "1".

4.

Reboot the machine.

   

Note: These settings will be retained during upgrades.


Rate this Solution
Did this article help you?

Please provide your comments to help us improve this solution.

 
  *This form is an automated system. General questions, technical, sales and product-related issues submitted through this form will not be answered.
 
 

Connect with us on