The installation process is straightforward and explained step by step in a knowledge article called ‘Installing and upgrading the Lansweeper Integration App’, that includes an easy-to-follow explainer video. The integration will also not create person records. Users of the assets can be related based on the Lansweeper Login ID, if this is known in 4me (registered either in the Support ID , Authentication ID , Employee ID , or Source ID field of the person record). To achieve this, the name of the software asset is compared to the Name of the software CI in 4me, or one of the names stated in the Alternative names field of the configuration item. Plus, if you use Spiceworks Inventory instead of PDQ Inventory, PDQ Deploy. We use it for about 400 PCs over 15 locations and it works great. PDQ is easy to use and is one of those software tools that (in most cases) just works. SCCM is going to be pretty expensive and probably overkill for you. Software CIs are not created by the integration, but a parent-child relation is created with the hardware CI it is linked to, just as it is in Lansweeper. For the number of PCs you have, PDQ all the way. For easy lookup, the System ID of the created CI record contains a direct link to the asset in Lansweeper. If that product does not exist yet, it is then created. When the integration creates a new hardware configuration item in 4me, it must be related to a product. From that moment on, administrators can decide to synchronize network assets only, i.e., assets that have an IP address. The first time the app is used after the initial install, all physical assets from the Lansweeper inventory are swiftly imported into 4me. Organizations that use 4me and Lansweeper can now easily integrate both platforms, by activating the 4me Lansweeper app in the ‘App Store’ section of the Settings console.
0 kommentar(er)
