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.

Deploy install latest software on static package?

Avatar
Pat Furrie

We setup new computers for users by using PDQ Deploy.  I have a package which has many nested packages, one for each application we want for a given department.  I'd like for PDQ auto-updated packages to be included, so the first version of a given app can be the latest.  But I can't point a nested package task to an variable, like those used in PDQ Inventory, which maintain the most current version of a given app.

 

For instance:

  1. Make a baseline software package, which has a couple dozen apps, each configured with their own packages (some are auto-update packages from PDQ).
  2. One package, say 7-Zip, is pointed to a specific PDQ auto-updating package...
  3. BUT... next week PDQ updates the 7-Zip package.  Now the master package which nests that 7-Zip package will not be pointing to the correct item.  I'll have to manually edit the master package to point to the new version of 7-Zip (and any other updated packages).

No fun!

 

Ideally, the variables kept in PDQ Inventory would be accessible in PDQ Deploy.  We could point to the variable which represents the most current 7-Zip package that has been downloaded.  That way, the master package never has to be edited for this.  It will always deploy the latest fresh-baked PDQ goodness, even if that package is a nested package.  Anything less is like using... hosts files.

 

Maybe there is a current solution.  If so, I'm not seeing it.  The variable picker in the package setup in Deploy doesn't expose that many variables, and I don't remember all the variable names from Inventory.   Heck, don't even know that I can manually point to one anyhow -- a nested package item doesn't provide for using variables in the name of the package to be nested.  Does it?

 

 

1

Comments

1 comment
Date Votes
  • Avatar
    Colby Bouma

    The name of the Nested Package step doesn't change, but it is pointed to the current version of the package. The name not changing is a bug. If you are seeing something different, please contact support@pdq.com.

    1