Migration software
Patch My PC
Suggested in 2 of our migration playbooks, mainly for Identity and security. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What it handles
The limits of the built-in tools that Patch My PC gets around, as covered in our playbooks.
Configuration Manager to Intune migration
- Re-package apps with the latest Content Prep ToolCreates third-party Win32 applications in Intune automatically, for required deployment or Company Portal.
- Intune cannot import Configuration Manager apps, so every app is repackaged.Creates third-party Win32 apps in Intune automatically.
Essential Eight in Microsoft 365
- Apps that do not update themselves need a new package for every patchPublishes a separate update Win32 app per product that only applies when an outdated version is detected.
- ML1 wants patches for office suites, browsers, email clients, PDF software and security products within two weeks. Apps that do not update themselves need a new Intune package each time.Publishes an update app per product that applies only when an old version is found.
How it handles key settings
From the settings checklists in our playbooks: what Patch My PC carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Apps | Creates third-party Win32 apps in Intune automatically. | Configuration Manager to Intune migration |
| Application patching | Publishes an update app per product that applies only when an old version is found. | Essential Eight in Microsoft 365 |
Tools for the same jobs
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.