We upgraded to 220.127.116.11 a few months ago and ever since then we have seen something odd with the status of the endpoints when running jobs. Every task/fixlet we run initially shows all endpoints as being Not Relevant, but then it slowly changes to waiting/running/completed depending on the actual status of that endpoint. This happens regardless of what endpoints (out of about 5000) we are deploying to. The task could have no relevance at all or just something simple like Computer Name contains WORKSTATION and it will still default to Not Relevant. I can set a target of 500 endpoints and all 500 will show Not Relevant for upwards of 15-30 minutes, but this could be related to how often they check in.
Is this a known issue that there may be a patch for or does anyone have something I can check to get this fixed?