Issue: Duplicate Device IDs overwriting Inventory records in Endpoint Manager

Version 4

    Verified Product Versions

    Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x

    Overview

     

    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.

     

    Determining if this is caused by imaging with an EPM agent installed

     

    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

     

    %LDMS_HOME%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 =************

     

    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

     

    1. Run eventvwr.msc
    2. Expand Windows Logs
    3. Click Application
    4. You can filter or sort by Source (this may take a few minutes)

     

     

    Resolution

     

    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

    3. 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 content

    4. Delete C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)
    5. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer". Without this step, you may encounter an error stating "LDISCN32: The inventory server [CORE] did not respond"
    6. 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 before running step 5, it will likely fail anyways until it can properly sync up with the right inventory information