Hi there! Today I would like to show you my approach to installing the PDQ Inventory Agent through PDQ Deploy. First, a quick disclaimer: the Agent is still new and has some scaling issues. Deploy it slowly and monitor the performance of your Inventory instance. If you start to notice issues, uninstall a few Agents.
In order for this deployment method to work, your targets need to be scanned by Inventory first. I’m assuming if you can deploy to them, you can scan them. Scanned computers can use the generic config file installation method. This is a file that Inventory automatically generates and contains information like the Server’s hostname, port, and public key. If the target hasn’t been scanned you have to generate a specific config file for each target, hence why you can’t easily build a package for that.
Here is the XML file for the package I built. Download that as an XML file, then import it into Deploy. In the next section, I will go over the specifics of this package and some things you may want/need to change.
- Copy Mode: This is set to Push because the paths to the files have to be non-UNC in order to be generic. You can change this to Pull if you change your paths to UNC format. Just don’t move these files into your Repository, they won’t automatically update when you update Inventory.
- Install File: If you have Inventory installed in a non-default location, you will need to edit this.
- Parameters: /S is “silent” and /Config points to the config file that is copied from Additional Files below.
- Additional Files: This is the path to the generic config file. If you have Inventory installed in a non-default location, you will need to edit this.
That’s how I install the Inventory Agent with Deploy. Just remember to be careful how many Agents you install. If you have any questions or run into any issues make sure to leave a comment below.