
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 03:04 PM
We have several assets we don't want to be scanned by lansweeper, that start with VDI.
I've tried excluding them by putting making a Windows Computer exclusion; VDI% and %VDI%, however they continue to be scanned.
Any suggestions?
I've tried excluding them by putting making a Windows Computer exclusion; VDI% and %VDI%, however they continue to be scanned.
Any suggestions?
Labels:
- Labels:
-
General Discussion
5 REPLIES 5

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 08:19 PM
if you go into the asset page for a windows one, you should 'asset excluded from scanning' in red or something at the top next to the computer name or similar... do you?
If you do, then it won't get scanned anymore, but, the asset will remain in Lansweeper. I deleted them from my assets after excluding them
If you do, then it won't get scanned anymore, but, the asset will remain in Lansweeper. I deleted them from my assets after excluding them

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 08:30 PM
JacobH wrote:
if you go into the asset page for a windows one, you should 'asset excluded from scanning' in red or something at the top next to the computer name or similar... do you?
If you do, then it won't get scanned anymore, but, the asset will remain in Lansweeper. I deleted them from my assets after excluding them
I've been deleting them every morning, or else we are out of compliance with our licensing and nothing scans. After setting up the exclusion and deleting them, they keep coming back. I was hoping I was missing something.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 04:19 PM
are they scanned as a windows asset, or a 'vmware guest' asset?
if it's a vmware guest asset, you'll have to disable scanning of the ESX hosts, unfortunately.
I have this same issue - there's another thread on here about it... i think they are working on a better fix.
if it's a vmware guest asset, you'll have to disable scanning of the ESX hosts, unfortunately.
I have this same issue - there's another thread on here about it... i think they are working on a better fix.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 08:15 PM
JacobH wrote:
are they scanned as a windows asset, or a 'vmware guest' asset?
if it's a vmware guest asset, you'll have to disable scanning of the ESX hosts, unfortunately.
I have this same issue - there's another thread on here about it... i think they are working on a better fix.
Actually after looking again, most are asset type Windows, only some were VMware guest.... so still not sure.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2019 09:17 PM
skuzzi wrote:JacobH wrote:
are they scanned as a windows asset, or a 'vmware guest' asset?
if it's a vmware guest asset, you'll have to disable scanning of the ESX hosts, unfortunately.
I have this same issue - there's another thread on here about it... i think they are working on a better fix.
Actually after looking again, most are asset type Windows, only some were VMware guest.... so still not sure.
Is there a way to disable scanning certain ESX host and not all of them?
