PDQ deploy or inventory auto run script to workstation

Follow

Alan Anderson

• October 21, 2020 15:32

Hi

we have a script that runs to delete files from workstations that have gone over a certain % of hard drive space left.

This is not working will as zabbix (our monitoring system) dose not always trigger PDQ deploy to run the script.

Is there any way to do this within PDQ? if pdq inventory updates and see a workstation have xxx% of storage left then run pdq package to workstation?

 

Thanks

1

• 

  Luke Nichols

  • October 21, 2020 16:54

  Alan,

  Yes you can do this, it should be fairly simple.

  1. Wrap your script that deletes files into a PDQ Deploy package.
  2. Create a dynamic collection in PDQ Inventory that contains only computers with xxx% of storage left
  3. Create a PDQ Deploy scheduled deployment that deploys the package from step #1 to the dynamic collection from step #2

  Here is an example of my dynamic collection that discovers workstations with low disk space:

  Any

  • Computer/Scan Status/Contains/There is not enough space on the disk.
  • Logical Disk/Free %/Between/0/15

  1

  Comment actions Permalink
• 

  Alan Anderson

  • October 21, 2020 18:09

  Hey Luke

   

  Thanks for the information, I wanted to ask would this be automatically deployed after set up?

  As soon as workstation reaches  xxx% PDQ Inventory dynamic collection is updated and package is ran

  or

  do a have to manually deploy it

  I think I can get away with setting a schedule to run every every hour? 

   

   

  1

  Comment actions Permalink
• 

  Luke Nichols

  • October 21, 2020 18:52

  Yes, you can make this automatic, depending on how you set it up. You will want to tweak your scan profile's triggers in order to catch these machines quickly. For example my "Standard" scan profile is set to scan automatically when the scan age is 7 days old. If I were to implement this in my environment, I could theoretically scan a machine, a user could download a bunch of files right after the scan and fill up their disk, and then my deployment schedule wouldn't find it until about 7 days later. If that is unacceptable in your environment you could create a new scan profile that just looks at disk space and have it run more frequently, e.g. every 24 hours. I personally wouldn't run it every hour since that seems overly aggressive, but you can test it and make your own decision regarding that. Only you know your environment well enough to make that judgement call.

  1

  Comment actions Permalink
• 

  Alan Anderson

  • October 21, 2020 22:45

  Thanks Luke

   

  I did have a look at this and see that our Standard is set to every hour already, must of been done by the guys before me.

  I have a think about the timing but now I know how to do it so thanks again

  0

  Comment actions Permalink

Please sign in to leave a comment.