# Custom Applications
## Overview The Custom Applications tool allows you to upload, package, verify, and deploy internal or vendor-restricted Windows applications that cannot be monitored or updated automatically by Pckgr. This tool is ideal for internal apps, apps behind authentication portals, or licensed software not publicly available for download. Follow the steps below to package and deploy a Custom Application: 1. Upload your installer file (EXE, MSI, or ZIP). 2. Fill in the application metadata and packaging settings. 3. Click **Verify** and wait for the packaging process to complete (may take up to 15 minutes). 4. Once verified, review the metadata, upload your logo and click **Save**. 5. Deploy the application from your Application Library. 6. When a new version is available, repeat this process. If your installer is publicly available, we recommend using the **Request an Application** feature instead. This allows the application to be added to Pckgr’s Private Repository, enabling automated updates and long-term support. **Business Plan Required**\ Custom Applications is only available to customers on the Business Plan. *** ## Best Practices To ensure a successful packaging process and reliable deployments, follow these guidelines: * Ensure the installer supports silent installation. Check the vendor’s documentation for appropriate install switches. * Provide known silent install switches in the Install String field. Do **not** include the filename in this field. * Use full version release installers only. Avoid incomplete, web-based, or stub installers. * Installation validation is performed on a Windows 11 virtual machine. If your installer requires additional software (e.g., .NET, Visual C++), specify the pre-requisite from the drop-down list. * Use clear and simplified naming (e.g. "FileZilla") for the Application Name. Avoid version numbers or installer filenames. * If verification fails, you can either try a different install string or select the option to raise a support ticket for assistance. {% embed url="" %} *** ## **When to Use Custom Applications** Use Custom Applications for: * Internal business applications. * Applications with installers behind authentication or paywalls. * For example, design packages such as AutoDesk DWG TrueView - read our blog post [here](https://blog.intunepckgr.com/2025/06/13/deploying-dwg-trueview-to-microsoft-intune-using-pckgr-custom-applications/) for insight into packaging applications such as this. * Commercial applications where Pckgr cannot programmatically access installer files for automation. **Tip:**\ If your installer is publicly accessible for Pckgr to download, submit it through [**Request an Application**](https://docs.intunepckgr.com/about-pckgr/applications-available/request-application). Pckgr will then fully automate patching and version management using its [**Private Repository**](https://docs.intunepckgr.com/getting-started/creating-deployments/repositories/private-repository). *** ## **Workflows** ### Packaging Workflow #### **1. Access Custom Applications** * Log in to the Pckgr Dashboard. * Select the **Custom Application** tool. * Click **Create New Application** to begin. #### **2. Upload Installer File** * Upload your installer file. * **EXE** or **MSI** only - this is a Windows Application tool. * For complex application with extra files, upload these as a **ZIP** file. * Upload the full release version you intend to deploy. #### **3. Set Application Name** * Enter a clear name (for example: FileZilla instead of FileZilla\_3.67.1\_win64-setup.exe). * The name is critical for downstream detection accuracy. #### **4. Configure Detection Logic** * **Auto Detection Enabled (default):**\ Pckgr will automatically extract detection information: * For MSI files: MSI Product Code will be used for detection. * For EXE files: Product Name is extracted from registry entries post-install. * **Auto Detection Disabled:**\ Pckgr will default to using your provided Application Name for detection. #### **5. Provide Install String (Highly Recommended)** * Supply any known silent install parameters. * Avoid including tokens, license keys, or tenant-specific data. * This can be added in the 'Install String' section when performing the actual deployment of the Custom Application from the Application Library. * Install strings dramatically improve test validation accuracy. * If you disable this setting, Pckgr will search for and create an install string for you. #### **6. (Optional) Select Pre-Requisite Application** * If your installer depends on another app being installed to validate: * Select the **Pre-Requisite Application** from the drop down list. * Pckgr will use this application during the installation validation test. * The pre-requisite is only used for verification, it is not included in your package nor deployed automatically. *** ### **Verification Workflow (Automated)** Once the above steps are configured, click **Verify**. Pckgr performs a fully automated validation process, which includes: 1. Downloading and isolating the installer file inside a secure container. 2. Scanning for malware or known malicious content. 3. Identifying the installer type (EXE or MSI). 4. Parsing and applying the install string. 5. Executing the installation silently in a test container. 6. Scanning the registry to detect installation markers: * For MSI: Product Code is captured. * For EXE: Product Name from registry or Application Name (if auto detection is disabled). 7. Generating a detection script based on registry entries. 8. Testing detection script accuracy against install results. 9. Generating application description metadata. 10. Returning the package back to you for final confirmation. **If verification fails**, you may: * Reattempt verification with a different install string. * Submit a support request. #### **7. Edit Metadata and Set Logo** * After successful verification: * Edit any metadata as required. * Upload a logo for the application (optional but recommended). * Assign RBAC for this application if necessary. ([read more](https://docs.intunepckgr.com/getting-started/setting-up-your-dashboard/adding-team-members/rbac-role-based-access-controls)) * ```
``` #### **8. Save Package** * Click **Save** to finalize the application packaging. * The validated Custom Application is now ready for deployment from your own Custom Apps repository - these applications are private to your company, you are not adding applications to the library for other Pckgr users. *** ### **Deployment Workflow** * Navigate to your **App Library**. * Select **Add New App**. * Choose **Custom App** as the app type. * Add your application to the library using the blue plus button. * Click the three dot menu and select Deployment. * For applications with licence keys etc, enter these into the install string in the settings box. * Deploy to Intune. * Assign devices. Deployment of Custom Applications follows the same process as standard applications within Pckgr. *** ## **Updating Custom Applications** * Custom Applications operate on a **static update model**. * Each time a new version is available: * Upload the new installer. * Repeat the packaging and validation process. * Save and deploy. ### Deploying Updates Using Dependencies For applications like AutoCAD, where updates are distributed separately from the base installer, you can use the Custom Application feature in Pckgr to package and deploy these updates with ease. By leveraging the **Dependencies** feature, you ensure that the update is tested in the correct context, with the base version already present. #### **Steps to Package and Deploy an Autodesk Update** **1. Ensure the base application exists**\ Before packaging an update, make sure the base version of the Autodesk application has already been uploaded to your Custom Library. Steps on how to package complex applications such as Autodesk, read our full blog post: [How to deploy Autodesk applications to Intune using Pckgr](https://blog.intunepckgr.com/2025/11/27/how-to-deploy-autodesk-applications-to-microsoft-intune-using-pckgr/) **2. Download the update installer**\ Log in to your Autodesk account and download the update you want to deploy. **3. Upload the update to Pckgr**\ Use the Custom Application tool to upload the update installer. Populate the required metadata and set the install command to use silent flags such as `-q` or `/quiet`. **4. Set the dependency**\ Select the original AutoCAD base application as a **dependency/pre-requisite**. This ensures the update is tested with the base app already installed. > Note: Dependencies are only used during the **testing** phase. The update will be deployed on its own once verified. **5. Upload and verify**\ Upload the package, then click **Verify**. Pckgr will provision a test environment, install the base application, then install the update. If the detection script passes, the app is marked as Verified. **6. Save and deploy to Intune**\ After verification, the update will be available in your Custom Library. You can now deploy it to your Intune-connected devices like any other application. Autodesk updates are typically much smaller than full installers, so there's no need for Azure Blob storage; the upload can be done directly. For a detailed walk-through, including screenshots and examples, see our full blog post:\ [How to easily package Autodesk updates for Intune using Pckgr](https://blog.intunepckgr.com/2025/12/18/how-to-easily-package-autodesk-updates-for-intune-using-pckgr/) *** ## **Known Limitations** * Portable apps (without registry entries) are not supported. * ARM architecture currently unsupported. * Silent install string detection may occasionally require manual input. *** ## Custom App Support When deploying a custom application, installation failures can occasionally occur due to incorrect install commands, missing dependencies, or packaging issues. Pckgr includes built in support handling to streamline troubleshooting and reduce resolution time. #### **What happens when a custom app fails** If a custom app installation fails, Pckgr automatically captures key diagnostic information at the time of failure. This includes: * Application name * Publisher * Install command used * Error summary * Full installation log * Timestamp of the failure This information assists our team with troubleshooting. #### **Creating a support request** After a failure occurs, users are presented with the option to create a support request directly within the platform. When submitting a support request: * The failure details are automatically attached * No manual log collection is required * The user has the option to include any further information and context of the package #### **What happens after submission** Once a support request is submitted: * The support team receives the full failure context * Tickets can be viewed in the 'messages' section of the ChatBot widget * Once the report has been analysed, a Pckgr technician will reach out to the user to assist * The failed application attempt is cleared to allow a clean retry * Users can correct inputs and redeploy without interference from previous failures #### **Best practices for faster resolution** To help resolve issues quickly: * Ensure install commands are accurate and tested where possible * Provide any additional context in the support request if prompted * Retry deployment only after making necessary corrections *** ## **Summary Table: Private Repository vs Custom Applications** | Use Case | Recommended Solution | Automation | | ---------------------------------------------- | -------------------- | ----------------- | | Installer files publicly accessible to Pckgr | Private Repository | ✅ Fully Automated | | Installer files behind authentication/paywalls | Custom Applications | 🚫 Manual Upload | | Internal LOB/Corporate Software | Custom Applications | 🚫 Manual Upload | All packaging, validation, and deployment is handled entirely within Pckgr’s secure infrastructure, with no reliance on external repositories.