If I understand correctly, when you install an agent on Windows 10 1803, they do not populate in LDMS 2016.3 inventory database?
A few questions?
Have you made sure you are downloading all patches from patch manager?
Have you tried rebuilding the agent configuration?
Is Upgrading the core an option?
If you do not get an answer here, you may want to try support.
A quick search shows that 2016.3 is fully supported but maybe that changes as Windows 10 releases more versions of it's OS.
Please review the following:
Yes, that's right ...
I'm not sure all the patches have been downloaded to the PC.
The agent was rebuilt.
It´s not possible to update a Core.
The patches downloaded to the Core?
odaza We are using the 2017 core, and don't seem to be seeing an issue with the data coming in, but what you might do is get the SCN file itself by using the commandline switch to output the SCN file to a local path.
Maybe create a folder on the PC, C:\Temp, then run LDISCN32.exe with the following:
LDISCN32.EXE /F /V /L- /O=c:\temp\%computername%.scn
Upload a copy of the SCN file to the LDSCAN folder. Make sure it doesn't then get processed into the error scan folder. You can also check the event logs to see if there is an error reported.
It could be something in the SCN file itself is getting thrown out, possibly data corruption or something unique to the device you are testing on. The event logs might also help indicate if its rejecting the SCN file on inserting the data into a specific table. The 2016 core database table sizes are smaller on some columns\tables than what you will find on the newer 2017/2018 versions, so you may find that you need to adjust your database tables if this is actually the root cause of the SCN files not getting imported.