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.

Help with 'Using Powershell to download updates' on custom package

Stephen Jewell

August 05, 2021 16:14

I'm following this guide to try and automate a few custom packages I have. I've ran in to two issues getting this to work:

Unsure about file permissions

I use my fileserver as my repository, but both the Deploy and Inventory databases are stored locally. If I run this script on the PDQ server, how does PS handle permissions for downloading, creating folders, moving folders, renaming folders? If I run the script on the fileserver, does PDQ pass along the creds to be used to view the DB?

Download URL is not static and changes with version number

I'm unfamiliar with how the WebRequests work, I'm assuming for this purpose this is actually a good thing, as I should be able to strip the filename from the URL and use that to determine if there is a new version? Has anyone gotten this to work or wouldn't mind pointing me in the right direction?

Comments

1 comment

Colby Bouma
August 06, 2021 22:33

If I run this script on the PDQ server, how does PS handle permissions for downloading, creating folders, moving folders, renaming folders?

That will all be based on the user you run PowerShell as.

If I run the script on the fileserver, does PDQ pass along the creds to be used to view the DB?

I recommend against doing this. Since database access is required, it will be easiest to run this script on the PDQ server.

I'm unfamiliar with how the WebRequests work, I'm assuming for this purpose this is actually a good thing, as I should be able to strip the filename from the URL and use that to determine if there is a new version?

Unfortunately, it's going to vary a lot between programs. Which programs are you trying to download?

0