Store your package files in your repository to avoid this hassle!įor those of us that learned our lesson too late, this blog post is for you.

Rather than change all of my hundreds of packages by hand (Pass! Boo! No thanks!), I figured that it would be easier to update them directly in the database. Using PowerShell and SQLite, this is a fairly straightforward task. Using a PowerShell provider to query the data.Since PDQ products use SQLite for their local database, we have a couple different choices to use with PowerShell and SQLite.

Pdq deploy enterprise download download#.

Otherwise it will only copy the file for the installation, and none of the other items that may be required for installation.

Under the step for installation, you need to check 'Include Entire Directory' for the specific scenario above. **EDIT: ** Leaving this here for anyone else who has this issue. Where do I tell PDQ to use the directory in which the installer is located? I do not feel I should need to change all of my installers to accommodate, so I hope there is just a checkbox I am missing. If I copy the directory to my machine and run it, it runs it from where I copied it, and installs no problem. If I install this on a machine itself, the %~dp0 line is replaced with the UNC path of the share. In other words, it is seemingly executing the batch file outside of the actual working directory. The output log, which I have found incredibly helpful for prior troubleshooting, is indicating that it is trying to run these commands from the 'AdminArsenal' folder under Windows. My problem stems as soon as I try to deploy. I have setup PDQ preferences to point to my repository of all of our installers, and that seems fine. Each of the installers is a batch file that uses %~dp0 to indicate the current running directory of the batch file.

So I'm having a hell of a time, and I'm not trying to change my installer script because it has worked flawlessly for months, but PDQ installs things differently than local installers or SCCM.