Sorry if there has already been something posted on this. I did a couple of searches and didn't find anything.
Ultimately, I'm looking to scope some EA's. Found this and voted it up.
I also voted up the feature request to bring back the recon verbs
In the mean time, if I create an EA with the Data Type as a String and the Input Type as Text Input, is there a way to populate that field with a separate script? Then you could scope the policy as need, essentially scoping an EA in a round about way.
I haven't touched the API yet but was thinking with the API this could be possible. Any thoughts?
Why not simply populate the EA using a script directly ?
Rather then using this "double method" ?
After all if you are going to source from a script to begin with, I see no point in introducing an intermediate stage..
- Just directly populate the EA from a script.
Yes you do have to run this on all computers, but the script could start with some condition that creates a shortcut exit on those machines that it's not to apply to.
Currently there is no way to scope EA's, and no 'contrived' way that I can think of.
The best method I can come up with for now is the "short-cut exit"
If necessary, if the conditions are really complex, then you could simplify by creating another script to set a client-side flag, and then test for that as the short-cut exit condition for the EA.
That would make the EA a very light-weight process, that could easily be run on all clients, with minimal impact.
So I think that would be the way to go.
I have started using this. It allows for populating EAs.
You will need to package the logging file and deploy it before the script runs. But its works great!