Generic Serial Numbers
We have a few computers that have serial numbers like "To be filled by OEM" or "123456" etc. These cause problems with the Asset import because one Hardware Asset will be updated a number of times every night. Does anyone know of a good way to handle these computers so they either can have their own HA or just be skipped by the import?
Thanks!
James
Best Answer
-
Shane_White Cireson Support Super IT Monkey ✭✭✭✭✭
As far as I know, changing it will not create duplicates but will not edit any existing records. As long as the existing Windows Computers are related to any HWA, then the workflow won't create a second HWA for it.
This is how your settings should look.
I would advise testing this in a test/dev environment first if you have one. And please do DB backups before hand just in case the end result is not what you are looking for and then you will be able to revert back.
Let me know if this is helpful!
Thanks,
Shane
5
Answers
Hi @James_Johnson
Not sure I am following on these, so you have a few computer with missing serial numbers, do all your computers come in through Asset Import or do you use SCCM?
What do you currently have configured for your Asset Management hardware Asset settings?
Thanks,
Shane
Hi @Shane_White
Thanks for the response. We use SCCM and that's where most of our CI's come from. I was talking about the HA sync workflow not the manual asset import.
It's not that the computer's don't have serial numbers but they're generic and we have multiple machines with the same serial number for a couple different generic serial numbers.
Thanks,
James
Hi @James_Johnson
So you are looking of a way to generate serial numbers that are unique then right?
Or generate a unique hardware asset for each computer but keep the generic serial numbers?
Thanks,
Shane
Hi @Shane_White
Yes a way to create unique hardware assets with the generic serial numbers. Or even just skip them on the sync workflow and we can manually create/update those hardware assets.
Thanks,
James
Hi @James_Johnson
Can you confirm what you have for this setting currently?
Thanks,
Shane
@Shane_White
It's currently set to Serial Number
Hi @James_Johnson
That will be why, you will need to change this to something else. As you are currently saying the unique key on a hardware asset is the serial number, so if you have generic serial numbers this is not going to work.
I would recommend you changing this to Id (Guid) or another value from the drop down that is 100% going to be unique between each asset!
Does this make sense?
Thanks,
Shane
Hi @Shane_White
That does make sense but we would like to avoid doing that if possible. We have around 2500 hardware assets that do use the serial number and that's our preferred method of tracking unique assets. The problem we do have is just with 10 or so assets with the generic one.
If we did change it to GUID how would that affect the records we already have? and the Primary ID field would become the GUID and the alt serial number field would hold the system serial number?
Thank you,
James
Hi @James_Johnson
As far as I know, changing it will not create duplicates but will not edit any existing records. As long as the existing Windows Computers are related to any HWA, then the workflow won't create a second HWA for it.
This is how your settings should look.
I would advise testing this in a test/dev environment first if you have one. And please do DB backups before hand just in case the end result is not what you are looking for and then you will be able to revert back.
Let me know if this is helpful!
Thanks,
Shane