Deployment Settings
Once an application is added to your library, follow these steps to configure its deployment settings before pushing it to Intune.
Last updated
Once an application is added to your library, follow these steps to configure its deployment settings before pushing it to Intune.
Last updated
Open Application Library.
Search for the application you want to deploy.
Click the three-dot menu next to the app → Select Deployment.
A settings window will open with multiple configuration options.
When an application is deployed using Pckgr’s default deployment settings, the following behavior occurs:
Installation & Detection:
Pckgr checks whether the application is already installed on the assigned devices.
If the application is not present, it is installed.
If the application is already installed, Pckgr verifies the version number and updates accordingly.
Automated Updates:
Pckgr continuously monitors for updates to the application.
Once an update is available, Pckgr tests, packages, and automatically pushes the new version to Intune.
This ensures that all managed devices stay up to date without manual intervention.
Intune Integration:
The application is uploaded as a Win32 app into Microsoft Intune.
Pckgr does not alter existing group assignments or Intune settings; it simply replaces the older version with the updated package.
Update Control:
By default, auto-updates are enabled, meaning new versions are pushed as soon as they pass testing.
Users can modify deployment settings to delay updates or require manual approval before pushing a new version.
Silent Deployment:
The application installs or updates in the background without user interaction.
Users can be prompted to close specific applications if needed, and updates can be deferred based on the altered deployment settings.
Dependency Management:
For Winget-based deployments, Pckgr ensures that the Winget Pre-Install dependency is managed correctly for all devices.
Private Repository applications are fully self-contained and do not require external dependencies.
Application Visibility:
Once deployed, applications can be viewed and managed directly within Intune.
Pckgr provides a “View in Intune” option for quick access to deployment details.
The default behaviour of the deployed application can be altered through the deployment settings window prior to deployment:
Custom Install String
Allows you to override the default install string.
You can add registration keys, or custom parameters.
Ensure that the full silent install command is included, leaving out only the filename.
Update Only
Select this option if you only want to update devices that already have the application installed.
If the application is not installed, it will not be deployed.
Useful for Company Portal deployments where users install apps manually. (Go to Company Portal Page)
Rename Application in Intune
Modify how the app appears in Microsoft Intune.
This can be used for naming conventions, tagging, or personalizing app names.
Remove Version Number in Intune
Removing the version number from the name is for aesthetic purposes only and does not affect the functionality of the app.
Auto Update (On/Off)
If ON, new versions of the app are automatically tested, packaged, and pushed to Intune.
If OFF, updates will be tested and packaged but will remain in the Application Library until manually deployed.
If disabled, an email notification will be sent when a new version is available.
To manually update, click the three-dot menu → Update.
Defer Updates - instead of Silent Install
Users receive a Windows pop-up notification when an update is available, prompting the user to allow or defer the update installation.
They can defer the update a specific number of times before it is forced, as determined in the deployment settings window.
Defer and Close Applications Before Updating
Users receive a Windows pop-up notification when an update is available and specific applications are currently in use.
The user has the option to close these applications to allow the installation, or defer the update.
In this settings box, list multiple applications to be closed by separating them with a comma (e.g., chrome, firefox).
The app names are the exact process names as found in Task Manager.
For a list of applications that need to be closed before they are updated, see the Applications that Require to be Closed Before Updating list.
Prompt for Restart
Prompts the user to restart their device after the update.
The restart notification includes a countdown timer, the length of which can be altered in the settings box.
Remove Shortcut
Deletes the desktop shortcut of the application after installation.
Useful for removing clutter from user desktops.
Install Flow: the shortcut is automatically added during the installation, after which a shortcut cleanup script is run to search for and remove the shortcut file.
The shortcut file name is the name of the application with the '.lnk' extension. For some applications this may require an initial installation on a test device to confirm what the name of the shortcut is.
If using the "Defer Prompt" option, we recommend hiding the Intune toast notifications for the application to prevent confusion with the end user. This is because if they choose to defer the installation, Intune will flag it as a failed install and show a toast notification.
Be aware when assigning to device-based groups that installs can occur without the user being logged in. This means if you have set processes to be closed or device reboots, it will happen without prompting the user. To avoid this please assign to user-based groups.
For applications using Pckgr’s Private Repository, additional rollout controls are available:
Pilot Group Assignment
Select an Intune Group ID to test the update on specific devices before rolling it out company-wide.
To find the Group ID:
Open Microsoft Intune → Go to Groups → Select the group → Copy the Object ID.
Paste the Group ID in the Pilot Group settings box.
The Production Delay slider is now activated.
Production Delay
Using the slider, set a delay (in days) between the Pilot Group roll-out and pushing the update to all production users.
This allows time for testing and issue resolution.
Global Delay
Using the slider, set a delay (in days) before ANY update deployments start.
Useful for avoiding vendor bug releases, receiving the fixes that were pushed post update release instead.
Enrollment Status Page (ESP) Integration (Autopilot)
Enter the ESP ID to ensure the latest version of the app is included in the Enrollment Status Page.
To find the ESP ID:
Open Intune → Go to ESP Settings → Open the profile → Copy the ID from the URL.
For further information regarding Autopilot integration with Pckgr, visit the Autopilot page.
Click Deploy to Intune to initiate deployment with the selected rollout strategy. Confirmation of the roll-out implementation can be viewed in Intune under the 'availability' status of your Pilot and Production Groups.
Mac applications in Pckgr are deployed using an integration with Installomator, which automates installation and updates through a shell script in Microsoft Intune.
Update Only – Only updates devices where the app is already installed.
Force Update – Installs updates without allowing users to defer; closes the app if open.
Auto-Update – Enables or disables automatic deployment of new versions.
Click Deploy to Intune, and Pckgr generates a shell script that installs and updates the application automatically via Installomator.
Once all settings are configured, click Deploy to Intune.
The application status will update as Pckgr packages and uploads the app to Microsoft Intune.
Intune will process, verify, and register the application.
Once completed, the status will change to "Success".
You can now manage the app through Intune or click View in Intune from the Pckgr dashboard.
Click 'Next' below for information on managing your applications after they have been deployed.
