Roll out Bitdefender agent
How the action installs a missing Bitdefender agent on Windows devices, which setting it has and when the step fails.
Use this action to make sure the Bitdefender agent (Bitdefender Endpoint Security Tools) is installed on a Windows device. If it is missing, octoja installs it from the GravityZone installation package of the company matched to the device's customer. The device must be online.
Prerequisites
- Bitdefender is connected under Integrations, and the device's customer is matched to a GravityZone company — see Set up the Bitdefender integration.
- The matched company has an endpoint agent installation package for Windows in GravityZone.
- The device can download the installation package from Bitdefender over HTTPS.
Configuration fields
If Bitdefender is not connected, the properties panel shows Bitdefender is not connected. Connect it under Integrations first.
Platform support
Outputs
If the step fails before it reaches the device, for example because octoja finds no suitable package, there are no outputs. You'll find the installer's progress messages in the step's standard and error output in Run history.
Result behaviour
octoja checks the integration, the customer match and the installation package on every run, before the step reaches the device. So these checks can fail even when the Bitdefender agent is already installed.
The agent counts as installed as soon as one of the services EPSecurityService, EPProtectedService, EPIntegrationService or EPUpdateService exists, even if it is stopped. The step never restarts the device itself.
You can safely run the step again: if the agent is already there, octoja just reports it and installs nothing. The step does not check whether protection actually works afterwards. For that, also assign the Bitdefender Protection check.
See also: Create an automation · Set up the Bitdefender integration
Was this helpful?
More in Actions
Send notificationAsk userDisable user accountDeploy browser extensionsStill need help? Ask the team