Hey everyone! I'm new to handling WIN32 packages and PowerShell, and I could use some help. We have a WIN32 app in Intune that's currently on version x.x, and I need to update it to version x.xx on all devices (specifically MS Surfaces 7). I've already downloaded the latest .msi file for the update, but I realize that I need to package it before proceeding. Can anyone advise me on what PowerShell command I should use for this, and which tool is best for the packaging process? If you need any more info from my side, just let me know. Thanks a bunch!
6 Answers
Check out the Microsoft documentation on creating a WIN32 app and configuring supersedence. They provide comprehensive guides that'll help you get familiar with what you need to do. It’s packed with all the info you could need!
Just curious, can't the MSI installer just deinstall the previous version and install the new one as part of its update? Make sure it can handle this! Don’t forget about setting up the silent install commands; the manufacturer usually provides specific parameters for that.
Start by looking into IntuneWin and how to configure supersedence for your app. There are plenty of resources available that will guide you through this process!
You actually don’t need to wrap the MSI into an IntuneWin package. You can upload the .msi file directly to Intune as it is. That makes it a bit simpler!
Yeah, Microsoft recommends keeping line-of-business apps and Win32 apps separate to avoid installation issues, especially with autopilot.
You might want to consider using Intune's own interface to handle the update, just like you did with the initial deployment. PowerShell is great, but it's not really the right tool for this whole update process, aside from the install commands.
I see people suggesting supersedence, but I think it's not always effective for updating. Supersedence won’t automatically update the app unless it’s redownloaded. If users are still on version 1.1 and you release 1.2, they’ll only get the new version if they download it or if it’s set as a required install. In my experience, using two separate packages works well—one for users to install manually and another that’s set as required for updates. Just make sure to configure the detection logic correctly so it checks the application version before the update runs.
I agree that its use is limited. Sometimes, having two distinct packages really simplifies the management of updates.
What? Since when can you do that? I thought you always had to use IntuneWin!