Control Manager 3.5 uses agents to manage products on the Control Manager network. It can use two types of agents:
Trend VCS agents (version 1.84 or later)- this is an upgraded version of the original Trend VCS agent, specifically designed to be compatible with Control Manager 2.5 server
Older versions of certain Trend Micro products require this agent.
Control Manager agents (version 2.51 or higher)- this agent is built according to the Control Manager 2.5 (and above) architecture
Trend Micro Management Communication Protocol (MCP)- Trend Micro's next generation agent with enhanced security, SSO, one-way and two-way communication, and cluster node support
The following table enumerates the features supported by Trend VCS, Control Manager agents, and MCP agents.
|
Feature |
Management Communication Protocol |
Control Manager Agent |
Trend VCS Agent |
|
Outbreak Prevention Services (OPS) |
Yes |
Yes |
No |
|
Single Sign-on (SSO) |
Yes |
No |
No |
|
One-way/two-way communication |
Yes |
No |
No |
|
NAT support |
Yes |
No |
No |
|
Cluster node support |
Yes |
No |
No |
|
Agent polls TMCM for updates and commands |
Yes |
No |
No |
|
Re-registration with the Control Manager server if the Agent database is corrupted or deleted |
No |
Automatic after 8 hours |
Only when the communicator service is restarted |
|
Communication security |
HTTPS/HTTP |
Encryption with optional authentication |
No encryption, server-to-agent authentication only |
|
Communicators |
Yes |
Yes |
No |
|
Work and Idle state support |
Yes |
Yes |
No |
|
Communicator heartbeat |
Yes |
Yes |
No |
|
Notification: Virus pattern expired |
Yes |
Yes |
No |
|
Notification: Agent unable to update components |
Yes |
Yes |
No |
|
Notification: Agent unable to deploy components |
Yes |
Yes |
No |
|
Notification: Product service stopped |
Yes |
Yes |
Not supported. In InterScan VirusWall for Windows, this results in a "real-time scan stopped" notification instead |
Each managed product has its own agent, which is responsible for the following actions:
Receiving commands from the Control Manager server, via the Communicator
Collecting managed product status and logs, and sending them to the Control Manager server, via the Communicator