This topic describes the necessary steps to deploy Citrix PVS with the Carbon Black Cloud Windows 3.7 sensor. Earlier sensor versions are not supported.

Procedure

  1. Put the vDisk into Private mode and access vDisk from the Designated Parent Device.
  2. Install or upgrade to the Windows 3.7 sensor.
  3. In the Carbon Black Cloud console, click Inventory>Endpoints or Inventory>Workloads.
  4. Select the endpoint, click Take Action, and then click Enable bypass. Confirm the action.
  5. Edit C:\ProgramData\CarbonBlack\DataFiles\cfg.ini and append the following statement. A separate script to re-register the agent is not required after specifying this parameter in the cfg.ini file. 
    AutoReRegisterForCitrix=true
    Note: If you are upgrading to the 3.7 sensor from a previous sensor version, add: HostNameAsOfLastReregister=<HOSTNAME>. Replace HOSTNAME with the hostname of the Designated Parent Device.
  6. Apply the new configuration by using the following RepCLI command. For more information about RepCLI, see Managing Sensors by using RepCLI in the User Guide. 
    RepCLI updateconfig
  7. In the Carbon Black Cloud console, click Inventory>Endpoints or Inventory>Workloads.
  8. Select the endpoint, click Take Action, and then click Disable bypass. Confirm the action.
  9. Shut down the Designated Parent Device.
  10. Put the vDisk into Shared mode.
  11. Start Citrix clone devices with vDisk in Shared mode.
  12. Verify that Citrix clone devices are visible in the Carbon Black Cloud console.
    Important: Do not use clone devices to access vDisk in Private mode. Always use vDisk in Private mode or Maintenance mode from the Designated Parent Device. Do not perform manual reregistration on the Parent Device.

    Remove any previous BAT scripts or other reregister mechanisms that you have set up. Leaving such mechanisms in place can cause sensors to reregister more than once.