clservices
The OfficeScan client runs the services listed in OfficeScan Client Services. You can view the status of these services from Microsoft Management Console.
Service |
Features Controlled |
Trend Micro Unauthorized Change Prevention Service (TMBMSRV.exe) |
|
OfficeScan NT Firewall (TmPfw.exe) |
OfficeScan firewall |
OfficeScan Data Protection Service (dsagent.exe) |
|
OfficeScan NT Listener (tmlisten.exe) |
Communication between the OfficeScan client and server |
OfficeScan NT Proxy Service (TmProxy.exe) |
|
OfficeScanNT RealTime Scan (ntrtscan.exe) |
|
The following services provide robust protection but their monitoring mechanisms can strain system resources, especially on servers running system-intensive applications:
Trend Micro Unauthorized Change Prevention Service (TMBMSRV.exe)
OfficeScan NT Firewall (TmPfw.exe)
OfficeScan Data Protection Service (dsagent.exe)
For this reason, these services are disabled by default on server platforms (Windows Server 2003 and Windows Server 2008). If you want to enable these services:
Monitor the system’s performance constantly and take the necessary action when you notice a drop in performance.
For TMBMSRV.exe, you can enable the service if you exempt system-intensive applications from Behavior Monitoring policies. You can use a performance tuning tool to identify system intensive applications. For details, see To use the Trend Micro Performance Tuning Tool:.
For desktop platforms (Windows XP, Vista, and 7), disable the services only if you notice a significant drop in performance.
To enable or disable client services from the web console:
Networked Computers > Client Management
For OfficeScan clients running Windows XP, Vista, or 7:
In the client tree, click the root domain icon or select specific domains or clients.
When you select the root domain or specific domains, the setting will only apply to clients running Windows XP, Vista, or 7. The setting will not apply to clients running Windows Server 2003 or Windows Server 2008 even if they part of the domains.
Click Settings > Additional Service Settings.
Select or clear the check box under the following sections:
Unauthorized Change Prevention Service
Firewall Service
Data Protection Service
Click Save to apply settings to the domain(s). If you selected the root domain icon, choose from the following options:
Apply to All Clients: Applies settings to all existing Windows XP/Vista/7 clients and to any new client added to an existing/future domain. Future domains are domains not yet created at the time you configure the settings.
Apply to Future Domains Only: Applies settings only to Windows XP/Vista/7 clients added to future domains. This option will not apply settings to new clients added to an existing domain.
For OfficeScan clients running Windows Server 2003 or Windows Server 2008:
Select a client in the client tree.
Click Settings > Additional Service Settings.
Select or clear the check box under the following sections:
Unauthorized Change Prevention Service
Firewall Service
Data Protection Service
Click Save.
To use the Trend Micro Performance Tuning Tool:
Download Trend Micro Performance Tuning Tool from:
http://solutionfile.trendmicro.com/solutionfile/1054312/EN/TMPerfTool_2_90_1131.zip
Unzip TMPerfTool.zip. to extract TMPerfTool.exe.
Place TMPerfTool.exe in the <Client installation folder> or in the same folder as TMBMCLI.dll.
Right-click TMPerfTool.exe and select Run as administrator.
Read and accept the end user agreement and then click OK.
Click Analyze. The tool starts to monitor CPU usage and event loading.
A system-intensive process is highlighted in red.
System-intensive process highlighted
Select a system-intensive process and click the Add to the exception list (allow) button .
Check if the system or application performance improves.
If the performance improves, select the process again and click the Remove from the exception list button .
If the performance drops again, perform the following steps:
Note the name of the application.
Click Stop.
Click the Generate report button and then save the .xml file.
Review the applications that have been identified as conflicting and add them to the Behavior Monitoring exception list. For details, see Behavior Monitoring Exception List.
See also: