Bitdefender Integration instructions*
This article assumes you have an account for both Kaseya and Bitdefender-GravityZone. And you are familiar with the Bitdefender GravityZone interface and the VSA dashboard. For more information, reach out to Techs+Together.
PLEASE NOTE: If you have already configured Bitdefender Gravity Zone with your VSA account using a procedure method, please refer to the ADDENDUM for more information.
Install the Bitdefender Connector
When needed, you can install the same version of the Bitdefender Connector without uninstalling the existing one. This solution is recommended in case of issues with Kaseya Agent Procedures (they have been deleted or they do not appear anymore for some reason).
Kaseya VSA needs to access Gravity Zone services. To authorize access, you need to generate an API key and configure the integration.
Generate API Key
Figure 1 – Gravity Zone API key dialogue
Integrate Kaseya VSA with Gravity Zone
Figure 2 – Gravity Zone integration configuration
Synchronize Kaseya Inventory
The synchronization mirrors your managed inventory in VSA (Assets) to the Gravity Zone Control Center.
Inventory Synchronization Task
See figure 3
For more information, see the section Manual Synchronization.
The synchronization task runs hourly. This will automatically synchronize your existing Inventory according to its hierarchical structure, and it will deploy the security agent on your endpoints.
Setting a prefix will ensure that your organization names in Gravity Zone are unique. It is required that you use a prefix to avoid conflicts with other tenants.
It’s highly recommended to set these items to automatic synchronization for the most trouble-free implementation. If there are any issues, please contact firstname.lastname@example.org.
Figure 3 – Gravity Zone VSA Configuration
Deploy a Security Agent
After you integrate Kaseya VSA with Gravity Zone, a default agent installation package is created in Control Center. Bitdefender’s security agent for Windows is titled Bitdefender Endpoint Security Agent (BEST). It is recommended not to delete the package.
Create Package in Gravity Zone
Installation packages are visible in Control Center only for the user that created them. To view the default package:
See figure 4
You can see the default package named KASEYA_Connector_Default.
Click to edit.
Figure 4 – Bitdefender default endpoint package dialogue
If you would like to give your end-users the ability to pause or cancel scans, you will need to install the Power User module as well. The cancel a scan, you must enter Power User Mode from the System Tray icon.
Other information beyond the basic instructions.
In Settings > Configuration, you need to configure a prefix for creating or associating organizations from the source inventory (Kaseya VSA) and the destination inventory (Gravity Zone) during the synchronization task. The necessary for better management of the organizations within the network inventory. This is how you set a prefix in Kaseya VSA:
Example: the organization “Company” from Kaseya VSA with the prefix “[Acme]” becomes “[Acme] Company” in the Gravity Zone inventory.
Example: if there is an organization “Company” in Kaseya VSA and an organization “[Acme]Old Company” in Gravity Zone, at the same hierarchical level, an event of Missing prefix-based association found is generated. In this case, you can associate both organizations, rename the organization from Gravity Zone, or to ignore the event.
For details about events, refer to Event Handling Settings.
You cannot use the prefix for machine groups.
During the synchronization task, the differences between inventories generate certain events. Choose to handle these events either automatically or manually under the Event Handling Settings section.
The automatic actions taken on the synchronization events are described below:
Move an item in destination inventory (Gravity Zone) to match the source inventory location (Kaseya).
Copy an item from the source inventory (Gravity Zone) to the destination inventory (Kaseya).
Create a link between items that have the same name and location in both inventories.
Prefix-based Association Missing
Create the link between items with the same name and location in both inventories, considering the destination contains the prefix set in Prefix Settings.
Delete an item in destination inventory (Gravity Zone) if its corresponding item from the source inventory (Kaseya) no longer exists.
It’s recommended to set these items to automatic synchronization for the most trouble-free implementation. If there are any issues, please contact email@example.com.
Synchronizes your Kaseya VSA inventory structure with Gravity Zone Control Center. Choose this option to view and manage your inventory structure in Gravity Zone Control Center.
Excludes from synchronization the entity you have selected. An excluded entity will display this icon and it will not generate synchronization events. An excluded entity will disappear from the GravityZone inventory. To include back the entity for synchronization, right-click it and select Include for Inventory Synchronization.
Deploys the security agent across your inventory structure. Choose this option to deploy the security agent from Kaseya VSA.
Excludes from deployment the entity you have selected. An excluded entity will display this icon and it will not generate synchronization events. To include back the entity for installation, right-click it and select Include for agents synchronization.
Questions, problems and troubleshooting
For more information or problems with your integration and deployment, please contact firstname.lastname@example.org.
Refer to Figure 3
Already existing endpoints will not be affected. If they report to the correct company they will be left alone. If you run install on them the plug-in will detect that the BD client already runs on them and leave them as they are. A future release will bring more functionality on the endpoint management where it will pull more endpoint data from GZ and show it in the plug-in.
For those of you using the MSPAssist Module, Bitdefender, and struggling to stop the “Unknown AV” alerts on servers.
MSPA does not, by default, check for BD.
NOTE: DO NOT use this and expect to be notified if BD is missing from the machine. If there is any other AV installed that is supported in the MSPA scripts, it will check those AV’s to see if they are up to date, and if so, no alert occurs. It will not tell you BD is not installed.
Here’s the GravityZone Bitdefender Administrators Guide to give you all you need to setup your Bitdefender Modules and Policies. Enjoy!
There’s a quick setup you can use. The cool thing about it is it makes a great example of how the pieces of Kaseya work together.
NOTE: The following setup is only as accurate as the last Audit that was run on the system.
|Schedule to get response “quicker” than your Latest Audit schedule to create a new listing of devices.|
In this image you can see the schedule set that looks for the file on each device. EPAG.EXE is the End Point Agent for Bitdefender, and will be present after a successful installation.
Remember to Save and Apply your changes for the policy so that it will be able to be distributed. If the Policy you’ve set is already Assigned to a group or devices, please “Allow the Scheduler to apply” the changes over a distribution window.
You can take this a step further by creating a 2nd View to use in the “Manage Agents” view. This view would be for people who don’t create or apply policies, and thus shouldn’t be editing a view with a “Policy – xxxxx” name / prefix. This is totally up to you, of course.
Questions? Comments? Help? Contact us at email@example.com.
Problem: There are many machines showing as un-managed, but the Bitdefender interface on the machine shows you are protected.
This situation is usually seen when UAC is enabled at some level on the endpoint computer. In order to correct the situation,
Good news is, disabling UAC (and re-enabling it if necessary) can be accomplished with a VSA procedure. It’s recommended to create/use a procedure for UAC control separately. Do not write it into the BD deployment procedure.
UAC procedures found at Automation Exchange: https://automationexchange.kaseya.com/products/56
If you are purchasing Kaseya VSA through Techs+Together, you are also receiving Gravity Zone Bitdefender at no charge to you.
As a new customer, you will need to integrate your Bitdefender with VSA by following the instructions here: http://allthings.techstogether.com/2018/08/gravityzone-for-kaseya-r95.html
If you already have a Gravity Zone account, you will need to migrate it to Techs+Together by following these steps:
– Log into your existing GZ account.
– Click on your account name in the upper right corner
– Scroll down and Change your Bitdefender Partner ID to us.
If you are on the EU server: 57f5d106d71aeab820e38caa4324bb9f
If you are on the US server: a3e1b24f8330f85418363031e8f26b1d
Once this is complete, let us know so we can make sure the proper license is assigned to you
Your existing agents will slowly start obtaining the new license key as they check in.
Recently, we are receiving many reports from our tenants about them having issues with the Bitdefender VSA Integration.
Please be aware that due to an issue in the last VSA patch update, the Bitdefender module might display a blank screen. Kaseya is aware of the problem and working on a fix. In the meantime, to work around the issue, please access the VSA using one of the following URLs:
MyRMM – https://storedtech.myrmm.com
Also, please make sure you are using an up-to-date browser (preferably Chrome) and be sure to clean out your browser cache and cookies.
If you continue to have issues after following these steps, please do not hesitate to reach out to us at firstname.lastname@example.org
– Your T+T Team