Pckgr
  • About Pckgr
    • Intro: What is Pckgr?
      • How Package Updates Work
      • PckgrBot
      • Homage to Winget
    • Applications Available
      • Request Application
    • Security of Pckgr
      • Microsoft Single Sign On
    • Pckgr Pricing Model
    • Feature Releases and Roadmap
      • Q1 2025 New Features Newsletter
  • Getting Started
    • Setting up your Dashboard
      • Signing Up
      • Managing Companies
      • Connecting Tenants
      • Adding Team Members
    • Creating Deployments
      • Application Library
        • Detect Applications from Intune with Pckgr
        • Application Status Tag
      • Repositories
        • Winget
        • Private Repository
          • Upgrading an Application to the Private Repository
        • MacOS
      • Deployment Settings
      • Application Management
  • Extra Features
    • Custom Applications
    • Cloning Intune Policies
  • INTEGRATIONS
    • Company Portal
    • Autopilot
    • Microsoft 365
  • Troubleshooting
    • Install Logs
    • Error Codes
    • Winget Issues
      • Winget Pre-Install
      • Winget CDN Issue
      • Repair Winget with PowerShell
    • Applications that Require to be Closed Before Updating
    • Frequently Asked Questions
  • SUPPORT
    • Pckgr ChatBot
    • Support Email
    • Delete your account
  • Policies
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  • Key Differences in Upgrading
  • Steps to Upgrade an Application to the Private Repository
  1. Getting Started
  2. Creating Deployments
  3. Repositories
  4. Private Repository

Upgrading an Application to the Private Repository

As of May 2025, Pckgr is transitioning away from the Winget Repository for application hosting, granting all users access to applications hosted in our Premium Private Repository.

PreviousPrivate RepositoryNextMacOS

Last updated 1 day ago

If you joined Pckgr prior to May 2025, you can upgrade your applications from the Winget version to the Private Repository version.

This guide explains how to upgrade applications to Pckgr’s . You can upgrade both deployed applications and those awaiting deployment, but the behavior differs depending on the application’s status.


Key Differences in Upgrading

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.


Steps to Upgrade an Application to the Private Repository

1. Identify the Application for Upgrade

  • Navigate to the App Library in the Pckgr Dashboard.

  • Select the application you want to upgrade (app must be available in the Private Repository).


2. Initiate the Upgrade

  • 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).


3. Confirm Upgrade

  • After selecting the desired version, select Confirm.


4. Configure the Deployment (Awaiting Deployment Status Only)

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).


5. Deployment Behavior

  • 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.

Private Repository