When one dynamically targets “All Computers” with an Action within a Custom Site, the Action shows a count of all the computers on the system rather than only the computers currently subscribed to the Custom Site. Is this expected? It seems like only the computers that have been subscribed to the site should be able to even see the Action. Will the Action truly target all computers instead of all computers subscribed to the Custom Site? If so, how can I only target only the computers that have been subscribed to the Custom Site? Thanks.
If the Fixlet/Task being deployed is saved in the custom site then it is only available to the systems subscribed to the Custom Site. They will be the only systems that can execute the action even if you target “All Computers”. Remember that really means … “All Relevant Computers”.
If you actually look at the resulting .fxf file that is picked up by the workstations, it will automatically include a Relevance clause that will limit the action to systems that are members of the custom site.
1 Like
Thanks, Tim. Thanks what I thought, but my first attempt at running such an action showed thousands of computers reporting instead of the three computers that were subscribed. It only succeeded on the subscribed computers, with an Error (“Invalid site context. The Fixlet site may no longer exist.”) or “Not Relevant” for all the others, but I was surprised that it even evaluated on the other machines at all.
Did you do this as a Master Operator, or a normal operator?
If you did it as a Master Operator, try it again as a normal operator and see if that is different.
In general, it is best to do as little as possible as a Master Operator as it affects the actionsite which all clients are forced to process, which slows things down. Obviously some things can only be done as a Master Operator, and that is completely fine and not a problem.
1 Like