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.

PDQ Deploy variable for latest version of an app?

Is there a PDQ Deploy variable which can be used in an install step to point towards the latest version of an app, as downloaded by an Auto Deployment package?

We're currently having an issue with Teams where even if we use the Uninstall Teams package before installing the updated Teams package, Teams does not get updated correctly.

We found a way to solve this but it requires some custom logic, specifically we have to do an msiexec.exe /fv "Teams_windows_x64.msi" followed by an msiexec.exe /f "Teams_windows_x64.msi" after installing the updated Teams package, in order to update the target machine's MSI cache. (as suggested by this thread

We'd like to be able to automate this - after all, PDQ Deploy itself is already automatically downloading the latest MSI - but the folder it downloads to has the version number in the folder name, so it changes every time.

Can anyone suggest a way to do this that doesn't involve us having to manually download the MSI every time it changes?



Date Votes
  • I know this is old, but this would be nice to have. Take Teams, for example. Would love to have a deployment that uninstalls Teams completely, then reinstalls the latest version, instead of running two different deployments or updating the deployment package every time Teams updates.

  • I do this all the time.  I have a schedule setup to run against the Collection Library.  Just add the Teams Uninstaller package to the schedule to remove the old version first, and then install the latest version.

  • Mike Kercher

    That's good to know. Is there a way to do it without the schedule? I need to be able to run both packages on command to certain computers. I was trying to do it all in one package. I suppose I can create a new, blank collection and add computers to it when needed.

    I'm still new to PDQ, so if there's a better way to go about it, I'd like to learn.

  • You can always do a manual deployment of both packages at the same time. It’s much simpler to let the schedule do for you though. I try to automate as much as possible.