1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

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.

Conditions with Nested Packages

Avatar
Kathleen Firth

Hi,

We have a package for delprof2 that is set to not run if the PC is a member of a certain collection. This works as intended, until we nest that package. When nested, the condition is ignored. We have a new scenario in our environment where if that runs on certain PCs, it's very disastrous, so I'm trying to make this very difficult to deploy by accident.

Is there any way to make sure that condition is always obeyed, or am I going to have to include it at the step level of any master packages referencing it?

Delprof2 package Behaves as intended on PCs in the [redacted]OB collection

Package using it as a nested step Runs the Delprof2 package step without acknowledging the Collection Membership condition in the Delprof2 package.

0

Comments

3 comments
Date Votes
  • Avatar
    Webmaster

    Should the checkbox for "Use Nested Package Conditions" be checked?

    0
  • Avatar
    Colby Bouma

    Yes. https://documentation.pdq.com/PDQDeploy/17.1.0.0/nested-package-step.htm

    0
  • Avatar
    Kathleen Firth

    Thanks, I completely overlooked that box! I tested making a new package with a nested step, and that box is ticked by default, so good, that's exactly what I need it to do.

    0