There is a way to modify a filter to make it visible in the console, though WHERE it would then appear is another matter.
If you remember the Query you ran to find the row in ITEM and the STATE column you copied out, well, that same row also has Attributes, set to 23 on my results.
However, it's not supported. In short, you have to directly modify the SQL in the table to change the value of that to probably 22.
The Attributes column is a combination column in essentially hex. 1 = hidden, 2 = no modify, 4 =, 8=, 16=...
23 therefore is a combination of 16, 4, 2, 1. The 1 is the culprit, so remove it, you get 22, and in theory it'd be visible in the console.
The problem becomes finding it. IF it's in the default location, no problem, right? But remember, it's hidden, so WHERE it is didn't matter to the developers. It doesn't have to be completely organized. So if it's not where you expect it, finding it is tricky, but possible. For instance, using the GUID for the PCA filter we found in the previous post, I built the following SQL:
Select i.name, i2.name [parent folder]
from item i
join itemfolder ifo on ifo.itemguid = i.guid
join item i2 on i2.guid = ifo.parentfolderguid
where i.name like 'windows computers with no pcanywhere%'
and i.description like '%filter%'
Conceptually, this is how you find anything in the console. This approximates how the tree is built. And, it turns out from the results of this, that the filter would be approximately where we would expect.
Have fun!