We opted for the full SQL Server install since there was a license available and also to avoid having to migrate the database later if it grew too big. Otherwise, a full-blown SQL Server installation will be needed as shown in this table: For example, if your database size will be under 10GB, you can safely go with SQL LocalDB which is bundled together with the Lansweeper install. In addition to the Lansweeper main install, you mainly pick component options based on the size and complexity of your environment. The requirements for running Lansweeper are straightforward enough. Lansweeper’s functionality can be extended to scanning assets in such environments as AWS, Azure, Intune and others. No more manually updating spreadsheets!Īnd scanning is not limited to on-premise devices only. Subsequent automatic scans keep the assets updated and add any newly discovered devices to the existing database. Here’s a short clip showing the discovery process and the type of data you will be able to see for each scanned asset:
#Lansweeper installation software
All this information then becomes available for analysis and reporting for IT folks like myself to get a solid grasp on the hardware and software in production and which users have it. Lansweeper then automatically creates a database from the scan results, providing a single source for inventory of devices, software and users. The list of all the device types and operating systems is quite extensive and can be found here.
This includes pretty much any device such as Windows, MacOS, iOS, Linux, Android, network hardware, etc. Lansweeper is an IT asset management solution that allows you to scan your network without installing any agents to discover various devices that may be running on it. I won’t go through the laundry list of other tools we have tried along the way and will come straight to the point of getting into the meat of our current solution – Lansweeper, which has met the above requirements while also providing additional functionality that I will get to later in this post.
#Lansweeper installation manual
Initial seeding of the database would involve minimal (preferably none) manual inputĮxtensive and easily customizable reporting The inventory tool had to be centralized and web-based So considering all of the above as requirements for managing our IT assets, here are some additional criteria (features) I wanted to have: And wouldn’t you know it, sometimes we wanted to run reports to get an idea of who was using what and where. Also, I was not the only one needing access to inventory information and other people needed to make updates to the existing data. Of course, as time went on and the organization kept growing in size, this inventory model would not be sustainable going forward. So a spreadsheet worked out for awhile even though it involved updating the data manually.Īgain, this only worked out for awhile because there was not a lot of equipment to keep track of and changes were not very frequent. I could literally go around visiting each cubicle and make a note of the hardware.
When I started managing IT equipment (laptops, monitors, printers, etc.) where I currently work, there was no system in place as the organization was pretty small at the time. In this post I am going to be reviewing Lansweeper asset discovery that I find very helpful to keep track of IT assets, so I thought I would share it with you. I have written about system management and administration tools that I have come across and am currently using, outlining both their strengths and weaknesses.