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.

Best Practice - Suggestion

Whit3Styler

February 10, 2022 09:21

Hello my pdq friends,
I have a little question for my current setup / infrastructre.

Our concept is the following:
We have many applications (~30 different Applications) which have some ad group dependices on it.

Our old software deployment checks every pc boot if the user/computer still have the ad group or the correct version. If not, it will uninstall or update the application.

I would like to do the same with PDQ.
One of my ideas is, to link a little psexec script which execute a Package which contains all applications packages in it and it will go through everything.

Does make sense?
Another idea would be (probably) check on a Heartbeat and then just do your stuff.

What do you think about it?

Comments

1 comment

James D
February 10, 2022 15:50

How often does membership change and how aggressive do you need it to be? A PDQ heartbeat is only going to run when a computer disconnects and reconnects to PDQ. So if your PC's are left online weeks at a time they would never get checked. You may need to run a manual check beyond that, but it would still be more capable than a scheduled task.

I would set this up in PDQ just so it would be in the same place as where you are managing your software from. A script may handle this best, Schedules don't seem to handle multiple packages well unless they are potentially nested in one package.

0