This article addresses how to resolve a specific issue with inventory records being overwritten due to duplicate device IDs in your environment caused by a misconfigured image or an imaging process that was done without correctly following your internal imaging process. Most likely the LANDesk agent was added to the image or was installed to a machine out of order during a new build.
How to determine if you are having a duplicate device ID issue resulting from the imaging process already including a LANDesk agent
Unfortunately, some of this is going to be you, your admin, or other console users saying that devices are just missing or not displaying in the network view. Noticing this issue may be occurring requires more detective work than a distinct and clear error.
If you are seeing weird behaviors with a batch of similar machines disappearing/reappearing in Inventory, review your Core server ldscan folder
[COREPATH]\Program Files\LANDesk\ManagementSuite\ldscan\ErrorScan
When opening the various .scn files (.scn file extension is the OOTB default for EPM, your environment may be configured differently), you will be looking for the following information:
Device ID ={***************************************}
Device Name =***********
Network - TCPIP - Host Name =************.domain
If you see multiple files with matching device IDs but different device name/hostname then you probably have an issue with how the machine was imaged
The reason these items are showing up in ErrorScan is because the core doesn't recognize the information even though it thinks it already has a matching device ID. Prove this by looking at the LANDesk Inventory Server warnings in the Application section of Event Viewer on the core
Run eventvwr.msc
Expand Windows Logs
Click Application
You can filter or sort by Source (this may take a few minutes)
How to resolve duplicate device IDs overwriting inventory records caused by an image with the LANDesk agent
NOTE: As a user with Administrative privileges on the client device
1. STOP all LANDESK related services
2. Delete the following Registry Keys for 32bit clients:
HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
Delete the following Registry Keys for 64 bit clients:
HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
3. C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)
4. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer" (this is important to make the inventory scan work, otherwise it will fail and you will see the entry in Event Viewer)
Without this step, I was encountering an error stating "LDISCN32: The inventory server [CORE] did not respond"
5. Open command prompt and run C:\"Program Files (x86)"\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC
You do not have to wait for Security Scan to finish, it will probably fail anyways until it can properly sync up with the right inventory information
