SolarWinds was the commercial tool that our teams disliked the most even though it is windows only, other commercial tools had a Linux version but we found them to be unstable and/or poorly implemented. So we bit the windows bullet and installed a windows server in our Linux …
We used ours mainly to test the wireless. Wireless could be several different things so the preconfigured tests on this device allowed us to quickly eliminate certain areas and allowed us to focus on the real problem. It’s easy enough a PC Technician could use it.
On its own, it's a solid choice for an SMB or Mid-size Enterprise if you're price sensitive and looking primarily for core functionality. SolarWinds has a large family of products that can also be leveraged in conjunction with SWNDM. Turning the product loose on a very large environment for discovery and mapping should be done with care and concern for a number of reasons but including the performance of the product for this task. If you're looking for an all-in-one product with some presumed supporting features built in (config manager, etc.) you'll need to look elsewhere.
We briefly tested a NetAlly LSPRNTR-300 LinkSprinter 300 Network Tester with WIFI and Distance to Cable Fault Indication and it was a worthy testing unit it but we quickly discovered that it did not offer the large range of testing in both the copper and fiber network drops, nor was it as complete with regard to wireless testing. But in it's defense it was not quite as pricy as the Fluke.
MS is meant for windows monitoring and up/down for mostly everything else. Moved away from MS System Center. Now we have better visibility and management can get reports. The other teams have added Linux to Solarwinds and also see improvements in monitoring. Whether you use snmp (v3), wmi or some other credentials to connect to you system, Solarwinds will more than likely be able to manage and monitor it.