Client Deployment

The client deployment process consists of several procedures. To successfully deploy the CPM for Mac client:
  1. Identify ineligible endpoints.
  2. Identify conflicting products.
  3. Remove conflicting products.
  4. Deploy CPM for Mac clients.

Identify Ineligible Endpoints

The CPM for Mac client supports most operating systems and typically does not require system resources that exceed those required by the host operating system. However, some factors can preclude otherwise eligible endpoints from receiving the CPM for Mac client. Before installing the client use these procedures to identify which of your endpoints, if any, require modification. Do this before you remove any existing security products to ensure a continuation of your endpoint security.

  1. From the IBM BigFix Console, click Endpoint Protection on the lower left pane.
  2. From the upper left navigation pane, go to Core Protection Module > Troubleshooting.
  3. From the list on the right pane, select Core Protection Module - Ineligible for Install -Insufficient Hardware Resources. The Fixlet Description opens.
  4. Click the Applicable Computers tab. A list appears with the endpoints with insufficient hardware resources.
  5. Below Actions, click the hyperlink if you want to connect to the Support web page for more information.
  6. Repeat steps 1-3 for any Tasks that pertain to endpoint readiness (for example, Troubleshooting > Core Protection Module - Ineligible for Install - Insufficient Software Resources).

Identify Conflicting Products

Before you deploy the CPM for Mac client to your endpoints, uninstall any programs that conflict with the CPM for Mac functions. For more information see Conflicting or Incompatible Programs.

  1. From the BigFix Console, click Endpoint Protection on the lower left pane.
  2. From the upper left navigation pane, go to Core Protection Module > Troubleshooting.
  3. From the list on the right pane, select Core Protection Module - Ineligible for Install - Removal of Conflicting Products Required. The Fixlet Description opens.
  4. Click the Applicable Computers tab. A list of endpoints running conflicting software appears.
  5. Below Actions, click the hyperlink if you want to connect to the Support web page for more information.

Remove Conflicting Products

  1. From the BigFix Console, click Endpoint Protection on the lower left pane.
  2. From the upper left navigation pane, go to Core Protection Module > Deployment > Uninstall > [product name]. The Fixlet Description tab opens, showing a list of the endpoints currently running the program.
    Note: Alternatively, you can click All Content and then go to Fixlets and Tasks > All > By Site > Trend Micro Core Protection Module. In the list of Fixlets that appears in the right window pane, select Core Protection Module - Uninstall [product name] by double-clicking it.
  3. Below Actions, click the hyperlink to open the Take Action window.
  4. In the Target tab, a list of the endpoints that are running the selected program appears. Click Applicable Computers to choose all relevant computers. In addition, you might also want to configure other options:
    Execution
    Set the deployment time and retry behavior.
    Users
    This option works in combination with Target, which is linked by the AND operand (both conditions must be present for the installation to occur).
    Messages
    Configure these options to passively notify the user that the uninstall is going to occur, to obtain consent, or to ask users to stop using their computer while the installation occurs.
    Offer
    Configure these options if you want the user to be able to choose whether the program is removed. A message displays on the target endpoints (requires that the client is enabled for offers).

  5. Click OK.
  6. At the prompt, type your private key password and click OK.
  7. In the Action | Summary window that opens, monitor the "Status" and "Count" of the Action to confirm that it is "Running" and then "Completed".

Deploy CPM for Mac Clients to the Endpoints

Use the Core Protection Module for Mac Endpoint Deploy Task to deploy CPM for Mac to all computers that you want to secure against viruses and spyware. The CPM for Mac client package is about 40 MB, and each endpoint is directed to download the file from the BigFix Server or Relay.

If you target endpoints using properties rather than by computer (the recommended behavior), any endpoint that later joins the network will automatically receive the CPM for Mac client.

Installation takes about 10 minutes, and the CPM for Mac client can be installed with or without the target user's consent. Installation does not typically require a restart. In addition, the client will be briefly disconnected from the network.

Note: Before you deploy the CPM for Mac client, be sure that your targeted endpoints are not running a conflicting product (see Conflicting or Incompatible Programs) and that they meet the hardware and software requirements described in Client Installation and Updates.
  1. From the BigFix Console, click Endpoint Protection on the lower left pane.
  2. From the upper left navigation pane, go to Core Protection Module > Deployment > Install.
  3. Note the number of eligible clients in the parenthesis after Install.
  4. From the list on the right pane, select Core Protection Module for Mac - Endpoint Deploy. A screen displaying the Task Description tab appears.
  5. Below Actions, click the hyperlink to open the Take Action window. In the Target tab that opens, a list of eligible endpoints appears. The default behavior is to install the CPM for Mac client on every relevant endpoint, whether anyone is logged on, or present, or not.
  6. Use the following deployment options if you want to change the target:
    Target
    Click All computers with the property values selected in the tree list below and choose a property that includes all the computers that you want to deploy this Action to.
    Execution
    Set the deployment time and any retry behavior.
    Users
    This option works in combination with Target, which is linked by the AND operand (both conditions must be present for the installation to occur).
    Messages
    Configure these options to passively notify the user that the Action is going to occur, or to ask users to stop using their computer while the Action occurs.
    Offer
    Configure these options if you want the user to be able to choose whether the Action is completed. A message is displayed on the target endpoints (requires that the client is enabled for offers).

  7. At the prompt, type your private key password and click OK.
  8. In the Action | Summary window that opens, monitor the "Status" and "Count" of the Action to confirm that it is "Running" and then "Completed."