Bitdefender VSA 9.5 - VSA X inventory migration
This topic describes how to adjust your inventory after migrating from Kaseya VSA 9.5 to Kaseya VSA X integration.
Topology
Partners that have migrated from the Bitdefender VSA 9.5 integration to the Bitdefender VSA X integration are able to perform a manual migration process to adjust the GravityZone new VSA X topology. Typically, a Bitdefender VSA 9.5 inventory has the following structure:
Kaseya VSA 9.5 organization is mapped as GravityZone partner company.
Kaseya VSA 9.5 sub-organization is mapped as GravityZone customer company.
Kaseya VSA 9.5 machine group is mapped as GravityZone group.
Bitdefender VSA X integration needs to be adjusted to support the new Kaseya VSA X topology change, which now consists only of organizations, sites and agent groups, not allowing for organizations to have sub-organizations like Kaseya VSA 9.5. Therefore, the GravityZone topology from the VSA 9.5 integration must be adjusted to the Bitdefender VSA X integration structure as follows:
Kaseya VSA X organization is mapped as GravityZone customer company
Kaseya VSA X site is mapped as GravityZone group
Kaseya VSA X agent group is mapped as GravityZone sub-group
Migration
Firstly, make sure that the Bitdefender Kaseya VSA 9.5 integration has been disabled or removed from your VSA 9.5 tenant. Then, perform the VSA X integration configuration as presented in our documentation.
Important
Under General > Configuration > Inventory synchronization, make sure the Synchronization level is set to Monitor and report synchronized inventory status
. This will make sure that the current VSA X Organizations are not automatically provisioned as GravityZone Companies without performing the migration steps first.
Under General > Configuration > Agent synchronization, set the Synchronization Level to Monitor and handle synchronized inventory status
and Synchronization Event Handling for Destination Moved to Automatic
. This will ensure that the GravityZone endpoints will be automatically moved to the right location inside GravityZone.
To adjust the topology, follow these steps:
Under Operations > Manage associations, please associate each Kaseya VSA X organization to their corresponding GravityZone partner company. This will ensure that top level structure (Kaseya organizations - GravityZone companies) are associated correctly.
Under Operations > Inventory, select the Kaseya VSA X organization associated at the previous step, and select Sync Inventory. This will ensure that the site group and machines groups are created in the corresponding GravityZone company. A Sync Inventory task will start and wait until it has finished.
Under Operations > Inventory, select the Kaseya VSA X organization from the previous step, and select Sync Agents. This action will check if the Bitdefender agent (BEST) is installed and if it is placed in the right location.
Already installed Bitdefender agents that do NOT correspond to the Kaseya VSA X location will generate a Destination Moved event, which will be handled automatically by the integration. After the Sync Agent task has finished, please check in GravityZone that the endpoints are in the right location.
Important
If any GravityZone policy assignment rules or specific policies are applied, please make sure that the corresponding GravityZone company has them in place. Only online endpoints can be moved inside the new corresponding location inside GravityZone.
Repeat the above steps for all Kaseya VSA X organizations that have already corresponding GravityZone companies.