Probably the most consistent would be hardware based, however, a change in motherboard would change that thought. I would use hardware based attributes - S/N , service tag, or if like the HP systems you have editable fields in the firmware. We put the computer name, purchase date, warranty etc... in these updatable hardware fields. LDMS Device id can change if the client is cleanly/totally uninstalled._____________________________________________________________Please consider voting for these ERs:Provide Better Pre/Post LDMS Patch/Sp/.0 Information To The CommunityCumlative Patch List for LANDesk ProductsQuery Builder ImportProvide bulk client deletions without carpal tunnel syndrome.Core Synchronization Allow Mirror functionality from Master Core
I've been using service tag but not all machines are dells and serial number are sketchy too on non-dell machines too.
I'm using it as a key import field into LANDesk Service Desk Configuration Manager so maybe I have to devise 2 separate import types. One for Dells and one for everything else
So that's 4 imports now. 2 for PCs and 2 for servers
Unfortunately there are no standards in the hardware arena. You could brand the registry but would have to do so after every reimage of the computer. This would offer you freedom to dump any identifier you want into the registry but procedurally you would have to put something in place. Standardizing on one hardware platform would also help.
1 of 1 people found this helpful
Your devices might also be detected as duplicate when serial number, name and/or mac adress change depending on your settings which will also generate a new LANDesk Device ID. If you have so many issues using data in the device it might be worthwhile to use something external, like a barcode sticker outside on the box that you can scan and use as Unique Identifier using DTS (ManagedPlanet/LANDesk Data Analytics)...
We as standardised as we can be really we have 8000 pcs and about 300 of those aren't Dell
I think that using the computer_Idn for the left overs is the best bet. Creating and new id when the PC is reinstalled\upgraded will be a small % of the 300
A slight aside: is the deviceid related to the computer_idn? i.e. if the scan decides a new database entry is in order will it generate a new deviceid and a new computer_idn? or if it reused a computer_idn would it reuse the deviceid as well?
Does that make sense?
Without SQL in front of me, computer_idn is linked to deviceid. If the device is deleted form LDMS all is lost. If it generates a new deviceid than I believe the computer_idn stays the same.
The deviceid i beleive is the guid for the computer record in the database
not the devicename
I guess the question is will wither of these attributes be reused on new entries?
The Computer_IDN should never be re-used as it is an automatically generated 'next in sequence' number. The only time it would change is if you start a new LANDesk database and that will start from 1 again.
Device IDs are not a unique database attribute although they are meant to be classed as unique. LANDesk will only accept one machine in the database with that ID in the DB, but the database does not mark this as a unique column. This can change easily for the same machine as it is created the first time the inventory scanner runs and if you rebuild the machine a new one could be generated. Machines generating the same IDs independently should not happen without there being a bug. Most duplicates are due to faulty imaging processes.
As has been said earlier, there is no 100% certain way to tag the machine through it's entire life. MAC address and serial number would be the closest attributes providing the motherboard does not get replaced. Serial number 'should' be the best but engineers are notoriously bad at adding the serial number back after performing a motherboard swap out.
LANDesk Silver ESP
The One-Stop Shop for LANDesk Enhancements