Adding an in-house Application to The Easy2Patch Catalog

Easy2Patch works integratedwith Intune, System Center Configuration Manager (SCCM) or WSUS by seamlessly integrating third-party patching and application management.

Easy2Patchcatalog has lots of 3rd party products. Detection, automatic distribution, unattended installation of outdated software can be performed via Easy2Patch without the need for an additional agent.

Software which are in-house developed, or some of the licensed software (e.g software that are not widely used) may not be included in E2P catalogs. Also, normally, it may not be possible to add them to E2P catalogs as they may not have an official distribution point for new versions. Because the products added to the catalog must be accessible, downloadable, and installable by all customers. Easy2Patch provides a feature called Custom Product Injection for adding enterprise-specific applications to the catalog. So, with this feature, products that cannot be included in the catalog can be added. The product added to the catalog will be distributable via SCCM or Intune as application.

Easy2Patch provides a free trial (which has a few applications) catalog that you can add it in SCCM/WSUS or Intune. For detailed information please visit To install Easy2Patch in your environment, please visit and download from

How to add an in-house application to the Easy2Patch catalog?

In the following article, you will learn how does Easy2Patch helps your organization’s information security and how to add your in-house and native applications to the Easy2Patch catalog.

First, on the Easy2Patch screen, one of the Application, Intune Update or Intune Application tabs is switched. This feature is only available in Advanced and Enterprise licensing. Select the node with the license owner’s name in the Custom App Category at the bottom of the list and right-click then select Add Applicaton.


The following screens are filled in order:

  • Title: The name of the application is entered.
  • Description: enters a short description about the application.
  • Version: The version information that appears on the Add/remove Programs screen of the product is entered. It is important to enter it exactly as it appears. Publisher: manufacturer information is entered.
  • URL/File: The file is displayed from a URL or local file system.
  • File Name: The name of the file. It is filled automatically.
  • Digest: It is the digest information of the file. is filled automatically.
  • Auto Deploy: Allows the application to be deployed automatically during deployment on SCCM or Intune.
  • Title: The name of the application is entered.
  • Description: enters a short description about the application.
  • Icon: An icon file with icon extension can be given, which can be up to 1 MB in size.
  • Title: The name of the application is entered.
  • Description: Enters a short description about the application.
  • Install Command Line: Enter the unattended installation parameters. The name of the application does not need to be entered.
  • Uninstall Command Line: Unattended uninstall parameters are entered. The name of the application does not need to be entered.
  • Installation Behavior: Deploy to User or System option is selected.
  • Detection Method: These are important parameters that must be entered to understand whether the application is installed on the target system. These parameters are searched in the Uninstall registry sets of the target system.
  • App To Sarch: Searches the DisplayName registry key of the application. It can be done in queries with a similar name by adding a wildcard (*) to this field. Fortinet means beginning with the word Fortinet.
  • Exclude Name: Adds the condition that this name should not appear in the DisplayName field.
  • Version: Searches the application’s DisplayVersion registry key.
  • App MSI Code: It checks the MSI code of applications that have MSI setup.
  • Architecture x86: Searches for 32-bit application installed on a 32-bit or 64-bit system. x64: Searches for 64-bit application installed on a 64-bit system.

Click the Save button and the application is added to the list. The application is now distributable.


After adding the application to the tree, the Save button must be click. After this stage, the application can now be published.


Note: This is a simple and easy practice to show how to add in-house or indigenous applications to the Easy2Patch catalog. If you have any questions about the product or a request for demo, please contact with [email protected] for details.