Custom Applications
Deploy and manage your own Custom Applications to Pckgr.
Custom Application Feature Documentation
Our Custom Application feature empowers customers with enhanced control over application deployments and third-party patching. Our ultimate goal is to create a streamlined, drag-and-drop process for deploying any application efficiently.
The Custom Application feature is only available on the business plan.
Benefits of Using Custom Applications
Improved Version Control: Maintain better oversight of application versions.
Reduced Reliance on Winget: Less dependency on Winget for application management.
Direct Installer Uploads: Upload installer files directly for ease and convenience.
Enhanced Reliability during Autopilot: More dependable performance during Autopilot setups.
Validation Process
The standout feature of Custom Applications is the automated validation process, allowing you to upload the installer and click "Verify." The validation steps include:
Downloading the application into a container.
Scanning the installer for malware or any known malicious content.
Identifying if the installer is an EXE or MSI.
Automatically detecting the install string (unless manually specified).
Testing the application installation.
Creating a detection script based on the registry entry created.
Testing the detection script.
Generating a description for the application (unless no information is available).
Returning the package to Pckgr.
How to Use Custom Applications
Log into the Dashboard: Select the Custom Application Tab.
Create a New Application: If you haven't added a Custom Application, a pop-up will open to create a new one.
Upload Your Application File: Click the Uploader and select your application file (must be EXE or MSI).
Set Application Name: Ensure this is as accurate as possible to assist with detecting the installation. For example, for FileZilla_3.67.1_win64-setup.exe, use "FileZilla" as the application name. If set to auto, the package will use the Product Name (for EXE) or the Product Code (for MSI).
Set Auto Detection: If set to auto, the package will use the Product Name (for EXE) or the Product Code (for MSI) to detect the application. If this is turned off, it will use the Application Name
Provide an Install String (Recommended): Although various detection measures are in place, manually adding the exact install switches is more accurate if known. Avoid including personal tokens or identifiers during validation. These can be added during deployment to Intune after validation.
Click Verify: Wait for the application to pass validation. If the application fails, try uploading again with a different install string or notify support.
Edit Metadata and Set a Logo: Once verified, you can change the metadata of the package and set a logo.
Save the Application: Complete the process by saving the application.
Current Limitations
Unable to install portable applications (does not create a registry entry)
May be unable to determine silent install string
How Does Detection Work?
Once an application is successfully installed, Pckgr performs a registry scan to identify the application based on provided details. For MSI installations, the system automatically uses the MSI Product Code for detection. For EXE installations, it will either use the application name specified by the user or, if set to auto-detect, will utilize the Product Name found in the registry.
Troubleshooting Application Failures
If an application fails during deployment, start by reviewing the error message provided in the pop-up, as it often indicates the cause of the failure. Additionally, a screenshot of the error will be displayed, which may contain specific error messages helpful for troubleshooting. If further assistance is needed, please reach out to support at support@intunepckgr.com with the application name and a download link. Our support team will conduct testing to help resolve the issue.
Last updated