Problem
On some client machines, the inventory seen from the console level is almost empty. The issue comes from the presence of some incorrect registry keys in CustomFields. Usually, even if these keys have been authorized in "Configure > Inventory > unknown elements" they do not appear in "Configure > Inventory History / Custom Data > Registry > Landesk Custom Fields".
Cause
If your Core has just been migrated from an older version, those keys probably existed already in one of your older version of LANDESK, but did not cause such an inventory error. There may have been a problem during the schema update process during installation.
Workaround 1
If you do not need the blocking registry keys just delete those keys from the client registry. The inventory should then be displayed correctly.
Workaround 2
1. Rename the impacted key in the METAATTRIBUTES table of your database.
2. Restart the inventory service on your Core server.
3. Launch a complete inventory scan on the impacted client computers.
4. After that, the inventory display should not be blocked anymore
Example of exact problem replication steps
- Inventory of the impacted machine S1003FR1 seen from the console level => Inventory almost empty:
- Inventory history: the key, which is well present in the inventory of the machine does not appear in the history.
- Inventory of the same machine S1003FR1 seen in the web console => the key DAL-FLU-06 does not appear.
The table that contains the names of the variables used in the inventories: METAATTRIBUTES
- In the METAATTRIBUTES table, replace the impacted key DAL-FLU-06 by another one like for example DAL-FLU-X6
- Restart the inventory service.
- On the inventory display of your impacted workstation (let's say S1003FR1) that did not complete a full inventory scan yet, the inventory should be blocked now by the key "DAL-FLU-X6" just after renaming it in the database.
- Launch a complete inventory scan now on the impacted computer. After that it should not be blocked anymore by the key DAL-FLU-06:
- Launch a complete inventory scan on another impacted client machine - let's say S1082fr2FR2
- The inventory display of the S1082fr2FR2 should be correct now.
- The key DAL-FLU-06 should appear again in the "Unknown Elements"
- Let's authorize the key DAL-FLU-06.
- Restart again the inventory service.
- Relaunch a complete inventory scan on S1082FR2
- The inventory display of S1082fr2FR2 should be still correct, and the key DAL-FLU-06 should now appear in the "Custom Fields" in the console.
- Add another blocking key "FIL-BEA-01S" to the registry of the same client machine S1082FR2 (this key were blocking the inventory display of other client machines)
- Relaunched a complete inventory scan on S1082FR2
- The inventory of S1082FR2 should be now blocked again
Solution
1. Stop the inventory service on your Core server
2. Launch a DB Repair with a cleaning of corrupt or incorrectly positioned entries - more info at How to download the Database Repair Utility (DBRepair.exe). You should clean all the corrupted values as well as duplicate root "custom data" in your language as well as in English.
3. Launch a CoreDbUtil in order to update the schema and display name with the correct language - more info at Running CoreDbUtil to reset, rebuild, or update a database.
4. Restart the inventory service
5. Complete cleaning of unknown inventory items to start with a healthy database and revalidate it on a case-by-case basis after receiving each new inventory scan.
Requires Access To
Database Server Access is required to complete these steps.
Verification example
- When we tested the client machine S1082FR2 the inventory was no longer blocked, but the key FIL-BEA-01S did not appear.
- It was present, however, in the registry of this machine.
- When we started a synchronization inventory scan the key started to appear again in unknown elements.
- We authorized the key and relaunched an inventory scan. Then the key appeared correctly in the console without blocking the display anymore.
