I don't have an answer but here are some thinking points.
1. The values show up in inventory, this shows the inventory scanner is reading the registry entries so it is working as it is suppose to.
2. You change the registy entries and on reboot the registry entries you made aren't there. This suggests something running on the computer is constantly writing to these registry entries.
3.The Inventory has not reverted even with Full Sync Scan. Are you actually doing a Full sync scan? Manual right click on computer in console- Inventory scan- Full sync scan.
The inventory after a Full Sync Scan should show exactly what it read from the registry.
Run this on the computer ldiscn32.exe /o=C:\scaninfo.txt (You'll probably have to CD to the landesk\ldclient folder to run this)
This will put the finding of the inventory scan in a file call scaninfo.txt in C:\ (This does not send the results to the core.)
Look in there and see if the correct custom data is being picked up. If it is somehow its not being sent to the core during a normal Full ync scan.
Thanks for your response.
1) Yes, I would agree that the inventory scanner reported the values it saw the first time it read the new Custom Data fields I created.
2) Yes, I did run a FULL SYNC SCAN (right click | Inventory Scan | FULL SYNC SCAN). I've run this repeatedly.
3) I ran the file to a text file on my desktop. The file had "wrong" values. It contained the values I see in Inventory.
It appears that once established, the CUSTOM DATA fields are never updated again.
I'm replying to this old thread in hopes that someone might have seen this and know of a solution. We are running into the exact same issue here. We have a process we run periodically to change the common local account passwords on all of our endpoints. When we do this, we modify a registry value noting that the passwords were changed for that period. We have Custom Data set up to monitor this. The task runs properly and updates the registry value properly. However, it seems to take some time before the computer inventory in the LanDesk console recognizes the change. I'd like to say that it eventually does recognize it, although I can't say with 100% certainty, but it seems to take quite a bit of time on some computers and no number if inventory scans speeds it up. As the OP did, I have confirmed on multiple machines that the registry value was updated and have run full scans with output to a text file. While the registry is correct, the outputted text file still contains the incorrect value.
I feel this has been happening for a while with other Custom Data entries as the behavior has always been erratic. I haven't thought much of it though until now when I need to report the status of these updates to leadership and the numbers can't be trusted.
Any help is appreciated. Thanks in advance.