HEBook a call
Book a callHE
Microsoft 365 SecurityGriffin31Admin RightsPatchingWeb SecurityAboutBlogContactBook a call
Patch My PC · Third-Party Patching

Third-Party Patching

Windows updates itself, but Chrome, Zoom, Adobe Reader, 7-Zip and the rest of your apps don’t. Patch My PC packages, deploys and updates them automatically through Intune or ConfigMgr — no manual packaging, and no extra servers with the cloud edition.

The challenge

  • Either apps don’t get updated

    Old versions of browsers, PDF readers and work tools stay on endpoints for months — and known vulnerabilities stay open.

  • Or IT packages everything by hand

    Every update is a new package: download, test, package, deploy. Sometimes it takes weeks for an update to reach endpoints.

  • And there’s no clear picture

    It’s hard to know which versions are installed where, and what’s still exposed.

How it works

Pick the apps you want to manage from the catalog. From there Patch My PC does the work: when a new version comes out, it packages it, creates it in Intune or ConfigMgr and deploys it to endpoints by the rules you set. Users don’t need to do anything, and there’s no extra agent on the endpoints — everything runs through the Microsoft management tools you already have.

Capabilities

  • A catalog of thousands of third-party apps, with pre-tested updates that install silently.
  • Automatic packaging and creation of apps in Intune, ConfigMgr and WSUS, on a scheduled sync.
  • A cloud edition (Patch My PC Cloud) for Intune, with no on-premises infrastructure — or an on-premises Publisher for ConfigMgr and hybrid environments.
  • Automatic discovery of the apps already installed in your organization, so nothing is missed.
  • Initial deployment of new apps, including endpoints set up with Autopilot.
  • Pre- and post-install scripts, and turning off the apps’ built-in updaters.
  • Full control over timing and deployment groups, through the Microsoft tools your team already knows.
  • Help meeting the patching requirements of standards such as NIST and NIS2.

How we implement it

1. Pilot

  • Choosing the right edition: Cloud for Intune, or Publisher for ConfigMgr and hybrid environments.
  • Connecting to your organization’s Intune or ConfigMgr.
  • Mapping the installed apps and choosing the first list to manage.
  • Deploying to a pilot group — IT and selected users — and checking that updates go through without issues.

2. Full rollout

  • Setting up deployment rings: pilot, a broader group and then the whole organization, with a delay between stages.
  • Turning off the apps’ built-in updaters, so updates arrive only through Patch My PC.
  • Moving manually packaged apps to automatic management.
  • Setting up reports and tracking the share of up-to-date endpoints.

Ask someone who knows.

A short intro call with a security engineer from the team. No call center, no sales script.

Book a callContact us