Patch My PC Publisher

Lots of proprietary third-party software can be licensed in many different ways. I would say the most common approaches can be one of four: Pass a license key via parameter Pass a file path to a license file via parameter Copy a license file to so...

It would be nice to allow Apps to sync once a week while patches could sync every day. Scenario: Schedule set to daily at 2:00am. Patches and Apps sync and distribute to all DPs (how we have it configured). Content transfer gets deep queue and dur...

Integrate with Azure Update Manager to provide 3rd party updates for servers managed in Azure.

Azure Key Vaults allow storing code signing certificates in a secure manner as the certificate can be called using an app registration (with certs and secrets) instead of having a cert with an exportable private key. This would increase security o...

When auto-publishing rules for Intune Applications are created, Patch My PC will create the Win32 application in Intune, however it will not automatically assign the application. As mentioned in the comment of idea PATCHMYPC-I-1835, I understand t...

The PMPC Publisher downloads apps before packaging them for Intune. The New-CIPolicy cmdlet can read the Publisher cert and export a small WDAC policy in .xml format. Customers can then use the WDAC Wizard to merge this policy with their existing ...

Currently in the Publisher console, when enabling the "Send Email Reports", the customization for the message are pretty basic: change the subject field of the email message and add a string of text before the report itself. We would like to have ...

The default for apps which need MCP to be enabled is "skip". This feature request is to let customers change their desired default, which changing the MCP option for All Products. In other words, what if a customer wants "notify" or "auto-close" a...

Add a Right-Click option similar to the "Add 32bit OS requirement" for ARM64 Requirements. This will allow 32 and 64-bit applications that can be emulated on ARM64 to be installed on those endpoints.

Currently, the catalogue can't contain update binaries larger than 2GB. Updates cannot be imported into SCUP if the byte size is larger than [int32]::maxvalue, and SCUP/Publisher cannot publish the update to WSUS because .cab files have a max file...