Volume Re-discovery Process in Solarwind

We have this option in Threshold and Polling setting, and I configured this with solarwinds support, but don't works

AUTOMATICALLY REMOVE UNKNOWN VOLUMES Set this value if you want to enable the automatic removal of 'unknown' volumes.
REMOVE UNKNOWN VOLUMES AFTER
2
days Remove volumes which have no statistical data and have been 'unknown' for longer than configured days.

Yes, please, I have the same issue

one more thought, don't save your passwords in the script if you can help it:

     Secure Credentials with Self-Signed Certificates for PowerShell Scripts | Ask Premier Field Engineering (PFE) Platform…

It used to be all scripted, but discovery got better, so now I do a few things.

Windows "stuff" is 99.9% on a domain. We simply rediscover Server OS objects in AD, and we have rules to bring them in. By putting stuff from certain OU's on specific pollers I don't need any scripting, just server reoccurring discoveries that I make sure are under 1000 discovered items.

Linux/AIX in our environment I do script via powershell, though we have many fewer we actaully have more disk changes so I can't ignore them. Script below just pulls the IPs and which polling engine.

Add-PSSnapin SwisSnapin

$swis = Connect-Swis "<yourserver>" -UserName <User> -Password <PW>

$query = '"SELECT N.EngineID, N.IP FROM Orion.Nodes N where N.IsServer = 1 and (n.MachineType like 'IBM PowerPC' or n.MachineType like 'net-snmp - Linux')"

$results = Get-SwisData $swis $query

$results | OGV

If you want to get fancy, use the sample discovery script: OrionSDK/DiscoverSnmpV3Node.ps1 at master · solarwinds/OrionSDK · GitHub  and pass the IPs directly into a discovery task. I don't want to pretend I did anything fancy, I basically used the sample script. I don't have a profile to automatically add disks and interfaces here, a human just reviews the discovery results on a regular basis importing good stuff and ignoring items we will never want.

And it doesn't directly apply to the disk concern above, but Network gear interfaces we most do by hand as things change, but you need to make sure nothing gets missed, so we run a similar query and use a slightly different sample script: OrionSDK/NPM.DiscoverAndAddInterfacesOnNode.ps1 at master · solarwinds/OrionSDK · GitHub

I like adding the interfaces in the second sample better, and thought about trying to treat volumes in a similar way, but I haven't given it a shot yet. I did note that the copy nodes script might have some clues the next time I am looking to dive into it (OrionSDK/CopyNodes.ps1 at master · solarwinds/OrionSDK · GitHub )

how do you generate your list of existing nodes? are you doing this through the gui or through something like python or powershell?