About CPM Client Deployment

The Tasks created in the procedures described below can only be deployed to relevant computers (the number of which is indicated after the Task name). In the IBM BigFix environment, relevance is determined by a "relevance statement" which defines certain conditions that the computer must meet. Any computers running an agent can receive relevance statements, and when they do, they perform a self-evaluation to determine whether they are included in the criteria. Relevant computers will complete whatever Action has been specified.

When targeting more than a few computers, Trend Micro suggests that you target endpoints by property rather than by list. Targeting by property does not require a relevant computer status and allows for the use of logic such as:

"Install on all XP computers, in California, that are part of the User group."

Note: Conventional scan is the default scan method for clients.

CPM Console and Client System Requirements

A complete list of system requirements can be found in System Requirements.

For information on the IBM BigFix Server and Console requirements, refer to the IBM BigFix Installation Guide in IBM Knowledge Center.

Compatibility with Trend Micro OfficeScan

Trend Micro CPM is intended to replace OfficeScan clients with CPM clients, which can be managed using the scalability and flexibility of the console.

Before deploying CPM clients, you should use the native OfficeScan uninstall program to remove all installed OfficeScan clients and then restart them.

Incompatible or Conflicting Programs

For a complete list of incompatible or conflicting programs, see Conflicting or Incompatible Programs. The following is a short list of software that you should remove from the endpoints before deploying the CPM client:

  • Trend Micro OfficeScan and Trend Micro PC-cillin

  • Antivirus software, including Symantec AntiVirus, McAfee VirusScan, Sophos Antivirus, and eTrust Antivirus