I've got a device that is discovered every day, creating a new alert. It scans fine, all data is valid, but it keeps creating the alert as being a new device every day. I looked at this post: http://community.spiceworks.com/topic/33928

But this post seemed to imply that there were duplicates, which there are not. I deleted the item out of inventory anyway and it discovered it on the next scan, and continued the behavior like before.

The best way to handle this would be to add the serial number for the device into the device's BIOS.

Is it a custom built device?

In some cases when motherboards are replaced under warranty the new motherboard isn't properly setup with the machine's serial number. Depending on the BIOS it may be a very simple operation to open up BIOS setup during boot time and add the serial number.

If you can't add the serial number to BIOS there isn't a way to properly identify this device, so you'll want to exclude it (if the new device alerts are bothering you).

Since everything is scanning an all data is working fine with it, I'm hesitant to rebuild WMI, since I don't know the full extent to which services may be affected. Any other suggestions? Rebuilding the WMI would help more for if it was an unknown or unresolved, but since it's gathering all data, I'm not sure that WMI is the issue.

Sometimes devices report bogus serial numbers to Spiceworks. We try to keep a running list of these bogus serial numbers so we can ignore them automatically, but thats kind of like fighting cylons - theres always going to be more of them.

Actually, blank for both... I would assume that's the issue then. Is there anything I can do to resolve that without modifying the server? Otherwise, since the server is basically static and never changes, I guess I could just put an exception in there and make Spiceworks skip it in the future scans. I would like to leave it in the scan range to get alerts still, but I can live without it if I have to. I don't mind editing the database if that's required.

The best way to handle this would be to add the serial number for the device into the device's BIOS.

Is it a custom built device?

In some cases when motherboards are replaced under warranty the new motherboard isn't properly setup with the machine's serial number. Depending on the BIOS it may be a very simple operation to open up BIOS setup during boot time and add the serial number.

If you can't add the serial number to BIOS there isn't a way to properly identify this device, so you'll want to exclude it (if the new device alerts are bothering you).

The IP never changes, so an exception should be easy to add. I believe it was built by our VOIP provider, so it's totally possible that the serial number info was neglected or overlooked when it was built. I think I'll just write an exception for it going forward.

It's good to know though how Spiceworks tracks device with that info, if I run into that issue in the future, I'll know where to start.

Thanks for the help!

~R

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.