Allow alternate options for Deploy-WtWin32App
to handle changing MSI GUIDs
#204
andrew-davison
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
For apps that either self update or change the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Zoom for instance seem to be changing their MSI GUID with every release, this means that when we deploy Zoom via
Deploy-WTWin32App
, and Zoom auto updates to a newer version, Intune will try and reinstall the old version but fail repeatedly, until the latest version is deployed viaDeploy-WTWin32App
. Issue occurs regularly because Zoom release updates on a pretty regular basis.It would be good to be able to choose to target the local .exe file path instead. That way we can rely on Zoom to auto update, and we just update the package on a regular cadence to make sure we're deploying a newish version with new builds.
I looked at other discussions mentioning MSI issues, but I think they were at different steps of the process.
Beta Was this translation helpful? Give feedback.
All reactions