Additional considerations
To ensure that no problems occur while working with coexisting servers, review the following considerations and apply them to your environment.
Software catalogs
To ensure that software on your computers is discovered based on the same software signatures, upload the same software catalogs to both servers. You can then disable the catalog delivery on one of them to avoid overwriting. The remaining server will deliver the catalog to all computers, regardless of the server that they report to, because the computers are in the same Fixlet site.
UPDATE DBO.SYSTEM_GLOBALS SET VALUE = '--- false
' WHERE NAME='catalog_download_actions_enabled';
Use the same database software for both servers, either DB2 or SQL Server. Signatures are different between these two types, and one software catalog might cause problems with discovery.
VM managers
You can use the user interface to add VM managers only for one of the servers, namely the one that has the BigFix server assigned to it. This is because VM managers added in the user interface must be managed by the VM Manager Tool that is installed on the BigFix server. For the other server, you can use advanced VM management, in which you install additional tools on any computer.
Changing assignments
- In the BigFix console, click Computers.
- Right-click a single computer, and then click Edit Computer Settings.
- Select the Instance setting, click Edit, and specify a new value.
Missing scan results
- In the BigFix console, stop all actions that are running on the problematic endpoints.
- Open the Fixlet site.
- From Fixlets and Tasks, select Uninstall Scanner, and click Take Action.
- Select all problematic computers, and click OK. Wait until the action is complete.
- Reinstall the scanner and rerun the scans. For more information, see: Setting up scans.