Find-FalconHostName case sensitivity with error? about psfalcon HOT 6 CLOSED

Thank BK appreciate your support on this.

from psfalcon.

• How many hosts are in the CSV? The number of contained hosts doesn't match the number of errors in your screenshot.
• Were the contained hosts the same ones that generated warnings?

I won't move to enabling -Partial by default, either in the script or in the function because the likelihood that someone will accidentally perform an action on a host is way too high (having hostname abc affect hosts abc, abcd, abcde, etc. -- case is not the only thing affected by the partial match).

from psfalcon.

How many hosts are in the CSV? The number of contained hosts doesn't match the number of errors in your screenshot.

20 unique machines were in the CSV (there was some duplicates). 2 were no longer valid assets, so action was taken against 18.

Were the contained hosts the same ones that generated errors?

The host names in the errors are the same AIDs below.

I won't move to enabling -Partial by default,

Ah I see why that might cause a problem; however, there is a larger problem in that Find-FalconHostName is case sensitive. Not sure about others but a host name might be gathered in many ways other than the CS console, so there are situations in which hostName1 will never match against Hostname1 even though they are the same machine.

from psfalcon.

20 unique machines were in the CSV (there was some duplicates). 2 were no longer valid assets, so action was taken against 18.

Something doesn't line up there. There are 25 warnings. Are 7 from duplicates? If they are duplicates and they were found, it shouldn't be producing a warning and is likely due to a bug that I should find and fix.

Ah I see why that might cause a problem; however, there is a larger problem in that Find-FalconHostName is case sensitive.

It's not that Find-FalconHostname is case sensitive -- the APIs themselves are case sensitive. The command is passing the values (in groups of 20) to Get-FalconHost and either using -Filter "hostname:'value'" (partial match, not case sensitive) or -Filter "hostname:['value']" (exact match, case sensitive).

from psfalcon.

It's not that Find-FalconHostname is case sensitive -- the APIs themselves are case sensitive.

Well that is just unfortunate. Is there anyway to over come that other than having a strong naming convention or ensuring all names are capitalized in the console?

from psfalcon.

As far as I'm aware, no. I think the underlying data is stored case sensitive, and I don't see that changing.

from psfalcon.