I don’t understand why I can’t change the IP address of a piece of inventory that has been scanned by Spiceworks. I have some equipment that was in a remote office connected via MPLS scanned into Spiceworks and since then that office has closed and those machines distributed to my main office. So, they have a different IP addressing scheme than what is on the local network there. I tried and tried but Spiceworks won’t find them and update. Am I missing something?
5 Spice ups
I would recommend that you jut delete the asset and then let Spiceworks re-scan it.
That doesn’t work because there is already another computer with that IP address in the database.
no, this hasn’t been resolved…based on what I’ve read here it probably won’t be.
ovitale
(Olivit)
7
Deleting an asset just to change the IP address is not acceptable as the details and custom fields values are lost!
Is there another option to change the IP address?
This is a really old (and BIG) issue never solved by SW team.
Thanks
4 Spice ups
Indeed, I have tickets tied to some of these inventory items and many of them are remote users that I set the device on the local network and scanned it then sent it out. So there is no way I can scan it again unless I have them send it back to me which isn’t going to happen.
I think this is a big problem for sure. I feel like I’m losing control of my inventory since upgrading to version 7. I now have several devices operating “manual” management with no way to go back to auto management. Also, when I scan a single IP address, I see several devices listed on the scan screen for that one address. They don’t get scanned properly.
1 Spice up
If you go into your Scan IP Range configuration and exception out (temporarily) the scanning of the device that already has the IP address per the Spiceworks database, then scan again for your target device, you may be able to pickup your target device.
1 Spice up
