Can GROUP_NAME be used for unattended install to assign Policy?

Products

• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
• Carbon Black Cloud Enterprise EDR

Issue/Introduction

Can the parameter GROUP_NAME be set in an unattended install to assign Policy?

Environment

• Carbon Black Cloud Console: All Versions
  • Audit and Remediation (CB LiveOps)
  • Managed Detection (CB ThreatSight)
  • Endpoint Standard (CB Defense)
  • Endpoint Advanced (CB Defense + CB LiveOps)
  • Endpoint Enterprise (CB Defense + CB LiveOps + CB ThreatHunter)
• CB Cloud Sensor: 3.0.X.X and Higher
• Microsoft Windows: All Supported Versions
• Virtual Desktop Infrastructure (VDI) Environment

Resolution

• To manually assign sensors to a policy (Not using sensor or asset groups to group sensors by policy) this parameter may be used.
• To automatically assign sensors to a specific policy (Using sensor or asset groups to group sensors by policy) this parameter should not be used.
• Setting this parameter will cause the sensor to register as "manually assigned", causing auto-assignment to fail.

Additional Information

• GROUP_NAME=value in an unattended sensor installation is not related to sensor groups, rather an optional policy name assignment. This will manually assign a sensor to a policy, not a group.  If the sensor is manually assigned to a policy, it is impossible to assign it a group.
• It is recommended to have specific policy configured for non-persistent VDI devices.
• Assigning VDIs to a group is not required, but can be useful for sorting the endpoints page.