Friday
We've been doing IP Range scanning for the past 2 months to get a general overview of the non-domain-joined assets on the network throughout the organization. This has helped us tremendously in terms of visibility and potential security holes.
We've just now decided, after the Fall Release, to begin deploying the IT Agent to our domain PCs. This decision was based on several factors, one of which we have a growing number of laptops that are sometimes not seen on-network for several days at a time (including several that never are).
Since the deployment, we now have thousands of duplicate assets and manually "resolving" is not an option.
Far as I can discern, the only issue is with "Installation" and "Type". Installation being the Hybrid site and the Type being the detection method (IT and IT_Agent).
MAC, Serial, and Hostname are all identical. The only other exception is, the agent is returning more detailed data-- presumably because we have numerous interval scanned items disabled from the IP range scans.
I need some help on how to systematically resolve these duplicates and any configuration changes required to prevent this from recurring. It's worth noting, that for the time being I have disabled all IP Range scans.
Thank you.
Tuesday
Hello Lee-TG,
Reading your post, we assume you are currently seeing duplicates between your IT Agent installs and the assets that are discovered with your existing Classic or IT installation.
Unfortunately, this is still a known issue. In our latest launch, we introduced a new reconciliation engine that will prevent duplicates for IT Agent and Network Discovery installs. However, this does not take the assets from a Classic installation into consideration yet.
We are still working on expanding our reconciliation engine, which is currently scheduled to be released in the first half of next year.
Tuesday
Thank you for your response. Will on-prem AD scans work with the IT Agent as well?
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now