Overview
You have a configuration migration issue and need help with missing database or custom attributes not showing up in the new server after you imported configs and scanning profile from the old server.
Solution
If the LanGuard scan results database (default name LNSSScanResults12) is missing, or the new server is not connected to the original database (or its copy) from the old server, it means that one of the steps for correct migration was skipped or failed.
This SQL backend database contains most of the configuration information, including custom attributes, agent/computer/group details and settings. Migrating the database is the only way to transfer these settings to the new LanGuard server.
To resolve the issue, move the existing database to the new server (make sure the new SQL Server version is the same or newer). Ensure that the rest of the migration steps were performed too, as they cover the transfer of all the required settings, including Scanning Profiles.