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.

Updating Custom Deploy Packages

edmondsong2

September 06, 2019 21:19

Sorry for all the questions.

I cannot see any way of deploying my own custom packages. I have one in which I have placed a piece of software. It's version 1.00 - I've deployed it.

Today version 1.05 was released. Can I drop this into the same package with PDQ noticing that the package has been updated? And so the new version is sent out on the next scan?

Cheers

Gareth

Comments

1 comment

Adam
September 08, 2019 01:09
PDQ Deploy on it's own is just used to push the software. The logic you'd have to build within PDQ inventory, which is monitoring the machines.

For my own packages, i'll build a deployment package, and then set up a dynamic list in Inventory monitoring for that package.

I.e. "package x not installed or not up to date"

The logic within that list would be:
```
any-
  software x not installed
  all-
    software x installed
    software x version less than y
```
Then my PDQ deploy package would be set to deploy on heartbeat or daily to the inventory "package x not installed or not up to date" list that is monitoring for those out of date conditions.

When i update a application then, i'll change the installer on the pdq deploy package to the new version, and change the monitoring version number (y) on the inventory list.
0