Pckgr
  • About Pckgr
    • What is Pckgr?
    • Applications Available
    • Security of Pckgr
    • Homage to Winget
      • PckgrBot
    • Pckgr Pricing Model
  • Getting Started
    • Introduction
    • Managing Companies and connecting to Intune
    • Create a Deployment
      • Deleting an Application
      • Redeploying an Application
        • Automatic Redeployment
      • Advanced App Installer
        • Example: Prompting to close an Application
        • Example: Deleting a Desktop Shortcut
      • MacOS Applications
        • Deploying an MacOS Application
      • Pckgr's Premium Private Repository
        • Upgrading an Application to the Private Repository
      • Detect Applications from Intune with Pckgr
    • Adding a Team Member
    • Requesting an application from the Winget Library
    • How Package Updates Work
      • Update Only Option
    • Custom Applications
    • Application Status
    • Code Signing
    • Deleting Account
    • Microsoft Single Sign On
    • Using Pckgr with Autopilot
    • Cloning Intune Policies
    • Application List
    • Pilot Group Deployment
  • Troubleshooting
    • Install Logs
    • Applications that Require to be Closed Before Updating
    • Winget CDN Issue
    • Repair Winget with PowerShell
    • Winget Pre-Install
    • Reporting a Bug
    • Frequently Asked Questions
    • Support Contact Details
  • Policies
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  • Overview
  • Enabling the "Update Only" Feature
  • What does this actually do?
  • Managing applications with the Company Portal
  1. Getting Started
  2. How Package Updates Work

Update Only Option

How to use the "Update Only" feature in Pckgr

PreviousHow Package Updates WorkNextCustom Applications

Last updated 10 months ago

Overview

The "Update Only" feature allows users to deploy applications to Intune with the option to update the app without performing a fresh installation if the app is not already detected on the target device. By enabling the "Update Only" slider during the app deployment process, users can ensure that only updates are applied to devices that already have the application installed.

Enabling the "Update Only" Feature

To enable the "Update Only" feature for deploying applications to Intune, follow the steps below:

  1. Go to App Library in Pckgr

  2. Locate the application you wish to update and add it to your Library

  3. Using the deployment options, tick the "Update Only" slider on

  4. Deploy the Application

What does this actually do?

Deploying an application in "Update only" mode adds an extra requirement script during the deployment process. This requirement script check via Winget if the application is already installed on the device. If the application is installed, the update will proceed. If the application is not installed, the status of the device will show "Not applicable".

Managing applications with the Company Portal

For customers wanting to use the Company Portal, you might be finding that your users are installing an application only to find that once a new version is released they are now outdated.

Here is where our Company Deployment strategy comes in!

  1. Start by going to the Application page and creating two deployments of an application.

    Here we will deploy Firefox Twice (Make sure to select "All Apps" from the drop down so you can make multiple deployments)

  2. Deploy one of these apps with "Update Only" turned off and one with "Update Only" turned on.

  3. Once Deployment is complete, head over to Intune to make your group deployments

  4. Select normal deployment (Update Only turned off) and edit the assignments. Select either a group or all users for the Available category. This will be your Application that shows in the Company Portal. Save Changes.

  5. Select the second deployment (Update Only turned on), edit the Assignments and set the Required field to all users or devices. This will act as an updating package that will deploy an update when the application is detected on the device. Keep in mind this will also target devices which installed the application without the Company Portal.

  6. Pckgr will then continue to deploy updates to these packages

Flow

  1. User downloads and installs application from the Company Portal (This will always be the latest version)

  2. When the application updates, the users device will be targeted by the second deployment and will force the application to update

  3. The detection from the application in the Company Portal will still show as up to date.