Assume the Falcon Sensor was installed on a Virtual Machine template using the installation parameter NO_START=1. Afterward, the Virtual Machine template is rebooted. What is the effect on the Falcon Sensor after reboot?
Assume the Falcon Sensor was installed on a Virtual Machine template using the installation parameter NO_START=1. Afterward, the Virtual Machine template is rebooted. What is the effect on the Falcon Sensor after reboot?
The NO_START=1 parameter is typically used to prevent the Falcon Sensor from starting automatically. This can be useful in situations where the sensor is installed on a Virtual Machine template, ensuring that it does not start and generate an Agent ID before the template is converted to individual VMs. Given that the parameter NO_START=1 was used, after rebooting the Virtual Machine template, the Falcon Sensor would not automatically start. It would require manual intervention to start the Falcon Sensor. This prevents the creation of multiple VMs with the same Agent ID from the template.
D is correct, If you restart the VM template before you convert the VM to a VM template image, host created with that template will all share an AID.
D is correct
D is correct. NO_STAR option is for VM template. It generate Agent ID after reboot.