Description
Within LDMS 2016.3 SU4 and EPM 2017.1 there have been improvements made with the way Device ID communication is logged on the core server. This newly logged information is useful in tracking down issues related to the Device ID assignment and restoration process.
Resolution
In order to enable the logging please follow the process outlined below:
1. On the core server navigate to Configure > Services and select the 'Inventory' tab.
2. Click on the 'Advanced Settings' button and within the new window navigate to the 'Use Rolling Log' option. Alter the value from a '0' to a '1', click 'Set' and apply the changes.
Note: As seen in the example graphic below, this will result in a restart of the Landesk Inventory Service.
3. Enabling rolling logs allows the Device ID actions to be logged in two places:
- On the core server within the LDINv32.exexxxx.log in the C:\Program Files\LANDesk\ManagementSuite\log directory
- On the client device within the changeslog.xml located in the C:\Program Files (x86)\LANDesk\LDClient\Data
Below are examples of data that will be collected within each log:
LDInv32.exexxxx.log - 09/01/2017 06:36:29: 0x2340: Removing this computer from the restore device ID map
06/01/2017 06:36:29: 0x2340: Device ID '{DE5EB4CC-D7E2-7749-B666-81F950A68834}' has been successfully restored to '{0367DB89-F2E1-4749-BA07-C2C4AA061234}'
ChangesLog.xml - <change timestamp="2017-09-01T07:36:25-7:00" bnf="Device ID" oldvalue="{DE5EB4CC-D7E2-7749-B666-81F950A68834}" newvalue="{0367DB89-F2E1-4749-BA07-C2C4AA061234}"/>
This information will be helpful in determining where the issue is occurring with the Device ID assignment or restoration process.
Note: Please remember to disable the 'Rolling Logs' option once troubleshooting has been completed to avoid unnecessarily filling up drive space on the core server.
Additional Information
How Restore old Device IDs works
About: "Devices" and "Duplicate ID's" option for Inventory, and how they work