Create a Custom App

Explains how to create a Custom App using Patch My PC Cloud

Patch My PC (PMPC) Cloud allows you to create your own Custom Apps, which are typically in-house developed.

To create a Custom App:

Sign in to the PMPC portal https://portal.patchmypc.com/.
On the App Catalog page, click Add App.
The Custom Apps Deployment Wizard starts.
On the Upload Application page, either: a. Click Select Primary Install File and browse to the location containing the app’s installer (EXE or MSI).
b. Drag and drop the installer file onto this page.

Tip

If you plan to deploy an EXE-based installer, use our free script to help you extract the required information from the registry. See Finding properties for EXE-Based Installers for more information.

The hash for the file is calculated as the file is uploaded to your portal.

If the installer does not require any additional files, go to Step 6.
If the installer does require additional files, either: a. Click Select Additional Files and browse to the location containing the additional files.
b. Drag and drop the files onto this page.
Click Next.
On the General Information page, either: a. Click Upload Icon to upload a suitable file (png, jpg or jpeg) to use as the icon for this app.
b. Drag and drop the image file onto this page.
In the App Name field, enter a unique name for the app.

Tip

Avoid specifying the version number in this field, as this field does not get updated whenever you add a new version

In the Vendor field, either select an existing entry from the dropdown or enter the required name.

Note

If the vendor is new to your portal, you will see the Success – The vendor <vendor_name> has been created notification. The next time you add an app, this vendor will appear in the Vendor dropdown.

In the Description field, enter a description of the app.
Enter any optional internal notes, then click Next.
On the Configuration page, configure the required options.

Field Description

Field	Description
Install Context	Controls the context in which the app is installed, either SYSTEM or User.
Architecture	Specifies the architecture for the app, either 64-bit or 32-bit. Detection uses this field to determine whether to look in the 32-bit or 64-bit registry keys: `HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall` or `HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall`
Version	The version of the application as shown in Add or remove programs. Detection uses this field to determine if the app is installed by looking for a matching DisplayVersion entry in the registry key: `HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall`
Language	The language of the application
Apps & Features Name	The name of the application as it appears in Add or remove programs. Detection uses this field to determine if the app is installed by looking for a matching DisplayVersion entry in the registry key: `HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall` NOTE As this field allows a "%" wildcard (which matches on any string of characters), consider replacing the version number with this wildcard if the version number is in the Apps & Features Name. This will allow App Detection and Update Requirement rules to detect older versions of the app on your endpoints. IMPORTANT As the Apps & Features Name is used to determine applicability and detection, using an overly generic name may cause Intune Updates to be detected as required on devices without the software installed.
Conflicting processes	A comma-separated list of executables that may interfere with the installation of this app. This field populates the list for the Manage Conflicting Processes right-click feature.
Silent install Parameters	Command-line arguments used to install the software silently, i.e. the user is not aware of the installation occurring. NOTE Providing `msiexec.exe /i` for MSI installations is not required. Using `msiexec.exe /qn` will be adequate for most MSI installations.
MSI Product Code	Applies to MSI installers only. The MSI Product Code for this app, which is used for detection. NOTE If the MSI Product Code for your installer does not update between versions, the Custom Apps Detection and Applicability rules will: • Not detect any changes and no updates will not be installed. • Detect the MSI app, even if an older version is installed. To work around this issue, change the MSI Product Code to all 0's (`00000000-0000-0000-0000-0000`) when creating the Custom App. This forces the detection and applicability scripts to fall back to DisplayName and DisplayVersion detection.

Install Context

Controls the context in which the app is installed, either SYSTEM or User.

Architecture

Specifies the architecture for the app, either 64-bit or 32-bit.

Detection uses this field to determine whether to look in the 32-bit or 64-bit registry keys:

HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

Version

The version of the application as shown in Add or remove programs.

Detection uses this field to determine if the app is installed by looking for a matching DisplayVersion entry in the registry key:

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

Language

The language of the application

Apps & Features Name

The name of the application as it appears in Add or remove programs.

Detection uses this field to determine if the app is installed by looking for a matching DisplayVersion entry in the registry key:

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

NOTE

As this field allows a "%" wildcard (which matches on any string of characters), consider replacing the version number with this wildcard if the version number is in the Apps & Features Name.

This will allow App Detection and Update Requirement rules to detect older versions of the app on your endpoints.

IMPORTANT

As the Apps & Features Name is used to determine applicability and detection, using an overly generic name may cause Intune Updates to be detected as required on devices without the software installed.

Conflicting processes

A comma-separated list of executables that may interfere with the installation of this app. This field populates the list for the Manage Conflicting Processes right-click feature.

Silent install Parameters

Command-line arguments used to install the software silently, i.e. the user is not aware of the installation occurring.

NOTE

Providing msiexec.exe /i for MSI installations is not required. Using msiexec.exe /qn will be adequate for most MSI installations.

MSI Product Code

Applies to MSI installers only.

The MSI Product Code for this app, which is used for detection.

NOTE

If the MSI Product Code for your installer does not update between versions, the Custom Apps Detection and Applicability rules will:

• Not detect any changes and no updates will not be installed.

• Detect the MSI app, even if an older version is installed.

To work around this issue, change the MSI Product Code to all 0's (00000000-0000-0000-0000-0000) when creating the Custom App. This forces the detection and applicability scripts to fall back to DisplayName and DisplayVersion detection.

If you are happy you have entered all of the details for the app correctly, click Create otherwise click Next.
On the Summary page, review you have configured the app correctly. • If you are happy, click Create.
• If you need to change something, click < Prev to backtrack through the Deployment Wizard to the relevant setting. Make the change, then step back through the wizard to this page. If everything is now correct, click Create.
The App Catalog is displayed and the following notification is displayed: <app_name> Added – Your application has been successfully added to the “App Catalog”
You can now deploy and manage your Custom App in the same way as other PMPC Cloud apps.