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.
- Make a baseline software package, which has a couple dozen apps, each configured with their own packages (some are auto-update packages from PDQ).
- One package, say 7-Zip, is pointed to a specific PDQ auto-updating package...
- 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).
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?
Please sign in to leave a comment.