We came across this problem as well..
Just some thoughts we used to get around our problem.
In the pre deployment tasks when creating the deployment package you can tell the job to check for software, folders or reg entries and if it finds it to skip installation.
Or as naveen suggests add with out targets or add an exception list. But depending how big your environment is exceptions get cumbersome. We found having the deployment check for previous installs allowed us to keep a job around for a while and not have to worry about about it..
Or as naveen suggests add with out targets or add an exception list. But depending how big your environment is exceptions get cumbersome. We found having the deployment check for previous installs allowed us to keep a job around for a while and not have to worry about about it..
Another method we used was to use Dynamic groups to identify clients with out a piece of software and deploy to that dynamic group.
In that scenario i let the job run indefinitely and as the dynamic group identifies a new target my software is automatically deployed.
best of luck and hope that helped!!!