|
To isolate the problem, disable the TSC.exe process from starting at startup. Please do the following:
|
| |
|
|
1.
|
On the Security Server, open the ..\PCCSRV\ofcscan.ini file using a text editor like Notepad.
|
| |
|
2.
|
Under Global Setting section, add the "DisableTSCAtStart=1" parameter to disable the TSC.exe process.
|
| |
|
3.
|
Save and close the file.
|
| |
|
4.
|
Log on to the OfficeScan / CSM / WFBS console.
|
| |
|
5.
|
Deploy the new configuration to all clients:
|
| |
|
|
| |
•
|
For OfficeScan:
|
| |
|
|
| |
|
a.
|
Go to Networked Computers > Global Client Settings.
|
| |
|
b.
|
Click Save.
|
| |
|
|
| |
•
|
For CSM:
|
| |
|
|
| |
|
a.
|
Click Security Settings > Configure > Domain Configure > Client Privileges.
|
| |
|
b.
|
Click Save.
|
| |
|
|
| |
•
|
For WFBS:
|
| |
|
|
| |
|
a.
|
Click Security Settings > Configure > Domain Configure > Client Privileges.
|
| |
|
b.
|
Click Save.
|
| |
|
|
| |
The "dtas=dword:00000001" registry is created in the HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-CillinNTCorp\CurrentVersion\Misc. hive of the OfficeScan client/ CSM agent / WFBS agent.
|
| |
|
|
| |
Note: The "DisableTSCAtStart" parameter in the ofcscan.ini file will not change from the client side.
|
| |
|
|
If the issue persists, delay the RealTimeScan process from starting at startup. Do the following:
|
| |
|
|
|
a.
|
Open the Registry Editor (regedit.exe).
|
| |
|
|
| |
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.
|
| |
|
|
|
b.
|
Go to the HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Real Time Scan Configuration\ hive.
|
| |
|
|
|
c.
|
Change the value of the registry key "NTRtScanInitSleep" to "180000" (DWORD, Decimal).
|
| |
|
|
|
d.
|
Note: The unit is in milliseconds. The value "180000" will delay the start of the Real Time Scan for 3 minutes.
|
| |
|
|
If the issue still persists, resize the "PagedPoolSize" registry key by doing the following:
|
| |
|
| |
Notes:
|
| |
|
| |
•
|
This registry key will not work with Windows Vista or Windows Server 2008.
|
| |
|
| |
•
|
This workaround will not work if there is a startup option "/3GB" in the boot.ini file for Windows XP and Windows Server 2003.
|
| |
|
|
a.
|
Open the Registry Editor.
|
| |
|
| |
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.
|
| |
|
|
b.
|
Change the value of "PagedPoolSize" to "0xFFFFFFFF".
|
| |
|
|
c.
|
Restart the computer.
|
| |
|
|
If this does not work, run the Case Diagnostic Tool (CDT). Select all of the options, then send the log files to Trend Micro Technical Support.
|
Connect with us on
| | | |