Update Sensors on Endpoints by using Group Policy

If you deploy sensors by using Group Policy, you must remove the existing sensor from the current Group Policy before you can perform a sensor update using Group Policy, the Carbon Black Cloud console, SCCM, manual updates, etc.

Procedure

• ♦ Use one of the following procedures to remove a sensor from a Group Policy or update sensors using Group Policy?
  • To remove the existing sensor from Group Policy
    1. Click Start > Administrative Tools > Group Policy Management and select the Group Policy Object (GPO).
    2. Click Computer Configuration > Policies > Software Settings > Software Installation.
    3. Right-click the CB Defense Sensor package and click All Tasks > Remove...
    4. Select Allow users to continue to use the software but prevent new installations and click OK.

    Note: The previous procedure removes the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\{Cb Defense GUID} registry key without uninstalling the current version of the sensor. To confirm that the registry key is removed, open Regedit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt. Search for "CB Defense", "PSC Sensor", or "Carbon Black Cloud". If no results are found, the key is removed.

    Note: If you are updating from Windows sensor version 3.2.x.x, read GPO upgrade fails on sensor version 3.2.x.x.
  • To update sensors by using Group Policy
    1. Follow the preceding procedure to remove the sensor from its existing Group Policy.
    2. Force a Group Policy update on all endpoints.
    3. Use the following instructions to update the sensors: To Install Sensors by using Group Policy.