1. PDQ Deploy & Inventory Help Center
  2. Community
  3. Collection Library Requests - PDQ Inventory
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Filter incompatible OS versions from collections

Avatar
David Steeves

Right now, PDQInventory collections show every machine that has an older version of a given application. However, some OSes are not compatible with these newer versions. These OSes are filtered out in the PDQDeploy packages but because they're not in PDQInventory, if you create your deployment targets from PDQInventory they will have a higher number of failures because of the incompatible OSes being deployed to.

I'm asking if there can be an option to have a filter by incompatible OS in each of the collections so we're not deploying to more machines than necessary.

Examples of incompatible apps and OSes:

Adobe Flash for IE - Any OS above Win7/2008R2

Chrome - Any OS below Win7/2008R2

Firefox - Any OS below Win7/2008R2

And yes, I am ashamed that I still have XP, 2003, & 2008 machines in my environment.

0

Comments

2 comments
Date Votes
  • Avatar
    David Steeves
    (Edited )

    I guess an alternative would be to change the PDQDeploy packages so that "Conditions not met: No steps were able to run" would be considered a success and not a failure. I could probably do this myself, but it would be nice if the packages came that way.

    Unless I'm not thinking of a scenario where reporting these deployments as failures instead of successes would be more beneficial.

    0
  • Avatar
    Permanently deleted user
    1. Adding conditions to collections: We are not going to do that because it would hide machines that have old versions of the software that was still able to be installed on old OSs.
    2. Making it so all steps skipped is a success: I believe the reason it is currently a cause for failure is so that it grabs your attention and you can avoid deploying to that target in the future. In this case it would alert you that you should probably uninstall the application from those old machines since they can't be updated any more.

    If you would like to add your own filtering to the Collection Library you can create collections that point back to the Collection Library.

    0