Upgrading an Application to the Private Repository
Migrating from Winget deployed applications to the Private Repository
Last updated
Migrating from Winget deployed applications to the Private Repository
Last updated
This guide explains how to upgrade applications to Pckgr’s Private Repository. You can upgrade both deployed applications and those awaiting deployment, but the behavior differs depending on the application’s status.
Application Status
Behavior During Upgrade
Deployed Applications
The new private version is automatically redeployed to Intune. The old deployment is removed, and all group assignments are copied over.
Awaiting Deployment Applications
The application is upgraded to the private version, but it will remain “Awaiting Deployment.” Manual deployment is still required.
Navigate to the App Library in the Pckgr Dashboard.
Select the application you want to upgrade (app must be available in the Private Repository).
Click on the Upgrade button next to the application.
A pop-up will appear prompting you to select a version from the Private Repository.
Choose the desired version from the available options (this will vary between applications).
Example: In the images above, the user selected TeamViewer (x64 MSI).
After selecting the desired version, select Confirm.
For upgraded applications, you can configure the following options before deployment:
Custom Install String (Optional)
Update Only: Deploy updates only if the application is already installed.
Remove Version from Display Name
Auto Update: Enable to keep the app updated automatically.
Delay Updates: Specify a delay (in days) for updates to roll out.
Advanced Installer: Add advanced install options (e.g., defer updates or close apps).
Deployed Applications:
The new private version replaces the existing deployment.
Pckgr automatically removes the old version from Intune.
All previous assignments (group deployments) are copied over seamlessly.
Awaiting Deployment Applications:
The app is upgraded to the Private Repository, but it remains Awaiting Deployment.
You will still need to click Deploy to Intune manually.
