Pattern File and Engine Updates
It is important to keep your CPM clients current with the latest pattern and engine files from Trend Micro. The update process can be scheduled to occur automatically and is transparent; there is no need to remove the old pattern or install the new one.
Pattern Rollbacks
CPM supports pattern "rollbacks", that is, swapping out the current pattern to a different one. Although seldom used, it is useful in case there is a problem with the pattern file, for example to address an issue of false positives. The default is to keep 15 patterns on the server for clients to roll back to if necessary, but you can set this number as high as 100 (in the CPM Dashboard, click and scroll to the bottom of the screen).
Incremental Updates
To reduce network traffic generated when downloading the latest pattern, the Trend Micro ActiveUpdate server includes incremental pattern updates along with the full pattern file. Updates represent the difference between the previous pattern file and the current one. Like the full pattern file, incremental updates download and apply automatically. Incremental updates are available to both the BigFix Server (which typically downloads pattern updates from the ActiveUpdate server) and to CPM clients that are configured to get their updates from the server.
Updates from the "Cloud"
Clients typically receive their updates from the BigFix Server or Relays, but CPM 10.6 also supports client-updates from the "cloud", that is, directly from the Trend Micro ActiveUpdate server.
Note that Trend Micro does not recommend updating clients from the cloud as the default behavior.
Pattern files may exceed 20MB/client, so frequent, direct client downloads from the AU server are usually not preferred. Instead, you can use the cloud as a fallback for clients to use whenever they are not able to connect to the server. Updates from the cloud support incremental pattern updates, however, it does not allow you to update only certain pattern types.