In our scenario, our BigFix Inventory instance is in some other network and we want to connect our BigFix Server instance as an additional data source in BigFix Inventory.
So, to be clear: on the local network I am setting up here, we do not have an instance of BigFix Inventory running.
Is this the reason why we do not see the “Install Additional VM Manager Tool” option in the fixlets list?
If so, how can I fix this?
I cannot install the VM Manager Tool via the console of the BigFix Inventory servers, since there is no direct connection. I was looking to have a distributed VM Management, as described in the documentation as Scenario 1: Deployment scenarios
The VM Manager Tool and other BigFix Inventory tasks are part of the BigFix Inventory v10 Site. Is the BigFix Inventory v10 Site activated and clients subscribed to the site?
The BigFix Inventory is running a seperate instance on a different network. It has relays and clients connected to it (from our colleagues at this site)
Our BigFix platform is only the root server and the relays, and it should be connected by adding it as a “Data Soruce” in BigFix Inventory.
Our clients and relays are connected to our BigFix platform, but not to BigFix Inventory.
Yes, the architecture you describe is valid, but the Tasks you seek are part of the BigFix Inventory v10 content site. You’ll need your local BES Deployment to subscribe to the site in order to find the tasks, or have the central BES Server export copies of the tasks and import them to one of your own custom sites.
A direct connection between those two environments will not be possible - so we will not be able to subscribe to the site of the BigFix Inventory instance.
Our instance is completely separated except for the possibilty to be added as Data Source, and we are using the airgap tool for our environment.
If I understand you correctly, the way to go would be to export the task from BigFix Inventory via console, and import it to our BigFix platform via console.
