We have a lot of machine in this range and are trying to use Spiceworks to speed up software auditing. Most machines use the same root / administrator passwords, but approximately 40% don't. They are inteleaved so much that we don't want to create rules for each of them by hand if possible.

I have an example machine on this network that has a different SSH root password, so because SpiceWorks can't login the device is unknown.

So I go to the Inventory->Unknown and select the machine "cvg-1". I see the message:

"There was an SSH authentication error when attempting to connect to this device."

I hit "save" and it says "This device has been fixed". Spice works then checks to see if this new account may fix some other unknown machines.

After it has finished I have 4 new lines in my Network Scan settings at the bottom of the list. It also says "Items lower on the list take precedence over items higher on the list. " which is good as these exceptions are at the bottom and should be used instead of the more generic rule for the network range.

However, these 4 machines are still classified as unknowns and when I go back and check why, I still have the message "There was an SSH authentication error when attempting to connect to this device.". As if nothing has changed.

I've tried this so many times and even asked an IT colleague to try, but we always get the same result. i.e. fixed, but then it's not.