So you set the analysis to only be relevant on computers that have the file that is going to be read by the analysis so if it has never been done, 0 computers will be relevant.
You create the property that returns the result you desire, but set the period to once every 30 days… it doesn’t matter what you set it to.
You run the task, output the file the analysis is going to read, the analysis becomes relevant and immediately processes the property right then and there on the client. This will give you the results fairly quickly. Putting “notify client ForceRefresh” in the actionscript might have it work a bit faster.
It would still probably be faster to use something like cURL on the endpoint to send the results back directly somewhere using a REST API, but I think the above option could be within 5 min or less if UDP notifications are working properly. The advantage of this approach is it does not require the client to have direct access to the thing it is sending the data back to.
The code I have here is an example of using a REST API to return results to a server: https://github.com/jgstew/remote-relevance/tree/master/python
It creates an action on the fly in BigFix that does relevance evaluation, gets the result, and sends it back using cURL.
I haven’t really put much polish on it, it isn’t very usable in its current state, but it is a fully working proof of concept for remote relevance.
Your need is not to send back relevance, but the result of a command, but the idea is very similar. ( I just realized my remote relevance project could also be used to run arbitrary commands and send the results back )
In my experience, this method took between 10 seconds and 2 minutes.