Most organizations use Patch My PC because it makes third-party app updates easy and keeps PMPC Win32 apps updated on its own. So the next question that usually comes up is this: can we assign these PMPC apps to the Autopilot ESP, and is the whole setup compatible?
PMPC creates two things in Intune: IntuneApps and IntuneUpdates
IntuneApps
These are full application installers. They install the complete app even if the device doesn’t have anything installed before. Think of them as the main Win32 app packages you deploy to users and devices.
More info – https://docs.patchmypc.com/installation-guides/intune/intune-apps
IntuneUpdates
These are update-only packages. They’re meant for machines that already have an older version of the app installed. Each update includes a requirement check that looks for an existing version on the device. If the app isn’t there, the update simply won’t run.
More info – https://docs.patchmypc.com/installation-guides/intune/intune-updates
Generally, IntuneApps usually appear with the normal application name. IntuneUpdates follow a different pattern and typically start with something like Updatefor_AppName.
According to PMPC, You shouldn’t associate Intune Updates from the Patch My PC Publisher with an Enrollment Status Page. The updates have a ‘Requirement’ script that checks if an old version of the application is installed. This is almost never going to apply during Autopilot or Device Enrollment.
So yes, you can assign PMPC Win32 IntuneApps to Autopilot ESP. PMPC IntuneUpdates should not be assigned.
