Lansweeper I believe is well suited for any environment - its low cost and small footprint make it an easy addition to any organization, big or small, that is looking for an asset inventory solution that can either replace or supplement existing asset management systems. It may not be well suited for situations where a lot of customization is necessary, such as pulling in custom fields or details from equipment that don't reside in a registry.
This program works from the roots of the problem and creates a professional matrix for each of its users. This will give them more skills and resources to carry out tasks and reduce the difficulties of operating each of the processes of my work, as well as being An ally for the manipulation and operability of all your master data; Prometheus is very easy to recommend since it is a program that fulfills its mission.
Inventory - LANSweeper scans the network for devices - anything with an SNMP trap or using AD or local credentials. We can get an in-depth look at devices.
Reporting - LANSweeper can generate just about any report you can imagine. We can check RAM in groups and determine where upgrades are needed. We can find local printers (which aren't allowed on our network) and address that issue with the user. We can check CPU type to help determine end of life without our network.
Printers - It's nice to have a quick look at printer statuses. Toner levels, out of paper, and service errors are all reported via LANSweeper.
Can only scan what it sees. Doesn't show every item on the machine. Patches are also absent.
Software Recognition is OK with Microsoft. It is dire within our network of multiple products. Recognition is at about 35% with constant manual work needed to baseline for each manufacturer in each network
Datacenter compliance is a manual project. We used Excel extensively.
License optimization is limited to installations v surplus licenses. We need to know who's using what and how.
As I said earlier I have not encountered any major drawback just minor challenges like new users may find Prometheus a bit overwhelming with its different modules can bring confusion.
Also they can face issues with PromQL can be somehow complex while building an advanced dashboard.
It is usable and one can learn if few people in the team are already using it. It can be difficult to understand at the beginning because of non intuitive UI and syntax of the rules. So, I've gone for 7 points as there is some room for improvement in user interface and rules syntax.
Lots of info online there are tons of SQL Reports you can copy from the web as Lansweeper and users post many of them. They also send out alerts that pop up on Lansweeper, letting you know of an update that you need for certain software and provide an SQL report so you can scan your system to see what PCs need this update.
Microsoft System Center needs to install agents on all IT asset for discovery and sometimes the agents can easily get corrupted. Lansweeper is a SaaS solution and it's easier to deploy to all IT asset that are connected to the network. This save us a lot of deployment time without the need to engage vendor for professional service.
Highly customized pricing plans to choose from. Lower pricing for the same features compared to competitors. Easy to reach the support team, which provided detailed documentation and helped set up the Prometheus. Monitoring metrics gets very easy after the integration with Grafana. It also has a sophisticated alert setting mechanism to ensure we don't miss anything critical.
It had a positive impact on solutions expense cause several teams we're using different solutions with different costs that used several servers and DB resources. Now, we've been able to simply that a lot with Lansweeper.
With my previous point, people had to train and learn about each of their solutions. Now we can put a team in charge and so the other teams can focus on other tasks.
Last year Lansweeper changed their licencing prices a lot so it slashed our budget.
The ROI mentioned during the purchase has not been achieved, however this could be due to lack of data from our side. 2 years of implementation is too early to calculate and confirm the ROI.
