yes and no. the discovery conditions will determine if the template applies to the target, if it applies at one time, then the target fails the check during a later discovery, the component is marked as invalid. if you are using a smart group as the target of the job you are possibly flying blind here as you can't check stuff like "fix exists" in a smart group query.
imo you should always use the discovery conditions - maybe you give someone read and then make another discovery job and point at random servers. if there are no discovery conditions they will get components on servers that probably shouldn't have them.
Thanks for the explanation Bill- so is it worth using a combination of both smart groups and discovery filters when targeting or just target all servers and let the discovery filters do the sorting?
It depends what you are doing. if you don’t really know what is out there and you are really ‘discovering’ then you target ‘all servers’ and let the discovery conditions do their work. if you know of know, like this template only applies to the windows boxes or rhel 5 boxes, I would still put the discovery conditions in the template, but then you could just run the job against a smart group of just the rhel 5 or whatever targets. depending on the check that may take less time that targeting all your systems.