Limitations of Discovery for Windows

[Phill_Hardstaff]

Hi all, this really just to make a comment as I eventually found the answer to the question I was going to ask after quite a few hours searching. So, returning customer here, was excited to see I could run all the on prem parts on Linux (discovery). So I set this all up, set up the cloud part and all was well. But when I started to look at the results it wasn't  what I was expecting. The asset details of Windows devices did not all the usual detailed WMI stuff I was expecting despite having valid credentials etc. So, I started searching and didn't find much.

Nothing mentioned here Install Network Discovery - Lansweeper Community
Nothing mentioned on the comparison page Comparing Lansweeper Sites and Lansweeper On-premises
Nothing here Lansweeper Discovery - Lansweeper Community

On fact "Windows" is ticked there for all three options. So I bit more digging, and I found this Network Discovery: Frequently Asked Questions - Lansweeper

Why is my Network Discovery installed on Linux only reporting back recognition data but no detailed asset data for Windows assets?

Currently, Network Discovery on Linux can’t get the details yet from a Windows device due to access restrictions. If you do enable Windows Remote Management between the Windows asset and the Linux sensor, you might already get more information. See How to configure WINRM for HTTPS - Windows Client | Microsoft Learn on how to enable it on your Windows asset.

ah ha ! While not a big deal I was used to the results I was getting before so thought I was doing something wrong, would be good if this was mentioned more up front than only listed here. I really like the low overhead of the Discovery installs and can pretty much get away with a very low spec Debian 12 VM. And it just works ! 

So I ended up installing a scan server on Windows, linked to Cloud and then started to see the results I was looking for. Like I said, no big deal. I saw there is a work around but don't really want to go down that path for now.

I am however not quite following what is being said about not being able to sue "IP Locations" which I used a lot before, being referred to making a custom report filtered by IP seems a bit of overkill? It seems because I am not "on prem"? I cannot create IP Locations like I could before it seems. Kind of weird how I can click on Manage IP locations. then Add IP Location but "Save Changes" is always greyed out. 

All the best from Nauru, Central Pacific Ocean.

[MichaelArens]

Is the WinRM-requirement also needed when the sensor and hub are both on Windows-OS?
Please make a WinRM tutorial specific for LANsweeper and what best to configure.

[Phill_Hardstaff]

Hi Gilian, thanks for the reply, much appreciated. I reckon discovery is on the right track and I will give the WinRM bits a try. Was just that I had already done everything in AD for the old way to work. Anyways, so far so good, will stick with old scanning for now as I have that working and then move on to network discovery as I get it working as I would like subnet by subnet.

Phill

[Gilian · Accepted solution]

@Phill_Hardstaff 

Thank you so much for the detailed experience on using Network Discovery. It really means a lot to us!

We mention the following on Comparing Lansweeper Sites and Lansweeper On-premises:
"Remote discovery (Windows, Linux and macOS): On Linux, Windows discovery is limited to credential-free device recognition (CDR). Full data discovery (software, user info, etc.) is planned but not yet available and will require remote WinRM on Windows assets. 
Active Directory discovery is not supported on Linux sensors due to connectivity incompatibilities with domain controllers."
But you're right, this difference should be highlighted more. That's why I'll ask to update the comparing page and also have it mentioned in Install Network Discovery - Lansweeper Community.

We plan on offering a Linux container image having Network Discovery on board which is capable of doing remote Windows discovery with full details (would still require WinRM to be enabled though due to the default trust level Microsoft put in Windows for remote connecting parties). Estimated planning is begin H1 2026.

Using reports with IP address conditions is currently the only workaround we have for IP locations.
We still plan on offering "IP groups" natively within your cloud site, without the need to specify an installation, as they refer to your entire inventory, spanning across multiple installations.
According to current planning this should be feasible by the end of H1 2026.